Subcommands

[Chillosophy]

tomozj actually came up with the idea, but I like this more in another way:

[22:14:22] <@tomozj> what about // caps tomozj
[22:14:35] <@tomozj> just /p does stuff, diff cmd for messages
[22:14:38] <@Nakebod> since almost every admin command , related to a player, is available in /p, some with a short alias
[22:14:53] <@tomozj> ./m?
[22:14:55] <@Nakebod> whats the dif with // caps tomozje/id , or /p id/name caps
[22:15:19] <@Nakebod> except that /p is common for everything

We could use // for subcommands. Let me explain this by an example.

For instance, we add /check [playerid]. If a crewmember types this he watches a player like you normally would with /watch, but you get access to subcommands. The subcommands for this command are:

Code:

// watch
// stopwatch
// nuke
// tp (is actually an /mtp)
// mute
// unmute
// cash [amount]
// kick [reason]
// ban [reason]
etc.

If you've used the /check command you have access to these commands. This is easy, because you don't have to remember the playerid or name. It's also faster because it saves a bit of typing.
If you want to 'get out' of the command you can just type another command, like /taxi 0, or use /stopcheck.

This could be used for other stuff as well. Another example is properties;
/property

Code:

// name [name]
// price [price]
// earnings [percentage]
// distance [meters]

Or even the new LVP 2.90 Race builder could use this.

I don't know if I made everything clear, it looks like an easy way to quickly enter a command without remembering id's or names, and in the process saving some time. The /check-command could be a whole new feature request. I've made a request like this about a year ago and I still like the idea of having one command to check cheaters for all different kinds of cheats. The /check-command could be expanded with a textdraw on the bottom of the screen (like in a /race) that shows some information about the player you're currently checking. Stuff like the amount of properties, if or how long a player has been registered, or even spawnweapons. If there's 150+ players on the server and there aren't much admins around this could make checking cheaters more effective.

Implementing this is quite a bit of work, but shouldn't be too hard. There could be an array for all players called "inCommand" which saves the last command (that uses subcommands) along with a player id or property id. In OnPlayerCommandText there could be a check if the player is in a command. If not return false, if so check authorization and do the subcommmand.

If the /check-command is implemented too there could be a simple modmessage like Chillosophy [13] is currently checking Some_Idiot [37]