Issue Data
|
Issue #23980: AbLegendaryScript: Cannot GetValuePercentage with None ActorValue
[03/02/2018 - 05:48:00PM] error: Cannot GetValuePercentage with None ActorValue
stack: [ (00181274)].Actor.GetValuePercentage() - "<native>" Line ? [Active effect 1 on (00181274)].AbLegendaryScript.OnHit() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\AbLegendaryScript.psc" Line 20 Note: This repeated six additional times. Also looks like the same thing as Issue #20595 except a different actor. Of course, maybe the fix in v2.0.3 covered all actors and wasn't retroactive after all. The change log gives no indication of that though. If it was a "NR" fix then this can be closed as a duplicate. |
That's a perfect duplicate of 20595.
My proposal to update the fix for 20595 (see my comment there, the original attempt at fixing it didn't work, so I reopened the ticket) was deemed inappropriate by Arthmoor and was not included in UFO4P 2.0.3.
Current state of the art is that we won't touch it.
In case we change our minds, we should reopen the original ticket.
My proposal to update the fix for 20595 (see my comment there, the original attempt at fixing it didn't work, so I reopened the ticket) was deemed inappropriate by Arthmoor and was not included in UFO4P 2.0.3.
Current state of the art is that we won't touch it.
In case we change our minds, we should reopen the original ticket.
Comment #1 Mar 10, 2018 6:20 am
Edited by BlackPete on Mar 10, 2018 2:04 pm
Reopened this because I have more information that may turn out to be helpful. So far, I couldn't attribute the error to a specific scenario, but this time, I only did Thicket Excavations, and the only legendary enemies were two legendary glowing mirelurks, both in the basin at the bottom of the quarry. I sniped the door bars from above and let them engage the raiders first. For most of the subsequent fight, the lurks were far away.
Now, one mirelurk - (sic, only one of them !) filled two pages on my log with that error. The other lurk remained completely silent (papyrus log-wise).
This obviously excludes an issue with specific actors.
Maybe the error is related to specific combat actions ?
Now, one mirelurk - (sic, only one of them !) filled two pages on my log with that error. The other lurk remained completely silent (papyrus log-wise).
This obviously excludes an issue with specific actors.
Maybe the error is related to specific combat actions ?
Comment #2 Mar 20, 2018 4:07 pm
Edited by Sclerocephalus on Mar 20, 2018 4:09 pm
Showing Comments 1 - 2 of 2