ID:153272
 Aug 4 2004, 8:56 am
|
|
I have a game which I'd like to put up 24/7, but I'm wondering what sort of administrative controls should be coded first. Examples of what I'm talking about include filters to prevent html from being sent via 'say' verbs, and flood controls that prevent players from sending messages larger than a specified amount of letters. What other sort of things does a host need in place before he/she can host 24/7?
| |
SSJ2GohanDBGT wrote:
limit the length of the message to 200 or so. That's just annoying. That would barely suffice a short paragraph...I'd say 750 character limit. Because, remember...it's not 750 WORDS, it's 750 characters, meaning spaces, etc. | |
Yes, but they could put in 750 breaks by copying and pasting them at the end of sentances, couldn't they? I've been looking for a way to prevent that myself.
| |
If the game is going to spend time being up with no staff in it, you could consider a temporary-ban-by-voting system. If X number or X percentage of people playing vote to ban soandso, he'll be kicked out for 2 hours.
Another thing that's nice is a way to record people's bug findings. There could be a BUG verb that opens up a form asking "What happened?" "What should have happened instead?" "What were you doing at the time it happened?" or whatever else you think you'll need, and the info can be appended to a txt file you can check later. Z | |
Garthor wrote:
Replace "\n" with "" Or better yet, with "..." or something similar; that way you get a visual break between lines, so people can still copy and paste messages and not have them all run together. If you do this, though, I also recommend you replace "\n\n" with "\n" first, so you don't have multiple line breaks creating dozens of periods. (hub://Deadron.TextHandling is handy for this, by the way.) Zilal wrote: If the game is going to spend time being up with no staff in it, you could consider a temporary-ban-by-voting system. If X number or X percentage of people playing vote to ban soandso, he'll be kicked out for 2 hours. Gotta be careful with this sort of system, though. People log in with multiple keys and ban everyone they don't like. This used to happen in MLAAS a lot, before vote-to-boot was removed. | |
If the game is going to spend time being up with no staff in it, you could consider a temporary-ban-by-voting system. If X number or X percentage of people playing vote to ban soandso, he'll be kicked out for 2 hours. That isn't too difficult to protect against: given that it is nigh impossible for someone to control multiple keys with different IP addresses, it is safe to assume that anyone who multi-keys will have the same IP address for each of his keys; if multi-keying is allowed in the game, it's still safe to add a restriction by IP address, such that if someone votes to boot with a certain IP address, no other votes from that IP address will work for 30 seconds (or thereabouts), regardless of the person they affect. | |
MSN Instant Messenger limits messages to 400 characters. Occasionally it gets in the way when you're writing a long description of something, but generally it works just fine.
| |
Zilal wrote:
If the game is going to spend time being up with no staff in it, you could consider a temporary-ban-by-voting system. If X number or X percentage of people playing vote to ban soandso, he'll be kicked out for 2 hours. My only issue with this system is that a group of friends could decide they want to be jerks and start kicking people off. | |
A ban code would be good, Crispy's library is extremely nice for that.