[Bloodlvst]

Originally Posted by Lissa So should it be; //Ban Section exec banned_user.cfg exec banned_ip.cfg writeid writeip or.. writeid writeip exec banned_user.cfg exec banned_ip.cfg

As per asherkin's clarification, it is the first one that I bolded.

[sinblaster]

Lissa it had me stumped for ages, and I still don't understand why all of a sudden I have to use those entries because I had a server setup for 14 months with sourcemod and never had the wipe issue until early this year.

So yeah like Bloodlvst said

//execute ban files exec banned_user.cfg exec banned_ip.cfg writeid writeip

[Larsen]

Does this apply if we're running sourcebans? I know our ip/id's cfg files are blank too and I recall we cleared it 'cuz we thought it was screwing with upgrading sourcebans.

I want us to have these if/when sourcebans gets fudged again.

[Bloodlvst]

Originally Posted by Larsen Does this apply if we're running sourcebans? I know our ip/id's cfg files are blank too and I recall we cleared it 'cuz we thought it was screwing with upgrading sourcebans. I want us to have these if/when sourcebans gets fudged again.

I can't check right now as I'm at work, but I'd believe it does. While SourceBans saves the bans into MySQL, I would think it would need to write them to banned_user.cfg as well fo rthe server to recognize them.

[Larsen]

Just changed it, thanks. Now to hope it saves the sourcebans info to these! Otherwise I suppose it'll start doing it for NEW ip's rather than the old.

*Edit: it not populating I think sourcebans handles it entirely when it's in use. :-/

[Bloodlvst]

Originally Posted by Larsen Just changed it, thanks. Now to hope it saves the sourcebans info to these! Otherwise I suppose it'll start doing it for NEW ip's rather than the old. *Edit: it not populating I think sourcebans handles it entirely when it's in use. :-/

If that's the case, then just simply keep backups of your SourceBans database so you can pull the Steam ID's from it.