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 Skyrim Special Edition Patch
Component: Skyrim SE: Vanilla
Category: Papyrus
Assigned To: Nobody
Platform: All
Severity: Very Low
Votes: 1
Watching: N/A
Opened By scorpiosixnine on Jan 10, 2020 4:29 am
Last Edited By Arthmoor on Jan 10, 2020 2:03 pm
Closed By Arthmoor on Nov 14, 2020 7:17 pm
Resolution: Lack of Needed Feedback

Issue #28394: WordWallTriggerScript error

 
Basically the same problem as #14195.

The script is failing because `lookTarget` has somehow become set to None.

I fixed it by patching the script as follows: 

bool Function isLooking()
	if lookTarget
		Return (game.getPlayer().HasLOS(lookTarget) && !WordLearned); && !game.GetPlayer().IsInCombat() )
	else
		lookTarget = lookTargetWord01
		StopFX()
		return false
	endif
endFunction

Related Issues: 14195  

Comments

3 comment(s) [Closed]
scorpiosixnine said:
 
I'd be happy to contribute a proper patch for USSEP, but I couldn't find instructions anywhere. Is there a github project somewhere?

Comment #1 Jan 10, 2020 4:31 am
Arthmoor said:
 
We're going to need more than this to assume there's actually a problem because the script flow clearly indicates that it can only break when the global variables are not updating properly, which is an issue we fixed way back in USKP 2.0.

Arbitrarily setting the target to the first word is not necessarily a correct solution either.

Comment #2 Jan 10, 2020 2:03 pm
scorpiosixnine said:
 
Well, I’ve been running with an up to date USSEP and encountered the issue, so it definitely is not fixed in all circumstances. As to how it gets set to none - I can’t say.

Fair point about the first word. It’s a pragmatic workaround though, which prevents a worse problem (endless spamming of the log as the script repeatedly fails).

Comment #3 Feb 8, 2020 7:29 am
Showing Comments 1 - 3 of 3