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: Fishing
Category: Papyrus
Assigned To: Nobody
Platform: All
Severity: Very Low
Votes: 1
Watching: N/A
Opened By DarthVitrial on Apr 17, 2022 5:42 pm
Last Edited By Arthmoor on May 30, 2022 7:07 pm
Closed By Arthmoor on Jun 8, 2022 11:08 pm
Resolution: Fixed
Comment: Fixed for USSEP 4.2.7.

Issue #32385: Fishing Papyrus Spam

 
Whenever you first enter a cell containing critter spawn markers added by the fishing creation (I recommend ClearspringTarn01, it's easiest) the log will get the following:
warning: Assigning None to a non-object variable named "::temp9"
stack:
[ (random refid)].ccBGSSSE001_CritterSpawn.SpawnCritter() - "CritterSpawn.psc" Line 141
[ (random refid)].ccBGSSSE001_CritterSpawn.spawnInitialCritterBatch() - "CritterSpawn.psc" Line 115
[ (random refid)].ccBGSSSE001_CritterSpawn.OnCellAttach() - "CritterSpawn.psc" Line 89


the more fish are there the more times this message will appear, usually.

Comments

4 comment(s) [Closed]
DarthVitrial said:
 
This papyrus error (along with some others) is fixed by this mod: https://www.nexusmods.com/skyrimspecialedition/mods/67276 , might be worth asking the mod dev how they did it.

Comment #1 May 30, 2022 6:14 pm
Arthmoor said:
 
I'm extremely hesitant to start fidding with things like this based on panic assumptions being made about data shown in Resaver or any other supposed script analysis tool. The save game format is NOT well known enough for that data to be meaningful and the devs have said several times that instances of scripts in the save are entirely normal and not something to worry about.

Given that this person has described that there are additional changes beyond simply addressing whatever is causing the log spam, it wouldn't be prudent of us to use that material directly. It would instead be better to isolate the actual fix from the rest of whatever has been done.

I'd also need to be absolutely certain that this issue is really something that happens in a base setup for 1.6. A lot of these kinds of errors are induced by throwing 6 million other mods on top of things, and then hacking up the save when they see 100 instances of a common script in there.

Comment #2 May 30, 2022 7:06 pm
DarthVitrial said:
 
Well, the papyrus errors themselves in the log are pretty easy to reproduce, I got them in a totally vanilla install when entering clearspring tarn (and any other area containing those placed fishing critter spawners) long before that “critterspawn spam fix” mod was created. So those non-object variable errors are vanilla.
(Whether they cause any problem or not, I can’t say. Just that they exist.)

Comment #3 May 30, 2022 7:13 pm  Edited by DarthVitrial on May 30, 2022 7:14 pm
Arthmoor said:
 
I think I got that one figured out. The SpawnCritterAtRef function in the Fishing DLC script needed to be adjusted to return a bool like the function of the same name in the vanilla script does with our fixes in place. There are no errors spamming the logs at ClearspringTarn01 anymore.

Comment #4 Jun 8, 2022 11:08 pm
Showing Comments 1 - 4 of 4