[ThantiK]

Hell, I wouldn't be running 100 servers...maybe a max of 5...lol

And you wouldn't need to be checking it on an interval. You check it on client_infochanged and client_connect

People dont change their names anywhere near every 24 seconds...and querying the mysql server 100x every 24seconds, (in your worst case scenario)...is what mysql was meant to do.

[Dygear]

Originally Posted by ThantiK Hell, I wouldn't be running 100 servers...maybe a max of 5...lol And you wouldn't need to be checking it on an interval. You check it on client_infochanged and client_connect People dont change their names anywhere near every 24 seconds...and querying the mysql server 100x every 24seconds, (in your worst case scenario)...is what mysql was meant to do.

I was thinking more of like baning there SteamID's, witch means that client_infochanged would not be needed for SteamID's b/c that does not change. As for there names that can be read from a text file, and then you could use client_infochanged, b/c hitting the server eveytime the client changes there name is not good for the db, even if it is only for 5 servers. Then you can Ban there SteamID's and not see them on your other servers. And the more servers we have hooked up to this the better ... I could like make a MySQL db on my webspace (when i get it) and then set it up so that there would be like a MAX of 100 servers on each db.
Then ervy night at 12:00pm a php doc would then do a search on each db for steamIDs they dont have and integrate them into there tables.. But when it gets to that point it goes beyond my abilities by far.

[FroXeN]

lol be funny if mygoat people changed there name to this.
MeYouGOwingTargetS - Bob

lol

[ThantiK]

Yea, I would like to ban by ip/steamid, but also check for certain "no-no-names"