Jump to content

Bug with opcode 33- Stat: Save vs. Death Modifier


Recommended Posts

Posted (edited)

Hey,
I found a tricky bug with opcode 33. I couldn't find any information about it.

With Type 3, the saving throw is modified as Type 0 moreover the instant saving throw is also modified.
The "normal" ST is correct but the "instant" ST modifies the save vs. Wands instead of save vs. Death.

A few tests can show this :

  1. A character with all ST at 20
  2. A spell with two effects

 

  1. First effect is one opcode (between 33 and 37) with type 3 and value to -20.
  2. Second effect can be negate by one ST.

The character will have a only one ST at 0 (thanks to the first effect). He can only success against one specific ST and fails all other.

It's pretty simple :

  1. If the first effect works and protect against the ST of the second effect, the ST succeeds.
  2. Otherwise, the ST fails.

 

  • A simple case : no help : all ST at 20
- Only one effect : no opcode 33-37
- Effect with negate Breath ST

⇒ Expected result : the ST fails
⇒ Result obtained : the ST fails

 

  • A basic case : opcode 36 is adding and protect against the second effect
- Opcode 36 (Breath) : type 3, value -20
- Effect with negate Breath ST

⇒ Expected result : the ST succeeds
⇒ Result obtained : the ST succeeds

 

  • Buggy case : same case but with opcode 33 and Death ST

Now, I change the ST opcode (36 (Breath) ⇒ 33 (Death)).

And I change the ST of the second effect (Breath ⇒ Death).

- Opcode 33 (Death) : type 3, value -20
- Effect with negate Death ST

⇒ Expected result : the ST succeeds
⇒ Result obtained : the ST fails

 

  • WTF case : same case but with Wands ST

Now, I change the ST of the second effect (Death ⇒ Wands).
The opcode 33 (Death) does not change.

- Opcode 33 (Death) : type 3, value -20
- Effect with negate Wands ST

⇒ Expected result : the ST fails
⇒ Result obtained : the ST succeeds

 

 


Note : This bug ONLY affects the immediate bonus so it is not visible on the character's screen.

 

Edited by rivvers
Link to comment
Posted (edited)

Ho thanks ! So I'm 6 years late !
Since the bug is known and checked in the last game version, it might be useful to add this information to iesdp ?

Edited by rivvers
Link to comment

I would be happy to propose a PR directly. But it's not easy to explain concisely. Moveover, my english is not very good.

I would propose a new formulation for the Type = 3 because its effect is twofold. So it will be easier to explain what's going on if we split it.
1. Update instantly the ST, the other effects on the stack take account the new ST value
2. Apply the Type = 0

On opcode 33, the first step changes the ST vs. Wands while the second step changes the ST vs. Death.


The problem exists since at least the version 2.5. For me, it looks like a dev mistake, so it's probably always been there, or « since implementation » like kjeron said.

Link to comment

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...