rivvers

There are many special cases: no rule can explain everything What I notice about special cases is that the damage bonus is the most useless part of the equation. It's the most changeable value and most +N values can be explained without it.

True, i have misread the description, I read STATE_SLEEPING twice. My bad. ok I assume this has been patched to 2.6 True again. It can remove the stun of opcode 210 but not the opcode 210 directly. Thanks to you, I'll correct my post

hey, I would like to make some minor additions Opcode 2 First one. Opcode 3 Type == 1 : Sets BERSERKSTAGE2 to 1 Opcode 24 This opcode set the STATE_PANIC flag Opcode 25 This opcode set the STATE_POISONED flag it is rather : HP >= 100 / 'Amount_1' If Amount_1 == 1, damage is dealt until HP == 99 If Amount_1 == 2, damage is dealt until HP == 49 If Amount_1 == 99, damage is dealt until HP == 1 If Amount_1 == 100, damage is dealt until death Opcode 38 On EE, bard's song has no effect Opcode 45 Sets HOLD to 1 Opcode 46 also remove opcode #109 and opcode #210 Opcode 47 Removes opcode #20 Does not affect creatures with STATE_NONDETECTION Opcode 48 Removes opcode #38 Opcode 50 First byte = Location Not implemented on version 2.5, maybe only on 2.6 ? if you have any questions, please do not hesitate

Hey, I'm coming over personally. My apologies for the delay. Thank you JohnBob for posting my remarks and lynx for checking and taking them. Before I start, this information is from decompiling and testing on version 2.5. I am far from being an expert, but unless I make a personal error or change in version 2.6, the information is quite reliable. I should point out that my English is so-so. I did some « not good » testing at the time but what I know is that these choices are not implemented in the game engine. For some opcodes it works fine : 55, 109, 175, 177, 185, 238, 283, 319... But not for the following ones: 100, 178, 179 & 219 Maybe it is a bug but it is easy to test. Effects with Type 6 are cumulative, like 0. This mode is used internally by opcode 12, for flags 7 & 8. And, yes, these effects are not cumulative. BUT this restriction is configured in opcode 12, not in opcode 18. So, this mode does not stack if used by opcode 12 because opcode 12 checks if a mode 6 effect is active but if used directly from opcode 18, there is no restriction. Fake or patched. Thanks to you