random mods are "crashing." it's not a specific one.

[KiraMoonrabbit]

i know you're supposed to go to the relevant discord servers for things like this but. i really, really, really do not want to join a discord I'll never talk in just for a single bug report. i'm staunch in this belief. but i digress.

hereupon is the crash log. https://pastebin.com/BdtDCxG7

it says something about the lobotomy corporation mod this time, BUT. every time i load the game. this specific error throws itself at me around the "configurating content" stage. but the thing is, every time it's a different mod's NPC "not being specifically set to an intance of an object" causing it. sometimes it'll be CalVan. sometimes it'll be Stars Above. sometimes it'll be Assorted Crazy Things. sometimes it'll be Gensokyo. and these are just the popular mods that are freaking out. wether or not i leave the offending mod un-enabled or go to re-enable it doesn't matter, next time it hits configuring another mod will throw that same error over a different small thing.

and the thing is, sometimes, very rarely, it'll launch properly. i have no idea what's causing this. i don't remember any specific mod that updated or that i added. i don't think it's an addition, in specific, this started during a time i hadn't added anything recently. the nature of these errors makes the classic "disable them all and slowly add mods one by one" fairly unfeasible since false positives could potentially happen.

the nature of the bug makes me feel like providing a modlist out the gate would be fruitless (and I'm already overwhelmed trying to make sense of this little error and also attempt to be as verbose about its nature as possible) but i will provide one if asked nonetheless.

[koimeiji]

Don't leave out info just because you think it's pointless or not helpful; anything you can give that's related to the topic helps.

Terraria version number
tModLoader version number
Mods list, with version numbers
Crash logs (you've already provided one though)
What you were doing that caused the crash (ie; placing a tile, killing an enemy, using a weapon, crash on launch, etc)
What kind of crash it is (FPS death, crash to desktop, frozen player, etc)
Is the crash repeatable; ie, does it happen consistently when doing a certain action

All of that helps in diagnosing what the problem is.



With all that said, I think your best bet for figuring out what's causing the problem is the logarithmic method. Disable/uninstall half your current mods, run the game.
If it crashes again, disable/uninstall half your current mods again.

Repeat until it doesn't crash. The offending mod is in the last half that you uinstalled.

[KiraMoonrabbit]

alright, i did a round of the old tried and true.

Small amount of extra context: these crashes happened while i was loading terraria itself, while everything gets set into place and there's a loading bar. the crash itself is the benign "disable this and try loading again" kind. i couldn't have gone in to swing a weapon or try to enter a world.

now as for my findings... here's the notepad I took, hence why recounting things suddenly gets a little messy.

the Tmodloader version: v 2023.6.25.31

SHORTLY AFTER ENABLING FARGO'S SOULS v 1.5.1.1, LOADING STOPPED SOMEWHERE AROUND THE CONFIG STAGE GIVING THIS ERROR:

https://pastebin.com/vK91X4mt


ABOVE ERROR DID NOT REPEAT UPON A SECOND ATTEMPT AT LOADING, nor did the mod disable itself, weirdly enough.

after enabling all my calamity-related mods (saving them last knowing calamity is a mega monster of a mod), the same error as the thread started from popped up again, what exactly was erroring doesn't matter since I know it's not the problem here.
disabling the calamity mods loaded normally.

then, I tried again with just calamity and the rest of the modslist, without the calamity peripherals.
The Error Shows Up Again.

Huh.

and knowing this, the calamity version is 2.0.3.2.
it didn't have this sort of error for a long time. i have zero clue why it's suddenly throwing up now. I'll boot the game up calamityless a couple more times to see if i've finally found some sort of direction to walk in or if this is just another one of those rare fluke boot-ups i've been having since this problem started.

[KiraMoonrabbit]

...aaaaand... it's another false positive sort of deal. the errors resume when i exit out and return. this is why i didn't think the slow method would work, because something that looks like it helps actually doesn't once i actually exit out of the game and return.

i'll have to get my modlist with versions later. right now i'm just full of frustration at the situation, because it already took way too long to troubleshoot the old fashioned way WITHOUT having to reboot the game itself every time.

[koimeiji]

That new log doesn't point towards any specific mod, but rather tModloader itself.
That, paired with the complete randomness of these crashes you're experiencing, leads me to wonder if it's not any specific mod but rather the loader itself that's broken.

My recommendation, at this point in time, would be a total wipe and re-install of everything. Uninstall terraria, tmodloader, delete all your mod files, pretty much delete everything related to terraria, then reinstall terraria and tmodloader.

Launch without anything installed.

Then slowly add the mods you want back, launching the game every now and then to make sure it loads correctly. Small mods you can do in batches, but any big ones like Calamity should be added by itself and then tested to make sure.


This will be time consuming, especially with how long Terraria takes to load let alone load mods, but it's your best bet in my opinion.

[KiraMoonrabbit]

that's a really scary conclusion. if some mod broke the loader itself... i shudder to think of having to submit that report.

i'll do the terraria deep purge Tomorrow since it's getting too late in my sleep schedule's day to do the whole thing all at once. then i shall report my findings...

[koimeiji]

Originally posted by KiraMoonrabbit:

that's a really scary conclusion. if some mod broke the loader itself... i shudder to think of having to submit that report.

i'll do the terraria deep purge Tomorrow since it's getting too late in my sleep schedule's day to do the whole thing all at once. then i shall report my findings...

It's not necessarily that some mod broke your loader. I find it more likely that, if the loader itself is broken, it simply just got corrupted somehow (which can naturally happen).

And, even then, it's entirely possible your loader is fine and it's some mod that's causing the issue. This method of a full wipe and reinstall will let you progressively add your mods, and in the event you download the offending mod (if there is one), you'll catch it almost immediately.

It'll also let you second guess some mods that you may not really need, but downloaded anyways.

[KiraMoonrabbit]

I think I might have a Culprit.

The Tmodloader-itself error mentioning the credits started during the "remove and reenable" stage around me adding Fargo's Souls. So that made me wonder if that mod, specifically, is what's causing this issue.

So after wiping all forms of Tmodloader-related stuff and refreshing the install, I actually started with enabling Fargo's Souls and a few mods I remember throwing up. I didn't even need to reboot the game for the familiar error to show itself (with its own dependency, Fargo's Mutant Mod, to boot). then, I enabled EVERYTHING except for Fargo's Souls, and it was error free. Rebooted, and the error did not re-occur, too.

Further bulletins as events warrant, but I think, for real, I might have finally found something to pin the blame on. And, for posterity, the version is Fargo's Souls 3.1.2.

[KiraMoonrabbit]

...wait, that's the Mutant Mod's version number. souls is still the same as the last time i mentioned its number. oops.