STEAM GROUP
SourceBans sourcebans
STEAM GROUP
SourceBans sourcebans
55
IN-GAME
316
ONLINE
Founded
August 6, 2007
Language
English
New Steam ID system
Sourcebans needs an update to be able to accept and enforce bans using the new Steam ID system. True to their nature, Valve broke a bunch of things in yesterday's update without warning anybody, and that left a bunch of gaming communities vulnerable. AlliedModders issued a band-aid fix for Sourcemod that will translate between the two Steam ID formats, but the new format is still not accepted by the Sourcebans Web panel. For a while before the Sourcemod update, Sourcebans was completely unable to enforce bans, and many servers were full of banned players wanting revenge. I'm not 100% sure the Sourcemod update fixes the problem of bans not being enforced, but for now, Admin permissions seem to work.
< >
Showing 1-2 of 2 comments
quake Aug 22, 2014 @ 3:24pm 
SourceMod core patch that was applied converts old IDs to the new ones. This, afaik, means that bans should still work as SourceBans gives the old SteamID to block to SM, and SM converts it to the new one, resulting in a ban at all situations. If adding a web ban, just use this 'formula'
Let's say user's ID is U:1:X,
If X is divisible by 2, his old Steam2 ID will be STEAM_0:0:X/2,
If X is not divisible by 2, his old Steam2ID will be STEAM_0:1:(X-1)/2
Bans (at least for me) work after installing the newest sourcemod snapshot, and so do admin permissions.
Hope I helped in a way C:
That might work. I haven't had any banned players connecting to my server, thankfully. It just seems so odd that they would forget to announce that they were going to be changing everyone's Steam IDs. Like, maybe they should let people know before they blow something up. Instead they made AlliedModders devs rush to apply a fix.

"BOOM!"
"What the fu<k was that?"
"Oh, sorry. I forgot to tell you. I'm demolishing the building now. You should probably get out. Like, five minutes ago."
< >
Showing 1-2 of 2 comments
Per page: 1530 50