mud/
mud/2.4.5/dgd/include/
mud/2.4.5/dgd/std/
mud/2.4.5/dgd/sys/
mud/2.4.5/doc/
mud/2.4.5/doc/examples/
mud/2.4.5/log/
mud/2.4.5/obj/Go/
mud/2.4.5/players/
mud/2.4.5/players/lars/
mud/2.4.5/room/death/
mud/2.4.5/room/maze1/
mud/2.4.5/room/post_dir/
mud/2.4.5/room/sub/
void add_action(fun, cmd, flag)
string fun, cmd;
int flag;

Set up a local function "fun" to be called when user input matches the 
command "cmd". Functions called by a player command will get the arguments
as a string. It must then return 0 if it was the wrong command, otherwise 1.

If it was the wrong command, the parser will continue searching for another
command, until one returns true or give error message to player.

For example, there can be a wand and a rod. Both of these objects defines
add_verb("wave"). One of them will be randomly called first, and it must
look at the argument, and match against "wand" or "rod" respectively.

If seconds argument ("cmd") is not give, it must be given by add_verb().
Support of add_verb() is of historical reasons.

Always have add_action() called only from an init() routine. The object that
defines commands must be present to the player, either being the player,
being carried by the player, being the room around the player, or being an
object in the same room as the player.

If argument 'flag' is 1, then only the leading characters of the command has
to match the verb 'cmd'.

Never define an action that will call the function exit(), because it is
a special function.

See also efun/query_verb, efun/add_verb, lfun/init, lfun/exit