Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config file not correct #15

Open
cobaltcoyote opened this issue May 13, 2022 · 14 comments
Open

config file not correct #15

cobaltcoyote opened this issue May 13, 2022 · 14 comments
Labels
bug Something isn't working

Comments

@cobaltcoyote
Copy link

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

@Thelnfamous1
Copy link
Owner

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.

@border999
Copy link

I'm running minecraft through the game launcher, and am having the same issue.

@HerringBarrel
Copy link

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

@CopperGiraffe
Copy link

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

@daan2202
Copy link

daan2202 commented Jan 1, 2023

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.

@HoneyspringsBw
Copy link

Same issue here, except in 1.19.2.

@Thelnfamous1
Copy link
Owner

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.

@Thelnfamous1 Thelnfamous1 added the bug Something isn't working label Apr 19, 2023
@Thelnfamous1
Copy link
Owner

@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

@Thelnfamous1
Copy link
Owner

@HoneyspringsBw
Copy link

@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.

@Thelnfamous1
Copy link
Owner

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.

@HoneyspringsBw
Copy link

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.

@Thelnfamous1
Copy link
Owner

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?

@HoneyspringsBw
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants