> Well, if I remember right, hit assumes that the character is still
> alive - among other things. The more likely the character is to be dead
> at somepoint internal to the loop, the more likely the loop is to
> attempt to act upon an already dead (and memory extracted) victim. Access
> data in an extracted character, and the mud crashes. Eventually.
--sn--
I'm glad you brought that back to my attention, I thought I'd avoided the
absent ch
scenario, but I was assuming that hit() checked the state of victim.. that
fixes the
"repeated use" crash I had found. Actually, I think it fixed the 50+ loop as
well.
*sigh* :)
--sn--
> As for the overflow, that's because you're trying to output too
> much data - at least, larger than MAX_STRING_LENGTH.
--sn--
Hmm I take it then that send_to_char is queued for output, hence the loop
(which
uses send_to_char and act) is causing an overflow? Are there consequences to
fiddling with MAX_STR_LENGTH that I should be cautious of?
Regards,
Kristof
+------------------------------------------------------------+
| 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 : 04/10/01 PDT