Woof.
 

In light of the recent events that have been amazingly juvenile and, at the same time, amusingly fucking stupid..I propose linking the steam_ID IN GAME to the registration on the forums. Not sure if it's possible since I don't know how these forums handle registration information...but...it would be nifty. This way you could totally avoid rejects that are apparently fucking emo and need to hurry the fuck up and finish the god damned job. Just a thought.


Btw Diamond. Fuck them. You do a damned fine job here in my sad little opinion. This, actually, is the only server I frequent anymore.

Peace, love, and a greasegun round in your ovary.

couldnt have said it better.


not to mention GJ consolidating them into 1 idiot with the beatquik QOTD.


oh and there are other servers?

lol

well i dont exactly know much about the workings of vbulletin.. im sure if i spent some time on it i might figure something out.... plus i dont think i quite understand what you mean about using steamids..

my ovaries!!! :'(

Interactive databasing.
 

Player logs on to the server. He does something neato like /cdrive_register NAMEHERE MYLEETPASSWORD. We yank his steam_ID as an identifier and store that wench somewhere along with his NAMEHERE. This way, we can compare it if some jackass just tries to use different names. In this way, you can have a bit more control over banning someone on the forums. The problem being that the db for the forums/vbulletin would have to interact with a new DB we create or be altered to compensate for the little steam_ID check (wouldn't be that hard under SQL I'd wager). I honestly don't know if all of that made sense..I just woke up.

ahh, i get what you mean now. simply that someone needs their steam account info to log into the forum. that way no one can come in under a new ip or proxy. although im pretty sure it couldnt be done w/o everyone re-registering.

ya thats what i thought you meant lol...

that sounds like an assload of work lmao..

i could use sockets or sql to have the server write stuff to the webserver.. but then having vB check a file or another database when a user trys to register would be a pain in the ass.. and to be honest.. its a pain in the ass i can do without lol.. especially right now

Server-side.
 

If vBulletin uses an SQL database...the only real work would be on the game server. You could just model the output to use the vB DB and add an entry for STATUS_FLAGS or something. Then take down the ability to register on the site. Game server modifies the DB...vBulletin simply uses the information. Of course, I have no clue as to how the information for vBulletin is stored. So, this is all just theory. ;0

wouldnt it just be easier to ban an ip from the forum?

not when ips change all the time