ERm, I was under the impression that SENDOK was used to find out if they
can receive information. Mobs have to be able to receive information
(send_to_char, act) or else many triggers won't function.
-B.
At 02:14 AM 7/8/98 -0500, you wrote:
>In the proccess of patching Circle bpl14 with DG bpl12-to-DG3, I came
>across a problem.
>
>The Patch calls for:
>#define SENDOK(ch) ((IS_NPC(ch) || (ch)->desc) && (to_sleeping ||
>AWAKE(ch)) && \
> !PLR_FLAGGED((ch), PLR_WRITING))
>
>
>Stock Has:
>#define SENDOK(ch) ((ch)->desc && (to_sleeping || AWAKE(ch)) && \
> !PLR_FLAGGED((ch), PLR_WRITING))
>
>
>This causes a problem during the init sequence, specifically eqing a mob
>with equipment that it it's forbidden to use(examples in stock world). As
>I make it out, there's no buffer for the message at that point, which is
>acceptable to my senses. My question is what are the ramifications of just
>removing the IS_NPC allowance, or, Why is it there in the patch?
>
> Douglas
>
>
> +------------------------------------------------------------+
> | Ensure that you have read the CircleMUD Mailing List FAQ: |
> | http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
> +------------------------------------------------------------+
>
>
+------------------------------------------------------------+
| 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/15/00 PST