3d93825f84, SVN 1799: Ribose (2010-10-17) (8 changed files, +182, -108)
<pre class="formatted">- Fixed a bug where users with "no stats available" on WarCraft III were given a druid icon.<br>
- Repairing overrides now works (before it was putting them in Main insteadof Override).<br>
- Updating overrides from the site now works for Diablo II: LOD (stopped working due to the changes made to the logon system).<br>
- Changed the @[tab] system again so that only the "other" gateway is suggested and not both (if you are on USEast it will give you Azeroth and not USEast and Azeroth; if you are on Azeroth it will give you USEast).<br>
- Added the .setbnlsserver command.<br>
- Added the [Override] PredefinedGateway. Setting it to some value will make the bot skip the /whoami check and assume the @Gateway is the one given. This is useful for PvPGN users.<br>
- Corrected phrasing in clan command errors.<br>
- The "No Timestamp" option has been fixed.</pre><br><br>
350e85ca7c, SVN 1797: Ribose (2010-09-23) (7 changed files, +216, 138)
<pre class="formatted">- Fixed a bug where when Diablo II naming conventions are on, it's impossible to give access to users (it expects a username with a " " or a "*" in the database check, which is impossible or insecure due to wildcards).<br>
- The username used in command processing is now strictly limited to account name only for Diablo II naming conventions users.<br>
- If you have the Blizzard Representative (0x01) or Battle.net Administrator/SysOp (0x04) flag, you are now considered to "have ops" (.IsOperator = True) so that PvPGN bot owners who fail to apply the op flag can do kick and ban functions using StealthBot.<br>
- When you type @[tab], the available auto-completions is limited to your gateway only. This feature supports the beta.battle.net gateway now.<br>
- When Diablo II naming conventions are enabled, and the add command is used with the format ".add *user" (where no other wildcards are present), the bot will assume the user means to add "user" and remove the star. To add a tag, you may do ".tagadd *tag" instead.<br>
- When Diablo II naming conventions are enabled, and the add command is used with a character name found in the channel, the bot will assume the user means to add the user in the channel's account. If an account name also exists with the same name as that character, this is not done.<br>
- Changed the logon system after account logon to do less spam and always retrieve the BotVars.Gateway correctly.<br>
Old system:<br>
On account logon complete:<br>
Send SID_ENTERCHAT<br>
Send SID_GETCHANNELLIST<br>
Send SID_JOINCHANNEL (home:#, makes the bot join an in-limbo "void" where /whoami will return gateway)<br>
Send SID_CHATCOMMAND (/whoami)<br>
On response to SID_ENTERCHAT:<br>
DISABLE user in channel-type events (see
revision 1497)<br>
Send SID_JOINCHANNEL (home as firstjoin, normally joins game-specific channel instead)<br>
Send SID_JOINCHANNEL (home)<br>
PADQUEUE<br>
EVENT LoggedOn<br>
On join home or silent in SID_CHATEVENT:<br>
ENABLE user in channel-type events<br>
Problems with this old system:<br>
If /whoami gets processed by Battle.net fast enough, you don't get a response because you haven't entered chat at all yet. I've noticed this causes BotVars.Gateway to have no value and naming conventions does not work.<br>
If the game-specific "home" happens to be the home channel that you provided in settings, you are spamming Battle.net with one extra join-channel command. Since this is unnecessary, it leads to the old problem of flooding off easier after logging in more than it helps anything.<br>
New system introduced:<br>
On account logon complete:<br>
Send SID_ENTERCHAT<br>
Send SID_GETCHANNELLIST<br>
Send SID_JOINCHANNEL (home:#, makes the bot join an in-limbo "void" where /whoami will return gateway), SID_CHATCOMMAND (/whoami)<br>
On response to SID_ENTERCHAT:<br>
DISABLE user in channel-type events (see
revision 1497)<br>
Send SID_CHATCOMMAND ("/whoami")<br>
On server info in SID_CHATEVENT:<br>
Send SID_JOINCHANNEL (home as firstjoin, normally joins game-specific channel instead)<br>
PADQUEUE<br>
EVENT LoggedOn<br>
On join channel in SID_CHATEVENT:<br>
if channel is home or silent:<br>
ENABLE user in channel-type events<br>
if NOT:<br>
Send SID_JOINCHANNEL (home)<br>
Problems with this new system:<br>
PvPGN servers may not respond the same or at all to /whoami, and the bot will STOP waiting for it! Use /fj after logon if this occurs.<br>
<br>
This system adds two extra steps to logon so that it should always work (on official servers) and does not spam as much (especially for WC3 bots who set their home to their clan channel).</pre><br><br>
cc041fd23c, SVN 1796: Hdx (2010-09-23) (1 changed file, +74, -73)
<pre class="formatted">Implemented SSC.GetDBEntry().BanMessage Thread
#5016</pre><br><br>
654a597a07, SVN 1795: Ribose (2010-09-11) (6 changed files, +44, -30)
<pre class="formatted">- DRTL users with non-valid statstrings now show up with the DRTL icon.<br>
- DSHR users with valid statstrings now show up with the (added) gray warrior icon. All DSHR official clients are warriors.<br>
- You can now override the statstring sent in SID_ENTERCHAT/0x0A using [Override] SetBotStatstring= for DSHR and DRTL stats.<br>
Ex: SetBotStatstring=LTRD 99 2 3 100 100 100 100 99999 0<br>
Ex: SetBotStatstring=RHSD 1 0 0 30 10 20 25 100 1</pre>