You're going to have to create a ban system of some sort and it just so happens that I wrote a couple of blogs about a month ago on how to create a decent one. You can check them out here:
Like I said at the end of part 2, I apologize for any small syntax errors. I typed those up pretty quickly. I skimmed through the SQL code and I think the problem is this line:
length varchar(25)
There needs to be a comma at the end of that line.
It's my job to help the next generation, and set a good example for them. And for that I'll gladly lay down my life.
Sessions expire when the user closes their browser. Bans shouldn't use sessions. What they do is compare the current date and/or time with that of the ban time in the database. My ban system bases its ban time off of the time() function.
It's my job to help the next generation, and set a good example for them. And for that I'll gladly lay down my life.
From the mention of Overlords and chatmins, your website concept doesn't sound profoundly "unique" as you would call it.
Also, for the record, given that browser cookies can be very easily deleted, using them to store ban information is one of the absolute worst ways to ban someone.