WC3Banlist 3.1 beta 210 - last change: Tue, 2007-04-06

[Kold_Rayne]

That is too bad, because a great new feature would be automatic spoof checking that kicks players that are using name spoofs. This can be done by issuing a whois command on the username and checking the responses verses the game name. Another great feature would be automatic country checking which kicks players that are not from the specified countries in your banlist preferences.

[ilaggoodly]

You know, these have already been suggested several times and frankly are a bit silly, especially the kick wrong country ones. And you can just spoofcheck by hand, that way you a)be able to type when people are joining the lobby, and b) not get ip/banned for sending too many commands to bnet at the same time

[Kold_Rayne]

You know, these have already been suggested several times and frankly are a bit silly, especially the kick wrong country ones. And you can just spoofcheck by hand, that way you a)be able to type when people are joining the lobby, and b) not get ip/banned for sending too many commands to bnet at the same time

Based on your logic. You must think it is quite silly to even have banlist period. I mean you can just get yourself a paper pad and pen and then write down all the leavers. All you would have to do then is check your list to see if players joining are banned.
Also, you must think the auto-refresh feature (which is included in the beta version) is silly as well since you can manually close all the slots and open them in game.
Oh and the bit about getting ip banned; you must not have any experience programming or using logic to overcome such challenges. The issuing of commands can be timed in order to prevent being spam kicked from b.net.
Oh, and why is the wrong countries one silly? I prefer playing with users from the USA and Canada for numerous reasons (more stable network connections between people in the same region, English speaking for team communication, reduced latency which improves game play for all, etc).

[ilaggoodly]

You don't think that queuing up a user into your blist to be whoised each time someone joins, and having banlist spontaneously type something, which will fail if you type anything, is more convenient than just using a phrase? And check this out, even stealthbot, who's objective is to spit text out cannot completely prevent itself from getting ipbanned for flooding because basically no one knows exactly how blizzard chooses to ban people.
Have you tried using the auto kick function for reserving a slot? Imagine if 4 BR people tried to join your game at the same time, the packet generation would totally get you ipbanned.

[Kold_Rayne]

This conversation is over. You are not suited to discuss programming and the logic behind it.

[heftig]

The way WC3Banlist autokicks requires it to determine whether a player should be kicked very quickly. There is no time to make a query to Battle.net.

[Kold_Rayne]

The way WC3Banlist autokicks requires it to determine whether a player should be kicked very quickly. There is no time to make a query to Battle.net.

This could be modified though as dropping a player from a game is as simple as closing the connection between them and the host.

[heftig]

WC3Banlist would hijack the chatline every time a player joins. That would be disruptive.

[Kold_Rayne]

WC3Banlist would hijack the chatline every time a player joins. That would be disruptive.

I concede that this may be an issue for the spoof check, but the country check wouldn't do this.

how about a spoof check command that can be assigned to a hotkey and can be ran to check the current players and kick spoofers?

I know you can setup custom commands to spoof check now, but there is no way to automatically kick.

[DEATH.TO.ALL.]

Why do you need to, you can spend 2 sec at the most and kick him.
The only people who dont do that are the lazy people who sit on the couch all day eating potato crisps and watching star trek

[ilaggoodly]

for real... the way it works now is certainly satisfactory

[Dimitry_tr]

Hi WC3Banlist users,

I have managed to spend some time on the project in the last days. For now there are only a few new features but a lot of bug fixes:

Bug fixes

the color subs and the colors at the current game tab have been fixed (you need to restore you colors.dat to the original one)
a corrupted messages.xml will not abort WC3Banlist's initialization anymore
WC3Banlist runs as normal process priority now and only switches to high if pings are performed
error messages for failed uploads to Buddies' Banlists are now displayed
false download progress on online lists fixed
added scroll bars for the phrase edit field
fixed strange behavior of phrases with non-ANSI characters
fixed the team ratio variable for custom comments that showed the spectators as team 13
WC3Banlist will now download online lists as gzip/deflate compressed if possible
the local IP addresses will now be fetched by using WinPCap instead of WinSock which should be more reliable
creating bans with illegal characters in the nickname or with nicknames longer than 15 charachters has been made impossible
the number of lines in the chat history has been limited to 100 (bloated messages.xml issue)
the settings for closing WC3 if there is a leaver during the count down will be saved now
comment length of infos and bans uploaded to banlist.nl has been limited to 255 chars to fit into the database
a detailed error message will be played if an upload to banlist.nl fails
the double slash command mode will not prevent WC3Banlist from receiving outgoing whipsers anymore
WC3Banlist is Vista compatible since version 3.1 beta build 183
the setting whether to use the backup of an online list will be saved now

