You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[client.log](https://github.com/user-attachments/files/18816548/client.log)
When switching mod packs during debugging, this issue occurs.
The probability of triggering is almost 100%.
The error appears after the player enters the world following the mod pack switch. At this point, the game resolution resets to the minimum default value, and all UI elements related to the mouse and mouse layers fail to render or disappear. I suspect this is a result of an error in the UI logic layer.
Once this issue is triggered, reloading the mod doesn't resolve it. It seems that the game must be restarted to restore normalcy.
I’ve tested about 8 times, and the logs always point to the CheatSheet mod, but the issue may not actually be caused by CheatSheet.
So, I’m looking for help, or perhaps if CheatSheet could implement some defensive programming, it might help avoid this issue from happening to some extent?
The text was updated successfully, but these errors were encountered:
Here is the log file:
[client.log](https://github.com/user-attachments/files/18816548/client.log)
When switching mod packs during debugging, this issue occurs.
The probability of triggering is almost 100%.
The error appears after the player enters the world following the mod pack switch. At this point, the game resolution resets to the minimum default value, and all UI elements related to the mouse and mouse layers fail to render or disappear. I suspect this is a result of an error in the UI logic layer.
Once this issue is triggered, reloading the mod doesn't resolve it. It seems that the game must be restarted to restore normalcy.
I’ve tested about 8 times, and the logs always point to the CheatSheet mod, but the issue may not actually be caused by CheatSheet.
So, I’m looking for help, or perhaps if CheatSheet could implement some defensive programming, it might help avoid this issue from happening to some extent?
The text was updated successfully, but these errors were encountered: