Open cobaltcoyote opened 2 years ago
Can you try running this mod either via the Curseforge launcher or some other means and confirm if the issue still persists? That should only be sent once per instance of a game.
I'm running minecraft through the game launcher, and am having the same issue.
I have this issue as well. It writes 5 new identical .toml.bak files with decreasing frequency before freezing up completely until I force quit the program.
Using the official launcher, and mod version 1.18.2 - 1.0.0
I can confirm the bug, I have the same message every 10seconds, spamming the console 1.18.2 - 1.0.0, tried to delete the conf but without a change Using LITV3 modpack
Log file.txt attached a logfile of this issue. Steps to replicate: 1: create a forge server instance for 1.18.2 / 40.1.84 2: add the 1.18.2 1.00 mod version to the pack 3: run server
this was done to attempt to isolate it from the other mods in the LITV3 pack, there this error also occurs in the server package.
Same issue here, except in 1.19.2.
Alright, I believe I've found a fix (pending some testing). I'll fix it in latest first (1.19.4), then bring it all the way downstream to 1.18.
@HoneyspringsBw and anyone else playing on 1.19.2, can you try this build out and see if it fixes the issue? https://legacy.curseforge.com/minecraft/mc-mods/sapience/files/4502823
Also, if anyone is playing 1.19.4, there's this too: https://legacy.curseforge.com/minecraft/mc-mods/sapience/files/4502809
1.18.2 fix is also available: https://legacy.curseforge.com/minecraft/mc-mods/sapience/files/4503097
@HoneyspringsBw and anyone else playing on 1.19.2, can you try this build out and see if it fixes the issue? https://legacy.curseforge.com/minecraft/mc-mods/sapience/files/4502823
Also, if anyone is playing 1.19.4, there's this too: https://legacy.curseforge.com/minecraft/mc-mods/sapience/files/4502809
Just tried it out, no difference unfortunately.
Just tried it out, no difference unfortunately.
How exactly are you testing?
I tested in a fresh install of 1.19.4 (which has the exact same fix as 1.19.2), and got no config errors in the log, even after I logged out and logged back in.
Just tried it out, no difference unfortunately.
How exactly are you testing?
I tested in a fresh install of 1.19.4 (which has the exact same fix as 1.19.2), and got no config errors in the log, even after I logged out and logged back in.
Apologies, I should have specified. I tested it in a 1.19.2 installation where the broken version of the mod initially resided before I removed it and added the fixed version.
Apologies, I should have specified. I tested it in a 1.19.2 installation where the broken version of the mod initially resided before I removed it and added the fixed version.
Can you try it either through a fresh install or after removing the original config file in your existing install?
Apologies, I should have specified. I tested it in a 1.19.2 installation where the broken version of the mod initially resided before I removed it and added the fixed version.
Can you try it either through a fresh install or after removing the original config file in your existing install?
All the original sapience configs were removed when I tested.
I get this message about once a second in my console window:
[15:51:20] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file F:\GAMES\Minecraft\MultiMC\instances\BeanPunk\minecraft\config\sapience-common.toml is not correct. Correcting