[lester]

Thank you for your quick answer.

Try %N now.

[TUSK3N1337]

So If im vac banned on CS 1.6 and source wich I am I wont be able to play on a server that has this in cs:go? right?

[StevoTVR]

Originally Posted by TUSK3N1337 So If im vac banned on CS 1.6 and source wich I am I wont be able to play on a server that has this in cs:go? right?

Yes

[2NASTY4U]

German translation updated. Because Sillium's translation is just a word to word translation. My translation is grammatically correct and makes sense.

[Bubka3]

In this plugin, line #321, why are you using the ServerCommand native to ban someone? That is unsafe at worst and unsanitary at best.

Use the BanClient native; http://docs.sourcemod.net/api/index....d=show&id=295&

[ecca]

Plugin came out 25th Nov 2008, i'm not sure if this was his first plugin back then.

Edit: Saw it's been updated a few times, tho he's using a safe version of servercommand banning since he's getting client ID and not name.

[StevoTVR]

Originally Posted by Bubka3 In this plugin, line #321, why are you using the ServerCommand native to ban someone? That is unsafe at worst and unsanitary at best. Use the BanClient native; http://docs.sourcemod.net/api/index....d=show&id=295&

I used the server command so custom ban management plugins like SourceBans can catch it. As far as I know, the native will bypass those and go directly to the local ban list.

[Bubka3]

Originally Posted by StevoTVR I used the server command so custom ban management plugins like SourceBans can catch it. As far as I know, the native will bypass those and go directly to the local ban list.

SourceBans 1.5 and 2.0 catch BanClient() just fine. SourceBans 1.4 has an optional native you can add to check if its loaded and ban using that. You really shouldn't be using ServerCommand. If I don't have sm_ban this plugin will fail.

[StevoTVR]

Originally Posted by Bubka3 SourceBans 1.5 and 2.0 catch BanClient() just fine. SourceBans 1.4 has an optional native you can add to check if its loaded and ban using that. You really shouldn't be using ServerCommand. If I don't have sm_ban this plugin will fail.

I checked and the SBBanPlayer native doesn't exist after 1.4, so I guess using it would fail on 1.5 and 2.0. Unless there is a better way that still works with all versions of SourceBans, I'll stick with the ServerCommand hack.

How common is it for people to run without sm_ban anyway?

[cb684]

Getting the following error after today's Halloween update. (Windows server)

L 10/30/2014 - 12:50:01: SourceMod error session started L 10/30/2014 - 12:50:01: Info (map "sd_doomsday_event") (file "errors_20141030.log") L 10/30/2014 L 10/30/2014 - 12:50:01: SourceMod error session started L 10/30/2014 - 12:50:01: Info (map "sd_doomsday_event") (file "errors_20141030.log") L 10/30/2014 - 12:50:01: [SM] Native "ReadPackString" reported: DataPack operation is out of bounds. L 10/30/2014 - 12:50:01: [SM] Displaying call stack trace for plugin "vacbans.smx": L 10/30/2014 - 12:50:01: [SM] [0] Line 135, vacbans.sp::OnSocketConnected() L 10/30/2014 - 12:50:21: [SM] Native "WritePackString" reported: Invalid data pack handle 0 (error 4) L 10/30/2014 - 12:50:21: [SM] Displaying call stack trace for plugin "vacbans.smx": L 10/30/2014 - 12:50:21: [SM] [0] Line 162, vacbans.sp::OnSocketReceive()