UO Second Age

Here's another thread where the issue is briefly brought up in discussion of Paralyze as a spell for use in PvP:

One more comment on paralysis.

You can't paralyze someone while they are casting a spell.

You should have no problems popping a magic trapped pouch and hitting
recall.

Can't recall? Perhaps you should go play on SP.

Corwin

There's also an old Advanced PvP Mage Tutorial from the old UO Power Gamers website that talks about tactics that are dedicated solely to UOR style mages (mostly scribe mages) that talks about paralyze being unable to work on an opponent who is already casting a spell. This indicates that the property still existed at that time on OSI servers, and to me, it also points to a near certainty that paralyze did not do any damage before that point in time on OSI servers, due to the way that disruption was modified with the introduction of UOR.

Also, regarding the 1 damage from paralyze: I think that this thread highlights the dubious nature of relying on player memory for determining exactly when something came in on OSI servers. As of now, we have at least 3 if not more separate guesses as to exactly when this particular feature was first introduced onto OSI servers, but as of now, we have no real concrete evidence one way or the other regarding this property, and without any evidence we can't draw any conclusions on the truth of this property.

I think the 1 damage para thing was 100% in UO:R. I mean in t2a reds would load para and run through instead of exp because of this.

If Para/casting spell issue is correct, wouldn't there be a patch note out that we could search stating they changed it? Most publishes from 2000-2001 are on their site and I can't find it. Just curious what it was implemented.

edit: also from my reading, they implemented a para resist sort of thing later on. I guess to fend off para ganks. Where if you got paraed, then you got a built up resist and couldn't be para or a short period after. I'd assume this was a corrective action to players abusing para during an earlier era.

Ideally, there would be a patch note detailing the fix to paralyze, but unfortunately there isn't any such patch note that I have been able to find. It's possible that such a patch note existed, but was posted under the FYI section of the UO website. A few patch notes from the T2A era were posted under this section of the website at one point in time, but were never directly added to the regular list of patch notes (we never got a full list of what those patches contained before the pages became accessible). The same is entirely possible regarding this change.

1) You couldn't para someone already frozen thats accurate
2) I'm not sure on the 1 damage but it was put in for murder counts at some point to make blue healers take counts.


so the end result should be para gives murder counts and para can not interrupt casting which is what we have. I think it is fine.

Malice, I think u missed the point about Paralyze interrupting spell casting.

From the information put forward in this thread it seems that Paralyze should have a chance to interrupt someone casting a spell (depending on the circle they are attempting to cast) but not actually paralyze them, instead they should remain frozen for the duration of the spell they are casting then give the system message "You can now move" at the end of the spell casting.

For example, casting an 8th circle summon daemon spell takes a significant amount of time to cast, roughly 13 seconds, if you are paralyzed while casting it should interrupt the spell but the caster is to remain frozen for the full 13 seconds(ish).

That or it completely stops the spell casting process and gives the "You can now move" message. I'm not sure exactly how its supposed to function there.

I'll clarify what information we know from the demo regarding paralyze and its interaction with spell casting.

When a player casts a spell, they go through a casting process that checks a number of things at the beginning the casting process, including whether they have the required reagents, their hands are empty (or are only holding a spellbook), and whether they have the required mana. If the player meets the requirements, the spell begins the casting animation (the "spell pump" animation). During the casting animation, a flag is set on the character that freezes them in place for the duration of the casting animation, and this flag happens to be the same flag that is set when a player is paralyzed.

This casting animation process is handled by a specific script in the demo that also has event handler code that is triggered whenever a player is hit. This means that at any time there is an event that counts as a player being hit by something, a signal is sent to the scripts alerting them to the fact that such an event happened, and that they should execute any blocks of code they have that are intended to trigger when something is hit. It is through this type of code that spell disruptions, finger slips on bandages, and angered animals for taming are handled in game.

