Broken Bot
Bug Reporting -- Bot's Home Board
- About Broken Bot
Broken Bot is a WarCraft III moderation bot. It supports multi-profiling, but not proxies. It's commands are a little confusing to some, but overall it's a simple and fairly effecient bot. This is the beta release of build 27. It's open beta, so everybody is welcome to download it. This is also the FIRST official release put out on the bot's new host, Bnet.cc!
Welcome to the readme.
- Commands
Basic command setup really, the bot master has 11 access, all other access is on a basis of 1 to 10. 1 is simply safelisted, 10 is administrator, -1 is blacklisted (shitlisted).
Commands shown as:
command, cmd alias(s) |
Info about command |
.command example |
Note: If certain commands in the command list are not being responded to by your bot, you may not have the latest version. This readme will ALWAYS be for the latest version of Broken Bot, and I am not making backups of this for older versions. Sorry.
Access Level 1: Safelisted, no command access. |
Access Level 2
?trigger |
Retrieves bot's trigger |
?trigger |
access, a, whois |
Gets a user's access |
.a; .a ne_sucks |
version, ver |
Retrieves the bot's current version |
.ver |
say |
Makes the bot say something (exploit safe) |
.say fuck you |
shout, yell |
Makes the bot shout something (ex safe) |
.shout jk rawful!1 |
cq, scq |
Clears bot's queues |
.cq |
|
Access Level 3
pingme |
Returns user's ping |
.pingme |
|
Access Level 4
kick, k |
Kicks a user from the channel |
.k Desu; .k D* |
|
Access Level 5
add, set |
Adds or sets a user's access |
.add WaR 10 |
remove, delete, del |
Removes a user's access |
.rem zabuza[nMx] |
setmotd |
Sets the clan MOTD to something. (Note: Must be a shaman or higher ranked to use!) |
.setmotd Wtf is clan NeS? |
Access Level 6
ban, b |
Bans a user |
.b Jivez; .b Ji* |
bancount, bans |
Retrives the count of users banned |
.bans |
status, stats |
Returns status of certain bot variables |
.stats |
unban, u |
Unbans a user |
.u sean; .u se* |
invite |
Invites a user to the clan |
.invite Lizzoud |
Access Level 7
ipban, ip |
IPBans a user |
.ip nesucks, .ip nes* |
unipban, unip |
UnIPBans a user |
.unip nesucks, .unip nes* |
blacklist, bl, shitlist, sa |
Blacklists a user |
.sa UserA |
unblacklist, ubl, shitdel, sd |
Removes a user from the Blacklist |
.sd UserB |
Access Level 8
pingban, pb |
Loadbanning mode 1. Bans all users with a ping above or equal to a specified number. (In example the ping is 555) 0/off to disable. |
.pb 555 |
loadban, lb |
Loadbanning mode 2. Bans all users with a certain string in their username. (In example the string is 'str*') 0/off to disable. |
.lb str* |
settrigger |
Sets the bot's trigger |
.settrigger # |
clanremove |
Removes a user from the clan |
.clanremove LaG |
rejoin, rj |
Rejoins the bot |
.rj |
join, goto |
Sends the bot to a channel |
.join Clan LeeT |
Access Level 9
shamans |
Displays current shamans |
.shamans |
bansperset, bps |
Sets the number of users to ban per ban set in loadmodes. |
.bps 4 |
bansdelay, bd |
Sets the delay (in seconds) between ban sets in loadmodes. |
.bd 22 |
autoloaddetection, autoload, ald |
Enables auto load detection. Variables: 1/pb - Pingban, bans all users with a ping over 'x'.2/hb - Hashban - bans all users with '#' in their names. 0/off to disable. (Example of both ALD modes) |
.ald pb 300
.ald hb |
reload, refresh |
Reloads bot settings |
.reload |
op, giveops |
Gives operator status to a user |
.op Username |
designate, d |
Designates a user |
.d Username |
Access Level 10
isshaman |
Checks if a user is a shaman in the clan |
.isshaman Loud |
save |
Saves all entries |
.save |
wipe, clear |
Wipes a certain element of the bot. Possible elements: chat, bans (banlist) |
.wipe bans |
reconnect, rc |
Reconnects the bot |
.rc |
show/hide |
Shows or hides the exe |
.show; .hide |
setgtrigger, sgt |
Sets the bot's global trigger |
.sgt !! |
load, connect |
Loads a bot profile # |
.load 1 |
unload, disconnect |
Unloads a bot profile # |
.unload 1 |
setrank |
Sets a clan member's rank (1=grunt; 2=shaman) |
.setrank LoudOps 2 |
invites, accept |
Sets the bot's response to clan invitations (1/on accepts, 0/off declines) |
.invites 1 |
sethome |
Sets the home channel |
.sethome ƒuck |
setemail, email |
Sets email account to register accounts to |
.email f@uck.com |
Access Level 11
setserver, server |
Sets the server to connect bots to |
.setserver useast.battle.net |
quit |
Closes bot's exe |
.quit |
open |
Opens a file in notepad.exe (good for editing configs, etc) |
.open config.ini |
*Up to date for Build 27beta
|
- Changelog
Build 25-27beta
- Userlist removed, now all done via arrays
- Interface redone
- Hopefully more stable in flood conditions, still untested!
Build 24 - 25
- Added icon (by AbDuCt)
- Fixed ping loadbanning (Now bans ALL users with ping)
- Bot now reports ping in channel list (PING|USERNAME)
Build 0 - 24
- Just coding it and getting it ready for release...
- About
Note: No, this program will not steal your keys or accounts. Yes, the author can drop the bot. But only on his account, which is on USWest, so USEast users don't even have to worry. Don't even try to brute my account either. -_-
The bot will automatically load profile 0 when started, so please no more "where are the connect buttons?", because it has none, it's all done via commands, stop asking. If you can't figure out how to work this bot, please use another then. Or learn how to use it. Your choice.
Loadbanning system: The loadbanning system on Broken works in such a way that all bots connected ban from the same queue. So this bot will work the most effeciently when you have more profiles loaded on ops from one exe. So, if you're only going to load one bot for ops, this bot will work and everything, but it will ban a lot faster and avoid more double bans if you load like between 2 and 5 ops from one exe. It is also best if all the bots you load ARE on ops. Otherwise it just wastes some code to skip over bots that aren't moderators.
Spamban: As of now (Build 24), the spamban system is still kind of in beta stage, since I have been working mainly on the loadbanning systems. So if it doesn't work as well as you'd like, I'm sorry. If you find it to just not work at all for you, then don't use it, because if you think you're not going to ban anything, why turn it on? It's just more RAM it uses, and it lowers the bot's stability a little bit.
- Known Issues
- No ban/kick queues. Only bans/kicks one user at a time.
- Upon first loading, the arrays will sometimes miss users. Simply rejoin all bots once they are loaded to fix.