<HEAD> <TITLE> process_input - inspect (and possibly modify) user input </TITLE> </HEAD> <BODY BACKGROUND=http://www.imaginary.com/~beek/gifs/bg.jpg TEXT=#000000 ALINK=#FFFF00 VLINK=#550000 LINK=#000099> <center> <H1> process_input - inspect (and possibly modify) user input </H1> </center> <p> <b> mixed process_input( string ); </b> <p> If process_input is present in the player object, then the MudOS driver will send it a copy of each line the player types. If a string is returned, that string is used as instead of the user input for further processing. If a non-zero, non-string is returned, no further processing is done. If zero is returned, processing continues with the original input. Matching against add_actions is then done. <p> Note: If NO_ADD_ACTION is defined, then there is no more processing to be done after process_input. In this case, the return value is ignored, and the mudlib is responsible for interpreting the string as a command (or other user input for non-command based uses). <p> See also: <A HREF=../../efuns/interactive/add_action.html> add_action </A> <p> <HR> <ADDRESS> <A HREF=http://wagner.princeton.edu/~tim> Tim Hollebeek </A> <p> <A HREF="http://www.imaginary.com/~beek/"> Beek </A>@ZorkMUD, Lima Bean, IdeaExchange, TMI-2, and elsewhere </ADDRESS>