Secret Santa 2024
Original Post
Useful commands to be added
List of commands which would make everyone's life a thousand times easier:

/channel [op|mute|spec|vip|kick|ban]
Will cause all people joining the channel to be automatically opped, mutes or specced respectively. While op and spec are only somewhat useful, /channel mute would work very similarly to /mode +m in irc, and would be very applicable when running tourneys (how often are you reading out rules to everyone and then three more people join and start talking?).

/autoadd [decap|dm][amount]
/autoaddcap [amount]

The first command, /autoadd, will generate [amount] of tc and add it to either the decap or dm prize pool. The raise will continue until the [amount] specified by /autoaddcap is reached, at which point no more will be added until the prize is claimed. For use in official rooms only (ingame admin only).

/vipall
Command very useful for tourneys due to the unstable nature of the servers. This command allows OPs+ to ensure the tourney participants will always be able to rejoin (unless banned), but the server can't be flooded by malicious users. Combining this command with /maxclients would be effective.

/floodprotect [ban|kick|mute][joins|messages|actions][amount][time] -AND OR-
/floodprotect [ban|kick|mute][joins|messages|actions][rate]

Same idea as /mode +f in IRC. Limits the amount of the specified things a user can do in the room within a given time period before they're banned, kicked or muted.


ok thats all i got boys
Some of these commands are rather complicated. VipAll would lead to rapid server maxes and more likely crashes imo although a lot of commands could use an "all".

The rest seems ok if it's worked out a little better.

For example, ops and mutes should be remembered automatically anyways if at all possible.

and
/autodecapprize
... etc

I love organization ;o
Chickster: I literally don't know why I did it.
Originally Posted by Link View Post
Some of these commands are rather complicated.

Not really a valid criticism imo, people don't have to use the commands if they don't want (obviously we're managing without them rn) - the only complex command would be floodprotect, which in the end would look something like this:

/floodprotect mute messages 5 1

not too hard. The guys mostly using this would be ES guys and perhaps ppl looking to run bet rooms, both of which are commitments in themselves.

Originally Posted by Link View Post
VipAll would lead to rapid server maxes and more likely crashes imo although a lot of commands could use an "all".

Fine, so limit this command to ingame admins - makes tourney management a lot easier and so forth.

Originally Posted by Link View Post
For example, ops and mutes should be remembered automatically anyways if at all possible.

I can get behind this, but I'd also say that auto-X'ing all incoming users is a different function to what you're describing
Last edited by Fear; Sep 8, 2016 at 05:40 AM.
Fine, so limit this command to ingame admins - makes tourney management a lot easier and so forth.

This is what I was thinking about. We set maxclients for a reason. Making everyone a VIP would ultimately make it harder.

Autoing all joining users would be great for muteall and I see what you mean by that there.

Sorry about the "complicated" thing. I should've used a different word that made more sense.
Chickster: I literally don't know why I did it.
Originally Posted by Link View Post
This is what I was thinking about. We set maxclients for a reason. Making everyone a VIP would ultimately make it harder.

Start tourney -> VIP all users currently in room -> set maxclients to 1

now only people who should be entering the room in the first place (people who might be pinging etc.) can join, minimising the likelihood of getting the one user who keeps joining on endless alts to flood the room, attempt to crash the room with join spams etc etc.

So I don't think it'll make it harder.

Maybe I didn't explain this one well, /vipall does not auto-vip all people coming into a room - it vips all the users currently in a room.
Setting max clients to one makes it impossible to have free space. Anyone who wants to join could happen to make the tourney have problems then. It has no minimization on on the likelihood of server crashes. When someone tries to join, they have to get the message that there is too many people in the server and I am fairly sure some connection process is happening there. I could be stupid wrong on that, but I doubt it. I believe server crashes happen the most due to people trying to connect to a max server, but I could still be stupid wrong about that too, however I still doubt it.

Users will not have leniency to join and watch once the tourney starts for a period of time if max clients are set to 1, in which case when max clients could be readded, the vip all thing would be practically useless then.

Giving everyone whos participating in the tourney a free VIP pass is a good idea imo as long as the cons can be overcome. Basically, it could cause even more crashes and issues that it's supposed to prevent at times. Of course, it could work a lot of the time, but I don't know if this could be worth the occasional disconnect and inability to rejoin upon one's turn.
Chickster: I literally don't know why I did it.
code:
<Fear> finally, what about these http://forum.toribash.com/showthread.php?t=572531
(hampa) I've forwarded them

5.x looking toasty