Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It's also possible that there is actually a minus sign due to there being a negative spawn rate, which would be a bug as previously mentioned.
The "+" at the end is to indicate how there is more information to be displayed (The display swaps between spawn rate and spawn limit). This is something the Weather Radio does during sandstorms, so it was added in for consistency.
The '+' at the end of the spawn rate display is to indicate it has extra information it alternates between (spawn rate and spawn limit), like how the Weather Radio does when there's a sandstorm going on.
I prefer vanilla friendly/vanilla+ mods, so Fargo's isn't exactly my cup of tea what with Mutant being extreme QoL and Souls letting you be super OP (albeit with challenges that require such power) and whatnot.
Here's an example filepath (For windows) if you don't know where log files are;
C:\Program Files (x86)\Steam\steamapps\common\tModLoader\tModLoader-Logs
Your best course of action is to narrow down the conflicting mods. It's a tedious task, but the best way to do this is to disable roughly half of your active mods and then check to see if the issue occurs. Rinse and repeat until the issue stops appearing. Once that happens, you'll have to re-enable them one at a time and check until the issue shows up again.
You should be able to find at least one of the conflicting mods this way, but it'll be harder to root out which mod(s) are conflicting with that one (Since you'd have to repeat the aforementioned process until you narrow it down to just the conflicting mods).
From my experience, bugs which cause the UI to disappear originate - unsurprisingly - from a UI-based error, so I'd focus on checking any mods which modify UI or have their own UI elements.
Also, are you certain this mod is causing the issue? You appear to be using a lot of different mods at once so it's likely a compatibility issue. Figuring out what mods conflict would be useful info.
I'd been meaning to do this a while ago, shortly after Avalon released on the workshop, but I wasn't able to find the internal names of its biomes until now.
Which of the two issues - old or new - is worse is debatable; one is an inconvenience unless you collect all the info displays (Which few people do since it's so tedious), while the other enforces a hard cap on how many info displays you can use at once. Regardless, we're stuck with the latter case, as that was the call the tML devs made.
I can only assume this was the only way to fix that bug and this was the call the tML devs made. I don't contribute to tML itself, so I wouldn't really know the true reasoning behind the change and/or if anything more can be done.