The event handler code in the casting script takes the input of how much damage that the player was hit for and the circle of the spell being cast, and runs a calculation using those values and the skill of the person casting the spell to determine whether the spell is disrupted. If the spell is successfully disrupted, a specific piece of code is run that cancels the casting animation, unfreezes the caster, and sends the disruption message to the caster. It is the interaction between the casting script and the paralyze script that makes it impossible to paralyze someone who's casting a spell.

Now, the paralyze spell itself is rather straight forward. The spell first determines how long the spell should last for, sets the frozen flag on the victim, does a hit of zero damage on the victim, and then sets up another script that is intended to unfreeze the player after the prescribed period of time. As a result of this order of operations, the effect of paralyze when combined with the spell casting script is the effect that a player cannot ever be properly paralyzed.

To better understand why it works this way, let's consider 3 different scenarios: a normal spell cast, a normal paralyze cast, and a paralyze cast on someone who is already casting a spell:

Normal spell cast

• Player A tries to cast a spell.
• Checks are made to see if the player has the reagents, the mana, and the empty hands to cast the spell.
• The spell casting script takes over at this point.
• The player has the frozen flag set to true on the caster, with a delay of the length of the spell being cast.
• The spell animation begins.
• The words of power are spoken.
• After the set delay, the frozen flag is set to false on the caster, and the target cursor is presented for the loaded spell.

Normal paralyze cast

• Player B targets Player A with a paralyze spell.
• The paralyze spell script calculates the duration of the paralyze effect for Player A.
• The frozen flag on Player A is set to true.
• A hit for 0 damage is done to Player A.
• A "paralyze management" script for Player A takes over, issuing the "You can not move!" system message to Player A.
• After the duration of the paralyze, the paralyze management script sets the frozen flag to false for Player A, and sends the "You can move!" system message to Player A.

Paralyzed while casting a spell

• Player A tries to cast a spell.
• Checks are made to see if the player has the reagents, the mana, and the empty hands to cast the spell.
• The spell casting script takes over at this point.
• The player has the frozen flag set to true on the caster, with a delay of the length of the spell being cast.
• The spell animation begins.
• The words of power are spoken.
• Some period of time passes that less time than the duration of the spell.
• At this point, Player B targets paralyze on Player A.
• The paralyze spell script calculates the duration of the paralyze effect for Player A.
• The frozen flag on Player A is set to true (which is already set to true due to casting a spell).
• A hit for 0 damage is done to Player A.
• The event handler code in the casting script for Player A is triggered.
• A calculation is made to determine whether the spell is disrupted or not.
  
  • If the calculation "succeeds" the spell is disrupted.
    • The disruption system message is sent.
    • The frozen flag on Player A is set to false.
    • The casting animation cancels, and the spell is now disrupted.
    • A "paralyze management" script for Player A takes over, issuing the "You can not move!" system message to Player A (but they can move since a spell was just disrupted!).
    • After the duration of the paralyze, the paralyze management script sets the frozen flag to false for Player A (which is already false because the spell was disrupted), and sends the "You can move!" system message to Player A.
  
  
  • If the calculation "fails", the spell is not disrupted.
    • A "paralyze management" script for Player A takes over, issuing the "You can not move!" system message to Player A.
    • Shortly thereafter, the casting script completes the cast of the spell, the frozen flag is set to false on Player A, and the target cursor is presented for the loaded spell.
    • After the duration of the paralyze, the paralyze management script sets the frozen flag to false for Player A (which is already set to false as a result of the completed spell cast), and sends the "You can move!" system message to Player A.

As you can see from the third series of events, there are two possible outcomes labeled in green and red based on whether a spell is disturbed or not by the paralyze hit. However, in both cases, the frozen flag which is manipulated by both the casting and paralyze scripts is set to false long before it should be set to false as a result of the natural end of paralysis. The only difference is a small difference in total time frozen, and whether the spell caster does or doesn't have a spell to cast once they are free to move. Incidentally, in both cases, there will be this odd "You can move!" message that appears when the caster would normally be unfrozen by the paralysis management script, but the player will be moving freely when that message is received.

I hope that this clarifies what we know about paralyze thus far.