New features

$clipboard and $wait phrase substitutions added (you can create a thread about it, if you don't know to handle them properly)
filtering the local database is done automatically when you're starting to type
possibility to clear old games and scores to reduce the size of the database
possibility to empty the recycle bin on shutdown
WC3Banlist will recognize when a server list has moved to another location and update its database (301 response code needed)
IME has been disabled for the phrase edit field to allow the input of IME codes for non-keyboard characters
server list downloads (XML) will now add a GET-parameter "clientversion" to their requests
added copy functions for the log and the game events at the snooping tab
added support for VIP lists which is a kind of online list containing important players of the community
added an automatic game refresh function with adjustable interval time
if a backup of an online list was used the tab's caption will show the date of the last successful download
now WC3Banlist can directly measure the latency a player will have (available as host only)
new commands /lat, /latlast, /latall

Known issues that come with this version

the colors of the game review are still wrong (will be fixed with the new database coming in March)

Changes during the beta phase:

build 210

- reduced the memory consumption of the IE control that displays the messages tab
- added an error report generator (MadExcept) that can create a detailed error report
- the latency plots will no longer show automatically if you're client
- a defective local database will no longer trigger dozens of access violations
- another try to fix the deadlock that stops WC3Banlist's packet processing and locks the program up at shutdown

build 202

- fix for a possible deadlock on game over

build 201

- fixed automatic game refresh failing if a certain number of games has been played
- the fake players of game refresh will now join a little slower to keep firewalls quiet
- made game refresh work properly on slow PCs (needs testing)
- added a switch to turn on in-game latency calculation (it's disabled by default to lower CPU load)
- some fixes for the overall latency calculation (TCP retransmission caused strange results)
- incoporated heftig's boxplots for displaying the in-game latency (only as host)
- fixed that multiple anti-dl messages were sent if a downloader has been kicked
- /checkall didn't work properly
- WC3Banlist will now show "$freeslots" for $freeslots when not in game
- added $lastkicked for phrases and custom comments, which contains the name of last kicked player by autokick/anti-dl
- fixed that the Warcraft III friend list was always used as autokick/anti-dl exceptions, even if the checkbox at Preferences -> Friend List wasn't set
- /fromall and /from have been rewritten completely and will no longer block WC3Banlist during their web queries
- removed /anyfrom because /fromall supercedes it, so it isn't needed

build 200

- changed the red apple into a yellow one (heftig's idea again)
- fixed hotkeys in maximized window mode
- finally got this UAC awareness going
- made latency comparable to ping in the lobby
- enhanced the flicker protection of the messaging tab
- made the gametimer start and the game-started sound play when loading is done and the game really has begun
- made anti-DL more reliable if players already have parts of the map

build 196

- //banlast fixed
- fixed the tab order of some preferences settings pages (network, db, messaging)
- added parameters "on" and "off" for the /refresh command
- made the VIP message appear and sound play again
- made WC3Banlist UAC-aware
- fixed that WC3Banlist would not appear in front when restoring it from the tray
- WC3Banlist will reset its automatic game refresh timer to zero when the game has been refreshed manually
- a latency column has been added to the snooping tab. it shows the measured latency (PSH->ACK delay) of the TCP protocol
- the number of measurements used for calculating the average latency can be adjusted at Preferences -> Network
- three new commands: /lat, /latall, /latlast (see the commands tab for an explanation)
- a related thread can be found here: viewtopic.php?t=8627
- import of infos from a backup didn't work properly

build 194

- right clicking and selecting "whisper to" will now bring up the correct whisper command at the messages tab
- using commands outside of phrases and adding a $variable to them resulted in strange symbols, fixed
- added an alternative routine to find out the path of the WC3 installation (using registry)
- some more Vista adjustments
- preferences -> database will now show in red when set files or folders do not exist
- added a third way of performing autokicks in the lobby which should be more reliable than the WinPCap one

build 186

- changed the lowest possible game refresh interval to 10 sec
- fixed the pause before the name of the game a friend has joined was copied to clipboard
- altered the refresher's nickname into a red apple (thx to heftig who found out how to do that)
- WC3Banlist will now ignore all refreshers and not identify them as spoofers/same IP (also the standalone AutoRefresh 1.1, I hope - didn't test)
- added settings for changing the source of the /np function (see Prefs -> Misc)
- the game refresh will now be deactivated if the checkbox is not marked
- private games won't be refreshed anymore
- added a /refresh command to trigger refreshing

build 185

- fixed a bug that caused double slash commands not to work in phrases when double slash command mode was enabled
- the setting whether to use an online list backup or not will now be saved
- the online lists tab shows the date of the backup used now
- WC3Banlist is now capable of refreshing a game, the interval can be set at Preferences -> Misc

build 184

- WC3Banlist commands inside of phrase were being ignored if the checkbox saying "Execute WC3Banlist's commands inside of phrases without sending them to WC3" at Preferences -> Phrases was checked
- the tilde (~) in front of commands inside of phrases prevented WC3Banlist from executing them without sending them to WC3's chat

build 183

- fixed the problems with XP when trying to call Vista related security functions
- added Vista to the diagnosis OS detection

build 182

- the hotkey mechanism has been modified to work with vista and it's UAC
- $param will be removed if it's used in a phrase / custom comment but there is no parameter given
- the double slash command mode will not prevent WC3Banlist from receiven outgoing whipsers anymore
- when creating a new custom comment the template edit field will contain "new custom comment" to make it more obvious how this is to be used
- support for the new list type "viplist" has been added, see viewtopic.php?p=70241

build 180

- fixed the delay before copying the name of game to clipboard
- $gamestart added, which stands for the time of day of the last game start
- altered the default pattern for the replay file name to use $gamestart instead of the current time

build 179

- unchecking the checkbox "Combine successive messages as one" works now (see this thread for more information)
- adding bans or infos for nick names that are longer than 15 characters has been made impossible
- added copy functions for the log and the game events at the snooping tab
- server list downloads (XML) will now add a GET-parameter "clientversion" to their requests
This way the server will know which WC3Banlist is used and see if the client can cope with redirections.

build 178

- the IME for the phrase edit box has been disabled, e.g. to make phrases work for Asian users
- the message that informs about a successfully archived replay has been modified to only appear inside of WC3Banlist
- the server lists support redirections now (temporary and permanent, for which the new URL will be saved by WC3Banlist)

build 176

- fixed a bug in the phrase manager, that made it get stuck when pasting a phrase that only contained WC3Banlist commands

build 175

- fixed the IP address detection via WinPCap (some NIC's IP addresses were detected as 0.0.0.0)
This will indirectly fix the empty-player-table-bug.

build 174

- fixed the access violations that occured in the beta
- filenames for replays are trimmed at the beginning and at the end of the filename (spaces are removed)
- the selection in the player table won't get lost if new people join

build 173

- fixed the false colors of the player table's second column

build 172

- fixed $lastbanned and $bannedlist for filename patterns
- clicking the label for cleaning up the scores and games performs the proper action now

The first version of the beta has been released and can be downloaded at WC3Banlist.de. In this forum you can ask questions concerning the beta and discuss necessary changes/bug fixes for the final version 3.1, hopefully coming by the end of the winter.

[thisbanlistlags]

And the point of that post is...?

[Gray]

There is clearly a bug in the beta version as now whenever i press one of the tabs it doesnt change the display in banlist. It always stays on Warcraft III Snooping tab regardless of which tab is selected. I have rebooted my computer and it still does this. Any ideas?

[thisbanlistlags]

There is clearly a bug in the beta version as now whenever i press one of the tabs it doesnt change the display in banlist. It always stays on Warcraft III Snooping tab regardless of which tab is selected. I have rebooted my computer and it still does this. Any ideas?

Have you tried reinstalling banlist 3.0 and the beta version?