I know what you mean about it being nutz. but since I was planing on
implementing this call throughout the skill code i created this macro:
#define CHECK_WAIT(ch) ((!IS_NPC(ch))? \
(((ch)->desc) ? ((ch)->desc->wait > 1) : 0 ):\
(GET_MOB_WAIT(ch)>0))
I know it looks nasty and icky, but do you see anything wrong but a bad code
style?
--Angus
______________________________ Forward Header __________________________________
Subject: Re: Re[2]: Re[2]: Mob fleeing
Author: INTERNET:CIRCLE@post.queensu.ca at CSERVE
Date: 10/28/97 12:31 PM
>>>#define CHECK_WAIT(ch) (((ch)->desc) ? ((ch)->desc->wait > 1) :\
>>> (GET_MOB_WAIT(ch)>0))
>>
>>The stock one is:
>>#define CHECK_WAIT(ch) (((ch)->desc) ? ((ch)->desc->wait > 1) : 0)
>>
>>Hence the work around.
>
>damn, guess that should be changed and not worked around. another patch george?
>or is there a reason not to check the mobs wait state if the char is a mob?
>bother, why the &#!! was wait stuck onto the desc? timing out during load?
>argh.
The mob wait variable is in the mob_specials structure.
The player wait variable is in the descriptor.
The macros are mob and player specific so you have to test both.
The whole thing is just nuts, I'm waiting on major projects to see what
bpl12 entails.
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/08/00 PST