Game crashing whenever i interact with magic storage/regular chest
Ever since a day or two ago, ive straight up given up playing calamity because of this problem, i dont know if its the amount of mods i have, or if its a specific mod, though when i looked it up i saw a forum that said that it might be one specific mod, but i have over 60 mods, so i might just disable each one until i find the one causing the problem, heres a list of all the mods i have if somebody knows if one of them is causing the issue, as well as my logs.
8 Replies
Welcome to #support-forum. Before someone helps you, please first consult the information in #TML Troubleshooting Guide and try all the suggestions that might fit your particular issue, especially in the linked FAQ page.
If the information in the pinned thread does not solve your issue, please post all log files by dragging and dropping them into this chat. In Steam right click on
tModLoader in the library, then hover over Manage and click on Browse local files. In the folder that appears find tModLoader-Logs and open that folder. Inside that folder are the logs files. Select them all except the Old folder and drag them into this chat. If you need a visual guide to this process watch this: https://github.com/tModLoader/tModLoader/assets/4522492/3f4efa43-753f-4733-b630-ba85e711340csorry, that mod list was incorrect, i updated it and alphabetically organized it according to my mod list.
According to the log, your world
tModLoader/worlds/TRIO_CUCKING!-!-!-!.twld is corrupt
Try restoring a backupThank you, but its actually my world called plot of myth the problem is occuring in.
ps, pls dont mind my world names i just type some bs most of the time...😭
you gotta post the log from when it actually crashes then
just to clarify, there are three different folders with text files named "Logs" which one should i show?
one file is called tmodloader, one is called tmodloader-preview, and another called tmodloader-1.4.3
wait i think i have the right one
but i cant upload the full txt. file for some reason?
heres a screenshot of the error in the logs
