Welcome to the AFK Mods bug tracker. In order to report an issue, please select a project from the drop down menu below. Select “Open New Issue” and fill out the form with as many details as possible.

An account will be required to submit an issue, so if you need one and are unable to register, please contact us via the forums at https://afkmods.iguanadons.net/

Issue Data
Status: Closed
Issue Type: Bug Report
Project: Unofficial Skyrim Legendary Edition Patch
Component: Skyrim LE: Vanilla
Category: Magic
Assigned To: Nobody
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By Noargle on Feb 17, 2017 12:18 am
Closed By Arthmoor on Sep 30, 2018 12:28 am
Resolution: Can't Fix - Engine Issue

Issue #22039: Cure Poison doesn't work on Afflicted poison spray

Potions of Cure Poison do not work on the Poison Spray effect that Afflicted can inflict on the player. The player continues to take full damage for the full duration even after consuming a Cure Poison potion.



3 comment(s) [Closed]
BlackPete said:
To the best of my knowledge, the reason for the issue "appears to be" the fact that poison spit is classified as a shout. I could be completely wrong on that though so someone else that understands it better (like MadCat) should take a look at it to be sure.

Comment #1 Feb 17, 2017 5:42 am  Edited by BlackPete on Sep 30, 2018 1:28 am
MadCat221 said:
Being a SHOU form likely isn't the cause; the SHOU forms still point to SPEL forms, which then point to MGEF forms. I'll investigate and compare to a known functional poison MGEF/SPEL when I can.

EDIT: I think that the Cure Poison effect may not work on taper-off effects (like fire damage). The assigned damage is over two seconds, but has a taper effect of four seconds. The taper effect works //after// the effect expires.

Basically, the Cure Poison doesn't detect any poison effects to remove and does nothing. Try gulping down a Cure potion within the two seconds that the effect is applied to test this.

Comment #2 Feb 17, 2017 9:51 am  Edited by on Feb 17, 2017 10:25 am
Arthmoor said:
I think it's fairly clear this is some specific behavior that was either intended or is an engine level bug.

Showing Comments 1 - 3 of 3