Issue Data
|
Issue #30827: Two Potential Papyrus Errors
Both of these errors are admittedly from items placed by a mod, but I have confirmed that they are using vanilla scripts with no alterations to the scripts except for those made by USSEP itself, and from what I can tell these errors should both happen in vanilla locations too, since these seem to just be the result of missing sanity checks in the scripts (it's just easier to reproduce in my mod setup because I know exactly where the placed objects are that will trigger the bug)
First error: warning: (XX17615A): Ref is in an unloaded cell, so it cannot cast spells.. stack: [ (0007E585)].SPELL.Cast() - "<native>" Line ? [ (XX17615A)].TrapFlamethrower.fireByCastingType() - "TrapFlamethrower.psc" Line 134 [ (XX17615A)].TrapFlamethrower.fireTrap() - "TrapFlamethrower.psc" Line 82 [ (XX17615A)].TrapFlamethrower.OnActivate() - "TrapBase.psc" Line 87 I know USSEP already fixes one such error in the TrapFlamethrower.psc script, so maybe this is just an edge case that your prior fix missed? (going by the line numbers, this is indeed the USSEP version of the script). Might not be fixable though since it happens when you exit the room while the script is running. Second Error: warning: (XX35CC2A): currently does not have 3d and cannot register for animation callbacks. Returni. stack: [ (XX35CC2A)].DLC2TrapApoTentacle.WaitForAnimationEvent() - "<native>" Line ? [ (XX35CC2A)].DLC2TrapApoTentacle.fireTrap() - "DLC2TrapApoTentacle.psc" Line ? [ (XX35CC2A)].DLC2TrapApoTentacle.OnActivate() - "DLC2TrapApoTentacle.psc" Line ? Probably just needs an Is3DLoaded check. |
This issue has had a reopen request processed which was denied for the following reason:
In the case of the second error, isLoaded is a boolean variable from the parent script, not a function call. Following the extends trail back to the base script type shows you it's an ObjectReference, not a Cell.
We've found in the past that the unloaded cell one can actually be a false error. Famously, we tried to kill that error with the Storm Call shout and broke it pretty badly and had to completely revert the changes.
I'm not sure we should bother with the other one either as it's not really going to affect anything by leaving it alone, and trying to fix it might result in other unwelcome issues.
I'm not sure we should bother with the other one either as it's not really going to affect anything by leaving it alone, and trying to fix it might result in other unwelcome issues.
Showing Comments 1 - 1 of 1