Re: [Circle] Spec Procs + Spec Commands.

From: Daniel Staudt (
Date: 02/14/00

i just added a command
{ "stop_commands_menu_here", 0, 0, 0, 0 },
and put any commands i didn't want on the command menu after this
then in acmd(do_commands)
changed num_of_cmds to an int
max_cmd=find_command("stop_commands_menu_here") and changed the for loop
with it. so the loop stoped right before the max_cmd and hide all the
'special' ones

>From: Patrick Dughi <dughi@IMAXX.NET>
>Reply-To: Circle Discussion List <>
>Subject: [CIRCLE] [Circle] Spec Procs + Spec Commands.
>Date: Mon, 14 Feb 2000 08:48:18 -0600
>         Sometimes it's the little things that count.  For example, there
>are a few instances in which we had spec_procs that had to use the 'pull'
>command.  For most of the rest of the mud though, the command is linked to
>the 'do_not_here' function, with a rewarding "Huh?" message.
..snip snip..
>         Exciting, but mostly simple.  The only thing you may want to do is
>to convert your existing spec_procs which perform actions on a random/time
>based system to check not just for !cmd, but for !cmd && !command - else
>each nonsense command in a room could potentially trigger the non-command
>spec_proc functionality, like playing cards or the mayor's walking path.
>For the most part though, I doubt this will be a serious problem.
>                                         PjD
>      +------------------------------------------------------------+
>      | Ensure that you have read the CircleMUD Mailing List FAQ:  |
>      |  |
>      +------------------------------------------------------------+

Get Your Private, Free Email at

     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  |

This archive was generated by hypermail 2b30 : 04/10/01 PDT