Unofficial Skyrim Legendary Edition Patch

Not (yet) getting the above errors in my new game (Level 37 so far). There are</em> a lot of odd errors in the logs along similar lines, but not what could be called "spam", just isolated instances.

Is there no one place for reporting all these (if they should be reported) or should each different one be a separate bug? Bug count could go through the roof if I did that (which is why I haven't).

Each distinct papyrus error should be filed in it's own bug (errors relating to the same script can be filed together). And if the same error keeps repeating, one bug report for it will suffice.

There's now a seperate category in the tracker for reporting script errors that don't fit into any other category neatly, Papurys.

Thanks. Not always easy to determine the best category, so this new one might attract quite a few entries

Not sure if there's much we can do with this one though. I've followed the logic through the word wall scripting before and it all seems sound to me so I don't know why sometimes they spam like mad and most other times they don't.

Thanks for looking - the amount of spam they were producing was ridiculous.
Still on the same game at Level 62 (or so) and it's not happened yet, but I've not yet fully started the main quest (not spoken to the Greybeards) and neither do I have Dragonborn active. I'll watch for it happening when I do those.

000709F6 is the Shearpoint word wall trigger, where the player learns three words at once, and it appears that the error occurs only there.

To proceed to the next word once a word has been learned, the value of the "shoutglobal" property on WordWallTriggerScript is incremented. This is performed in the StartFX() function and reads as follows (line 152):

ShoutGlobal.value += 1

This doesn't work on a global!

Amend this line to read:

ShoutGlobal.SetValue (ShoutGlobal.Value + 1)

Can't say whether this is the only bug in the scripts, but fixing this is certainly a good point to start with.

That could explain why I've not seen the errors in my current game - completely managed to miss locating Shearpoint entirely.
I'll go do that and my 2 remaining missing words (Shalidor's Maze and Forelhost) and see what happens.

I see why you guys hate these...

I went to Shearpoint, killed the Dragon and the Dragon Priest, got the shout (all 3 words) - no spam.
Went to Shalidor's Maze, completed it and got the shout. No spam.
Went to and completed Forelhost and got the shout. No spam.

So I now have all the shouts (from Skyrim, not the DLCs) - and no spam.

The difference between my current game and the one where the spam was happening is that in that game I had all 3 DLCs active, in the current game I don't have DG or DB - coincidentally those which add new shouts and Word Walls....

Fixed for USKP 2.0.

That's one obscure error, good catch. I wouldn't have caught that since I had no idea you couldn't use += on a global.

Marked as [NR] after beta testing.

Likely related <a class="bbc_url" href="http://www.afkmods.com/index.php?/tracdown/issue/12399-dismay-shout-unlocking-is-bugged/" title="">Bug #12399</a>, <a data-ipb='nomediaparse' href='http://www.afkmods.com/index.php?/tracdown/issue/13156-call-of-valor-second-word-bug/'>Bug #13156</a>, <a class="bbc_url" href="http://www.afkmods.com/index.php?/tracdown/issue/13333-aura-whisper-word-walls-bug/" title="">Bug #13333</a> and <a data-ipb='nomediaparse' href='http://www.afkmods.com/index.php?/tracdown/issue/13810-chanting-returned-at-already-learned-wordwall/'>Bug #13810</a>, all assumed fixed via fixing this bug.

Something is still not right - i just got over 300KB of this. New, clean game with 2.0.0a (release).

Difference from all the above is that this visit to Shearpoint was the 2nd, not the first. In addition, there were occurances of
"Cannot call DisableNoWait() on a None object" from WordWallTriggerBleakFallsScript mixed in with all the LOS errors. I hadn't been anywhere near Bleak Falls Barrow...

Logs prior to this point have been clean of this LOS error. I have a suitable save game if required.

You should open a new report for it as fixed bugs are generally considered closed and not actively monitored by the team. Just add a link into your new report back to the original issue.

Done - #14195.