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: Vanilla
Category: Papyrus
Assigned To: Sclerocephalus
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By Sclerocephalus on Mar 30, 2017 8:51 pm
Last Edited By Arthmoor on May 8, 2017 5:16 pm
Closed By Arthmoor on May 8, 2017 5:16 pm
Resolution: Fixed
Comment: Fixed for UFO4P 2.0.1.

Issue #22250: abProtectronRaceScript - Cannot call startInPod() on a None object

[03/31/2017 - 03:17:10AM] error: Cannot call startInPod() on a None object, aborting function call
stack:
[Active effect 1 on (FF08E375)].abProtectronRaceScript.OnEffectStart() - "g:\_F4\Art\Raw\ScriptsMilestone\abProtectronRaceScript.psc" Line 31
[03/31/2017 - 03:17:10AM] warning: Assigning None to a non-object variable named "::startInPod_var"
stack:
[Active effect 1 on (FF08E375)].abProtectronRaceScript.OnEffectStart() - "g:\_F4\Art\Raw\ScriptsMilestone\abProtectronRaceScript.psc" Line 31


This script tries to read a property from another script that is apparently not existing on some protectrons. The fun thing is that the property to be read out does already exist as a property with the same name on abProtectronRaceScript. Thus, if that other script is missing, this script proceeds with the value from its own property anyway, and this always works (because we never see any protectrons standing besides their empty pods in the game; that's what this property handles).

A look at code of the missing script showed that this once had more than 100 lines but all of them were commented out except for two property definitions (a script note says that this is now used only as a data holder). Considering that one of these properties is duplicated on abProtectronRaceScript anyway, it may well be rhat the devs stopped using that script at some point entirely.

Therefore, I simply added a sanity check. This eliminated the log spam entirely and had no unexpected in-game effects.