At 01:07 AM 1/24/98 -0800, you wrote:
> This really isn't a bug, as it makes sense, but I thought I'd warn
>anyone who didn't know. I just spent about 2 and a half hours looking for
>the reason my MUD was crashing, and it seems to be that someone made a
>random trigger on a mob, and used the %actor.name% variable with it.
>Obviously you can't do this, but DG scripts should ignore it...well, it
>doesn't. It just crashes your MUD.
I have a hard time beliving simply using %actor.name% in a random trigger
crashes your mud (especially since I have a coder that did it too without
crashing us.) I would be more prone to believe that using it as the argument
to a specific command might crash you. Could you post your trigger or the
command that crashed so it can be determined if the problem is local to you
or one that affects everyone?
The reason simply using %actor.name% in a random trigger is really not
something to be alarmed over is "actor" is not a keyword; it's merely a
variable that is pre-set for relevent triggers. If it, in itself, crashes
you, this
either means that using an undefined variable crashes you or trying to
reference
a field in an unused variable crashes you. (I tested both of these and didnt
crash.)
+------------------------------------------------------------+
| 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