The second place to check for commands is the player himself. Any of these steps can be skipped if the context was the same as the element about to be checked. The player object has some basic commands, such as 'tell' and 'remote', as well as player account setting commands, such as 'title', and actions, such as 'look' or 'examine'.
Next comes the players location. These commands are effects like 'say' or 'shout', actions, such as 'lock', and modifications, such as 'description' (to edit the rooms description). Note that a command like 'description' will almost certainly be overridden by the player step. This means that the only way to change the description of a room is to set it as a context.
Now we can step through the commands available from the various groups a player can be a member of. Many groups will have channel commands 'a:' 'a~', and some will have additional commands available, such as 'enroll', or 'delete'.
Finally, we check the system command list, for anything else. Commands listed here are like 'who' or 'time', and can generally be executed by anyone connected. There is a possibility of allowing these commands to be executed from the login prompt (ie, anonymously).
| tell . > | Send a private message to another user or set of users |
| remote , < | |
| rthink rt | |
| title | |
| description | |
| plan |
| say ' " | say something so that everyone in the room may hear |
| emote ; : | |
| think ~ | |
| shout ! |
| time | A measure of how long the system has been up (some statistics) |
| finger | (or lastlog, or something), which would indicate the last time a certain player connected, and possibly some other information about them |
| who | list the players online atm |
| help | start referencing the forest helpfile system |