Having STATE_x is better for more than just MOUNTED. You should also look at putting STATE_SLEEPING, STATE_STUNNED, etc for these. Since you can be sitting and alseep, they should be 2 different things. You'll just need to add in some macros and check throughout the code for checked against GET_POS since they use <, >, or = and make the appropriate changes. Rick -----Original Message----- From: Edward J Glamkowski <eglamkowski@angelfire.com> To: CIRCLE@post.queensu.ca <CIRCLE@post.queensu.ca> Date: Friday, February 05, 1999 4:47 PM Subject: positions >Having just added mounts to my mud, I added in a >POS_MOUNTED to allow for certain skills that can be >used only from horseback (e.g. a jousting skill). >To this end, I am thinking of making fighting a state >instead of a position so I can have players engaged >in combat while remaining mounted. > >But before I do this, I would like to hear opinions on >making such a change. The alternative would be to >create an additional position POS_MOUNTED_FIGHTING >and everywhere it currently checks for POS_FIGHTING >have it also check for POS_MOUNTED_FIGHTING. +------------------------------------------------------------+ | Ensure that you have read the CircleMUD Mailing List FAQ: | | http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html | +------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST