Welcome to the AFK Mods bug tracker. In order to report an issue, you need to have a VALIDATED account to post one. Once you have followed the link the registration email sent you, 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.

Please also consider sending your bug report to Bethesda if you are reporting on an issue with Skyrim Special Edition, Fallout 4, Starfield, or Oblivion Remastered. Doing so will help everyone on all platforms.

Issue Data
Status: New
Issue Type: Bug Report
Project: Unofficial Fallout 4 Patch
Component: Unofficial Fallout 4 Patch
Category: Papyrus
Assigned To: Sclerocephalus
Platform: All
Severity: Normal
Votes: 0
Watching: N/A
Opened By Glitchfinder on Aug 23, 2025 1:46 pm
Last Edited By Sclerocephalus on Sep 8, 2025 3:09 am

Issue #35771: DefaultCollectionAliasOnDeath: Array index 0 is out of range (0-0)

 
[08/23/2025 - 11:12:09AM] error: Array index 0 is out of range (0-0)
stack:
	[alias GhoulBosses on quest MinRecruit07 (00186642)].DefaultCollectionAliasOnDeath.UFO4P_AddRefToTriggeredRefArray() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\DefaultCollectionAlias.psc" Line 144
	[alias GhoulBosses on quest MinRecruit07 (00186642)].DefaultCollectionAliasOnDeath.TryToSetStage() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\DefaultCollectionAlias.psc" Line 78
	[alias GhoulBosses on quest MinRecruit07 (00186642)].DefaultCollectionAliasOnDeath.OnDeath() - "F:\_F4\Art\Raw\Scripts\DefaultCollectionAliasOnDeath.psc" Line 11


This is the result of a race condition not being fully accounted for. Specifically, the alias in question has two different scripts running OnDeath events, and one of them removes the relevant reference from the alias as part of its processing. While the unofficial patch accounts for this at some points in the code, the reference can be removed from the alias at any point in TryToSetStage or the functions it calls due to the scripts running in parallel. In the case of this log, the reference was removed after validation on line 49 but before TriggeredRefArray could be set up on line 117.

When this error occurs, the quest winds up stuck on the current stage because there are no more bosses remaining for the player to kill.

As a note, the line numbers in the script log are incorrect. It would appear the compiled version included in the unofficial patch was not updated after comments were changed and code was rearranged, so the actual line numbers in the current source code would be 138 and 74, rather than 144 and 78.

Related Issues: 23739  25818  25819