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 Fallout 4 Patch
Component: Fallout 4: Automatron DLC
Category: Papyrus
Assigned To: Sclerocephalus
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By Sclerocephalus on Dec 4, 2017 1:01 pm
Last Edited By Sclerocephalus on Mar 13, 2018 1:07 pm
Closed By Sclerocephalus on May 18, 2018 10:01 pm
Resolution: Fixed
Comment: Fixed for UFO4P 2.0.4

Issue #23269: DLC01WorkshopRobotAttack01 - Index 5 for GetAt is outside max range (0)

[12/04/2017 - 05:18:34PM] error: alias Raiders on quest DLC01WorkshopRobotAttack01 (0100FD0D): Index 5 for GetAt is outside max range (0).
stack:
[alias Raiders on quest DLC01WorkshopRobotAttack01 (0100FD0D)].recollectionaliasscript.GetAt() - "<native>" Line ?
[DLC01WorkshopRobotAttack01 (0100FD0D)].rescript.::remote_REParentScript_RECheckForCleanup() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\REScript.psc" Line 252

       
Related Issues: 24040  

Comments

1 comment(s) [Closed]
Sclerocephalus said:
It's important to add here that no errors were thrown for indices 0-4, although they are invalid too (the code that throws this error is looping through a collection alias). It thus appears that the collection was deleted while the loop was running. Which in turn means that REScript must have started processing another cleanup event after it stopped the quest.

To make this happen, REScript must have received two cleanup events in very short succession. This is possible because a function on REParentScript allows external scripts to create a copy of that script at runtime, and those copies would start to send their own cleanup events upon creation.

To fix this, I added a few lines to REScript to unregister for the cleanup event when it stops the quest.

I also added some code to skip cleanup events that are received while the script is still processing a previous event.

       
Comment #1 Mar 12, 2018 3:39 pm  Edited by Sclerocephalus on Mar 13, 2018 1:05 pm
Showing Comments 1 - 1 of 1