We indeed had a lengthy discussion about this on IRC yesterday, and there are definitely some interesting things to consider. Fact is though that SourceBans has had a public ban appeal/request system for 6 years, and I haven't heard a single complaint of abuse. So for me it would be more about convenience (people not knowing or having to look up their Steam ID) than protection. And I agree that requiring them to register and remember yet another username and password would most likely scare people away, so using Steam login would be a nice middle ground.

If not done already, I'd like to see a method employed that'd let us change ServersIDs instead of editing the various MySQL tables directly.

Server IDs are generated and used internally, so unless I'm misunderstanding you, you shouldn't be changing them. They're also not displayed on the web anymore, and the SourceMod plugin has been switched to using the server's IP address (which it attempts to detect).

I have added some screenshots of the administration pages to the first post, for people who don't feel like installing it. Also thanks to everyone for the positive feedback, it makes the work worthwhile

Server IDs are generated and used internally, so unless I'm misunderstanding you, you shouldn't be changing them. They're also not displayed on the web anymore, and the SourceMod plugin has been switched to using the server's IP address (which it attempts to detect).

I have added some screenshots of the administration pages to the first post, for people who don't feel like installing it. Also thanks to everyone for the positive feedback, it makes the work worthwhile

That'll be helpful, thanks. With SourceBans 1.4 it's a bit more external. Originally we used Servers IDs 1-9 however after deleting 4-6 to move to another machine, it wouldn't reallocate those IDs and instead uses 10-12. Changing them in MySQL should be fine as long as I'm through in checking every table. Or I could switch to SourceBans 2.0 now and save myself some hassle. How stable it is so far?

That'll be helpful, thanks. With SourceBans 1.4 it's a bit more external. Originally we used Servers IDs 1-9 however after deleting 4-6 to move to another machine, it wouldn't reallocate those IDs and instead uses 10-12. Changing them in MySQL should be fine as long as I'm through in checking every table. Or I could switch to SourceBans 2.0 now and save myself some hassle. How stable it is so far?

I would say is stability is fair. It is more feature rich but is up to you, ultimately there is no upgrade install yet so you will have to install fresh and export old bands to import them and probably readd admins. I would at least get the move process to see if all of those features work properly before making it live.

@11530: So it's kind of an OCD thing? ;) You can also use the 1.5 plugin, it's exactly the same as the 2.0 plugin but it works with the old database structure. Under "Changes" there's an explanation of the ServerIP option.

@11530: So it's kind of an OCD thing? ;) You can also use the 1.5 plugin, it's exactly the same as the 2.0 plugin but it works with the old database structure. Under "Changes" there's an explanation of the ServerIP option.

Very likely. I'd much prefer my servers using 1-to-9 than 1-to-3-and-7-to-12 I'll probably check out the 2.0 so I know what database structures to expect. Thanks for this too by the way - one of the most useful plugins out there.