Jump to content

Recommended Posts

Posted

Hey all,

So I'm trying to set up a config for my mod and having some issues.  It keeps tossing the following error at me:

Quote

Configuration file path\modid-server.toml is not correct. Correcting
Incorrect key generalsettings was corrected from null to SimpleCommentedConfig:{}

I've been searching high and low to figure it out and I'm having a time of it.  I'm not sure if I found a forge bug or if I'm just missing something stupid, but in any case, hopefully someone here can help.  Code is as follows...

Main:

ModLoadingContext.get().registerConfig(ModConfig.Type.SERVER, ServerConfig.CONFIG, "modid-server.toml");
ServerConfig.loadConfig(ServerConfig.CONFIG, FMLPaths.CONFIGDIR.get().resolve("modid-server.toml").toString());

ServerConfig:

@Mod.EventBusSubscriber
public class ServerConfig {
	
	private static final ForgeConfigSpec.Builder BUILDER = new ForgeConfigSpec.Builder();
	public static final ForgeConfigSpec CONFIG;
	
	static {
		GeneralConfig.initServer(BUILDER);
		CONFIG = BUILDER.build();
	}
	
	public static void loadConfig(ForgeConfigSpec config, String path) {
		final CommentedFileConfig file = CommentedFileConfig.builder(new File(path)).sync().autosave().writingMode(WritingMode.REPLACE).build();
		file.load();
		config.setConfig(file);
	}

}

GeneralConfig:

public class GeneralConfig {
	public static ForgeConfigSpec.BooleanValue SIMPLE_DAY_CYCLE;
	
	protected static void initServer(ForgeConfigSpec.Builder server){
		setupGeneralSettingsConfig(server);
	}
	
	private static void setupGeneralSettingsConfig(ForgeConfigSpec.Builder builder){
		builder.comment("General Settings").push("generalsettings");
		SIMPLE_DAY_CYCLE = builder.comment("").define("simpledaycycle", false);
		builder.pop();
	}

}

 

Thanks, and have a great day!

Posted
9 hours ago, JayZX535 said:

Main:


ModLoadingContext.get().registerConfig(ModConfig.Type.SERVER, ServerConfig.CONFIG, "modid-server.toml");
ServerConfig.loadConfig(ServerConfig.CONFIG, FMLPaths.CONFIGDIR.get().resolve("modid-server.toml").toString());

 

I think this is the problem. According to documentation, you need to write it this way:

ModLoadingContext.get().registerConfig(ModConfig.Type.SERVER, ServerConfig.CONFIG);
ServerConfig.loadConfig(ServerConfig.CONFIG, FMLPaths.CONFIGDIR.get().resolve(modid +"-server.toml"));

You don't need to specify the file name, it will be your MODID name. Keep it simple and you will stay out of trouble ;)

 

and this:

ServerConfig.loadConfig(ServerConfig.CONFIG, FMLPaths.CONFIGDIR.get().resolve("modid-server.toml").toString());

 

will not compile, the last parameter needs to be Path not String

†GnR† Slash

can one man truly make a difference?

Posted (edited)
8 hours ago, GnRSlashSP said:

I think this is the problem. According to documentation, you need to write it this way:


ModLoadingContext.get().registerConfig(ModConfig.Type.SERVER, ServerConfig.CONFIG);
ServerConfig.loadConfig(ServerConfig.CONFIG, FMLPaths.CONFIGDIR.get().resolve(modid +"-server.toml"));

You don't need to specify the file name, it will be your MODID name. Keep it simple and you will stay out of trouble ;)

 

and this:


ServerConfig.loadConfig(ServerConfig.CONFIG, FMLPaths.CONFIGDIR.get().resolve("modid-server.toml").toString());

 

will not compile, the last parameter needs to be Path not String

Ah, I'd been trying the first part that way originally but saw a suggestion to try it like this.  Didn't help, so I've changed it back now.

Hmmm.  I had mine set up to take a string (as noted in my ServerConfig file) but I tried changing it to a path.  It now looks like this:

@Mod.EventBusSubscriber
public class ServerConfig {
	
	private static final ForgeConfigSpec.Builder BUILDER = new ForgeConfigSpec.Builder();
	public static final ForgeConfigSpec CONFIG;
	
	static {
		GeneralConfig.initServer(BUILDER);
		CONFIG = BUILDER.build();
	}
	
	public static void loadConfig(ForgeConfigSpec config, Path path) {
		final CommentedFileConfig file = CommentedFileConfig.builder(path).sync().autosave().writingMode(WritingMode.REPLACE).build();
		file.load();
		config.setConfig(file);
	}

}

But still no dice.  Still getting the

Quote

Configuration file is not correct. Correcting
Incorrect key generalsettings was corrected from null to SimpleCommentedConfig:{}

Incorrect key generalsettings.simpledaycycle was corrected from null to false

error :/

Edited by JayZX535
Posted (edited)

Anyone know what else I could try to fix this?  I'm truly at a loss :/

 

Edit 6/30/20: Updating for anyone who may come here seeking answers later: I... fixed it?  I ended up recreating my modding workspace, and now it's working again.  So I'm guessing something got goofed up there?  Truly, this is one of the more mysterious things I've encountered, and I wish I had a more solid idea on what I did.  But when all else fails, redo your workspace I guess?

Edited by JayZX535
Adding a fix. Well. Sort of.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.