On Thu, 9 Dec 1999, Ryan Honeyman wrote:

>
> Good work Kit. I also experimented with Pixie Strike last night
> in the Arena on myself after I died.

Nice bit of research yourself too.

> Since Pixie and Lullaby are so closely tied together in their
> effective impact (stuns a creature) - I am willing to bet there
> was an indirect change a month or so ago which is propagating
> false signals to the objects stun code. (As it stands now,

Mesmerize is a better term. You can wake a creature up from a
mesmerize by hitting it. You cannot with a stun.

You know, now that you mention it, there was a change several
months ago where you couldn't cast certain spells on a
mesmerized mob anymore without waking it up.

> If you try this on yourself, clearly the server is not correctly
> giving you the stun 'command' whatever it may be. I first thought,
> maybe the server is in fact telling the object it is stunned
> but expiring it so quickly that nothing happens. But wouldn't
> you see: You are stunned. You are unstunned. at the same
> time? I would think so. Or maybe telling an object to stun
> for 0 seconds is just skipped since a 0 second stun is obsolete.
> That could be, then no messages would display. But that's if
> the coded it in said way.

Keep in mind GZ has said that mobs have a chance of breaking
out of certain spell effects (e.g. root) every round (I'm
guessing that's 2.5 seconds). Pixie Strike and Lullaby would
definitely fall under that category since they often do not
last their full duration. Assuming that's the case, the 0 sec
Strike would be:

Strike not resisted
Stunned
Roll to see if mob breaks out
Success - mob breaks out
Unstunned

So even a 0 second stun on yourself should be accompanied by
the "You are stunned" message.

So it would seem something is just causing the song not to
work at all, either unrelated to resists, or done via a hidden
resist check for which we get no messages.

--
John H. Kim
kim@...