t is null error

Semi-frequent error, unsure what the trigger is.

changed the description

Any rough estimate of where during gameplay it is happening? Endweek? Slave interact? etc.

It might've been the cache or something eating up my SSD space (it went to 0 GB multiple times yesterday despite having a few GB free), haven't tested to be sure.

Nevermind, just happened again with 18 GB space, maybe when the passage is being rapidly updated? It seems to be more frequent when I'm spamming something. (Security Upgrades, Weapons Manufacturing Research, Prosthetic Reverse Engineering, etc.)

Don't spam and see if it happens. It is very possible to spam a link hard enough that it sort of goes off twice or more to very bad effects.

Hmm, I'm pretty sure it happened even when I didn't spam albeit much much rarer. I'll get back to you if it does.

It just happened without spam, I was just going through the week end events.

Is it consistent? If it is, passing a save from the week prior would be wonderful. Finding which t is null is like finding a needle in a haystack.

Where does it occur? During the slave report? Economic report? During the event phase?

Honestly, I would love if I could get a stack trace for this. Not sure it's possible though.

This is fairly likely to be a dud slave too, which !12340 (merged) would flag. Wish I knew what was making it happen though.

I know this sounds incredibly unhelpful but honestly it seems completely random. I've seen it happen in Weapons Manufacturing when going through all of the research options, I've seen it happen in the Prosthetics Lab when reverse engineering everything, I've seen it in an event, etc.

It genuinely feels random to me, just much more likely when you're clicking a lot of links in succession but still possible albeit much MUCH rarer if just going through links normally.

That said it isn't a MASSIVE issue, I've gotten it like 6-8 times in the same save and no issues so far.

In regards to stack trace, I'll check the console next time it happens.

Stack Trace: U/show/<@file:///E:/Git/fc-pregmod/bin/FC_pregmod.html:643:7346 show@file:///E:/Git/fc-pregmod/bin/FC_pregmod.html:643:7383 U/Tt/u<@file:///E:/Git/fc-pregmod/bin/FC_pregmod.html:643:14470

Got it to trigger fast upgrading the prosthetics lab on a fresh cheat save. (always waited for the passage to refresh before clicking again but it was in quick succession.)

I THINK what's happening here is that t is redefined at every passage load and is deleted whenever you click on a link that loads another passage. (ie. temporary variable)

Essentially, the javascript initializing t hasn't had time to trigger but the user is already loading the next passage. (THIS IS JUST A GUESS)

Maybe something like this will work?

$(document).on(':passageinit', function () { // Disable all passage links before rendering $('a.link-internal').addClass('disabled'); });

$(document).on(':passagerender', function () { // Enable all passage links once the passage has been rendered $('a.link-internal').removeClass('disabled'); });

Had some PC problems, but I am back now. I was going to post this in #5668, but I think it has more relevance here. So it is referencing this issue because I am too lazy to rewrite it

---

I think #5654 is caused by one of the libraries we use, but I would have to get to my notes to make sure. If I am remembering correctly I hunted it down to where t was defined and used, but couldn't figure out what the actual problem causing the error was. I think it may have been the popup/tooltip library, but I am not sure without referencing my notes (that I don't have easily accessible right now). It seemed to happen when a lot of DOM updates happened in a short period and the updated DOM included one or more tooltips