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, or Starfield. Doing so will help everyone on all platforms.

Issue Data
Status: Closed
Issue Type: Bug Report
Project: Unofficial Fallout 4 Patch
Component: Fallout 4: Vanilla
Category: Placed References
Assigned To: Nobody
Platform: Windows PC
Severity: Low
Votes: 0
Watching: N/A
Opened By Sclerocephalus on Nov 29, 2016 7:05 pm
Last Edited By BlackPete on Feb 4, 2018 11:25 pm
Closed By Sclerocephalus on Oct 19, 2017 8:10 pm
Resolution: Duplicate
Comment: Duplicate of #22189

Issue #21644: Trigger with missing keyword property, RefID = 00210692

 
[11/29/2016 - 07:45:26PM] error: Cannot call LocSetKeyword() on a None object, aborting function call
stack:
[Followers (000289E4)].followersscript.HandleMessageFromSASTrigger() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\followersscript.psc" Line 2593
[ (00210692)].sastriggerscript.OnTriggerLeave() - "g:\_F4\Art\Raw\ScriptsMilestone\SASTriggerScript.psc" Line 67
[11/29/2016 - 07:45:27PM] error: Cannot call LocSetKeyword() on a None object, aborting function call
stack:
[Followers (000289E4)].followersscript.HandleMessageFromSASTrigger() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\followersscript.psc" Line 2593
[ (00210692)].sastriggerscript.OnTriggerEnter() - "g:\_F4\Art\Raw\ScriptsMilestone\SASTriggerScript.psc" Line 42

Related Issues: 22189  

Comments

1 comment(s) [Closed]
Sclerocephalus said:
 
There's nothing wrong with the trigger. However, due to a bug in the HandleMessageFromSASTrigger() function on FollowersScript, the trigger ref could get lost and it would then try to run operations on a 'none' object. The issue has been fixed already for UFO4P 2.0.1.

Showing Comments 1 - 1 of 1