Unofficial Fallout 4 Patch

The X-02 Power Armor addon presents an interesting variety of script errors in the log. The first and most obvious group is:

[03/02/2025 - 02:09:13PM] error: Unable to bind script ccBGSFO4115_:X02TerminalScript to  (001D2072) because their base types do not match
[03/02/2025 - 02:09:13PM] error: Unable to bind script ccBGSFO4115_:X02TerminalScript to  (001D1AF1) because their base types do not match
[03/02/2025 - 02:09:13PM] error: Unable to bind script ccBGSFO4115_:X02TerminalScript to  (00191EFB) because their base types do not match
[03/02/2025 - 02:09:13PM] error: Unable to bind script ccBGSFO4115_:X02TerminalScript to  (00191F08) because their base types do not match
[03/02/2025 - 02:09:13PM] error: Unable to bind script ccBGSFO4115_:X02TerminalScript to  (FE0019B5) because their base types do not match
[03/02/2025 - 02:09:13PM] error: Unable to bind script ccBGSFO4115_:X02TerminalScript to  (001AC2CC) because their base types do not match
[03/02/2025 - 02:09:13PM] error: Unable to bind script ccBGSFO4115_:X02TerminalScript to  (001D8830) because their base types do not match
[03/02/2025 - 02:09:13PM] error: Unable to bind script ccBGSFO4115_:X02TerminalScript to  (001E2305) because their base types do not match

This group happens because a script that extends Terminal has been bound to Terminal objects that are placed in the world. Objects in world expect ObjectReference type scripts and as a result the scripts fail to bind. However, the script still successfully binds and operates on the base object, meaning that it still functions as needed. In order to resolve this error without breaking the addon, we would need an ObjectReference script similar to the following:

ScriptName X02TerminalReferenceScript Extends ObjectReference

Struct QuestStage
  Int MenuSelection
  Int StageToSet
EndStruct

Quest Property MyQuest Auto Const mandatory
X02TerminalReferenceScript:queststage[] Property Digits Auto Const mandatory

Event OnInit()
  Terminal BaseObject = GetBaseObject() As Terminal
  RegisterForRemoteEvent(BaseObject, "OnMenuItemRun")
EndEvent

Event Terminal.OnMenuItemRun(Terminal akSender, Int auiMenuItemID, ObjectReference akTerminalRef)
  ; Skip if this object is not loaded, to prevent multiple copies of the terminal reference from running
  ; Without this, persistent references will all run the subsequent code together. This can be observed by
  ; the holotape sound effect rapidly playing multiple times if this check is removed.
  If (!Is3DLoaded())
    Return
  EndIf
  
  Int index = Digits.findstruct("MenuSelection", auiMenuItemID, 0)
  If index >= 0
    MyQuest.SetStage(Digits[index].StageToSet)
  EndIf
EndEvent

The above script can take the same properties that the existing script takes, while operating via the in-world ObjectReferences rather than the base Terminal objects. Switching the RelayTowerTerminal and ccBGSFO4115_ConsoleTerminal Terminal objects over to the above script and ensuring the properties retain the same data resolves those errors and prevents the change from breaking the quest.


Next up is the following error, also present at startup:

[03/02/2025 - 02:09:27PM] error: Property Digits on script ccBGSFO4115_:X02TerminalScript attached to  (FE001A7D) cannot be initialized because the value is the incorrect type

This is the result of the array property on ccBGSFO4115_HolotapeTerminal810 being empty. Since that property being empty means the script won't do anything in the first place, this error can be fixed by removing the script from this Terminal object. Presumably this is a leftover from a cut stage in the quest where a no longer implemented option in that terminal would prompt an objective.


After that comes the following:

[03/02/2025 - 02:09:27PM] warning: Property StageToSet01 on script ccBGSFO4115_:X02TerminalScript attached to  (FE00181A) cannot be initialized because the script no longer contains that property
[03/02/2025 - 02:09:27PM] warning: Property MenuNumber01 on script ccBGSFO4115_:X02TerminalScript attached to  (FE00181A) cannot be initialized because the script no longer contains that property

These are both properties that no longer exist, and this can be fixed by opening the script's properties on the ccBGSFO4115_HolotapeTerminal01 Terminal object. The Creation Kit will automatically purge the properties and prompt you to click OK to confirm the changes.


Finally, we have these two errors prompted by stage 100 of ccBGSFO4115_DM_Quest:

[03/02/2025 - 03:26:52PM] error: ccBGSFO4115_DM_Quest (FE001845): unknown quest objective 100.
stack:
	[ccBGSFO4115_DM_Quest (FE001845)].ccBGSFO4115_:Fragments:Quests:QF_ccBGSFO4115_DM_Quest_01000845.SetObjectiveDisplayed() - "<native>" Line ?
	[ccBGSFO4115_DM_Quest (FE001845)].ccBGSFO4115_:Fragments:Quests:QF_ccBGSFO4115_DM_Quest_01000845.Fragment_Stage_0100_Item_00() - "F:\_F4\CClub\Art\Raw\Creations\BGSFO4115\Source\Scripts\ccBGSFO4115_\Fragments\Quests\QF_ccBGSFO4115_DM_Quest_01000845.psc" Line 190
[03/02/2025 - 03:26:52PM] error: Object reference has no 3D
stack:
	[ (00043CDF)].Sound.play() - "<native>" Line ?
	[ccBGSFO4115_DM_Quest (FE001845)].ccBGSFO4115_:Fragments:Quests:QF_ccBGSFO4115_DM_Quest_01000845.Fragment_Stage_0100_Item_00() - "F:\_F4\CClub\Art\Raw\Creations\BGSFO4115\Source\Scripts\ccBGSFO4115_\Fragments\Quests\QF_ccBGSFO4115_DM_Quest_01000845.psc" Line 191

The first error is very straightforward: Objective 100 no longer exists, and that line of code should be removed. The second one is slightly more complicated but easy to fix. Bethesda is attempting to play a sound using a disabled reference, which fails and produces an error. While we could switch this line and the one after it that enables the object, the use of EnableNoWait means there is a chance of this error recurring due to race conditions. It would be better to place a new marker object that is enabled by default, add it as another property on the script, and then use that marker object rather than the existing one that also acts as an enable parent.