Potion of Invulnerability
OurQuestIsVain
Member Posts: 201
Current behavior - The potion of invulnerability, which can be obtained in Durlag's Tower, is unidentified when you first get it but upon identifying it the item description says that it offers protection from physical attacks and a boost to saving throws for 5 turns. The item description also mentions a murky color at the bottom of the bottle. Upon drinking the potion you are petrified and killed.
Expected behavior - The item description should show "Potion of Invulnerability" before it is identified and show that it is a cursed item upon being identified.
This wouldn't really be an issue but this item behaves differently than any other cursed item in the game. Usually you see an item that is unidentified and you can roll the dice and try to use it or you can identify it and find out for certain whether or not it is a cursed item. Or you find an item that is already identified as something like oil of speed and the item description gives you a clue as to whether or not it is cursed even though it is shown as being identified already.
Expected behavior - The item description should show "Potion of Invulnerability" before it is identified and show that it is a cursed item upon being identified.
This wouldn't really be an issue but this item behaves differently than any other cursed item in the game. Usually you see an item that is unidentified and you can roll the dice and try to use it or you can identify it and find out for certain whether or not it is a cursed item. Or you find an item that is already identified as something like oil of speed and the item description gives you a clue as to whether or not it is cursed even though it is shown as being identified already.
2
Comments
HELL NO!
Because a little alarm bell in your head tells you that this could in fact be p*ss...
So... You found a bottle, huh? Strange place? Identified it? Bit murky? Tell me your not gonna drink it...
I usually think of a bug as an unintended result that occurs because the computer wasn't programmed correctly. In this case, I don't believe it's the technical programming that causes the bug, but a lapse in the story telling. Somebody at the non-programming level forgot the usual protocol for this kind of thing. I guess this broadens the definition of a bug for me.