1.18.2 version Crash when change server config, World wont load

Question

1.18.2 version Crash when change server config, World wont load

Daihok41 opened this issue 3 years ago · 2 comments

Daihok41 commented 3 years ago

1.18.2 version Crash when change server config, World wont load. If leave the config normal world will load fine.

---- Minecraft Crash Report ----
// I let you down. Sorry :(

Time: 3/28/22, 6:56 PM
Description: Exception in server tick loop

net.minecraftforge.fml.config.ConfigFileTypeHandler$ConfigLoadingException: Failed loading config file betteranimalsplus-server.toml of type SERVER for modid betteranimalsplus
at net.minecraftforge.fml.config.ConfigFileTypeHandler.lambda$reader$1(ConfigFileTypeHandler.java:61) ~[fmlcore-1.18.2-40.0.32.jar%23229!/:?] {}
at net.minecraftforge.fml.config.ConfigTracker.openConfig(ConfigTracker.java:74) ~[fmlcore-1.18.2-40.0.32.jar%23229!/:?] {}
at net.minecraftforge.fml.config.ConfigTracker.lambda$loadConfigs$1(ConfigTracker.java:64) ~[fmlcore-1.18.2-40.0.32.jar%23229!/:?] {}
at java.lang.Iterable.forEach(Iterable.java:75) ~[?:?] {re:mixin}
at java.util.Collections$SynchronizedCollection.forEach(Collections.java:2131) ~[?:?] {}
at net.minecraftforge.fml.config.ConfigTracker.loadConfigs(ConfigTracker.java:64) ~[fmlcore-1.18.2-40.0.32.jar%23229!/:?] {}
at net.minecraftforge.server.ServerLifecycleHooks.handleServerAboutToStart(ServerLifecycleHooks.java:81) ~[forge-1.18.2-40.0.32-universal.jar%23232!/:?] {re:classloading}
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] {}
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?] {}
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] {}
at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] {}
at net.optifine.reflect.Reflector.callBoolean(Reflector.java:710) ~[preview_OptiFine_1.18.2_HD_U_H7_pre2.jar%23233!/:?] {re:classloading}
at net.minecraft.client.server.IntegratedServer.m_7038_(IntegratedServer.java:81) ~[client-1.18.2-20220228.144236-srg.jar%23228!/:?] {re:classloading,xf:OptiFine:default}
at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:661) ~[client-1.18.2-20220228.144236-srg.jar%23228!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.m_177918_(MinecraftServer.java:261) ~[client-1.18.2-20220228.144236-srg.jar%23228!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B}
at java.lang.Thread.run(Thread.java:833) [?:?] {re:mixin}
Caused by: com.electronwill.nightconfig.core.io.ParsingException: Invalid value containing only whitespaces
at com.electronwill.nightconfig.toml.ValueParser.parse(ValueParser.java:62) ~[toml-3.6.4.jar%238!/:?] {}
at com.electronwill.nightconfig.toml.ValueParser.parse(ValueParser.java:69) ~[toml-3.6.4.jar%238!/:?] {}
at com.electronwill.nightconfig.toml.TableParser.parseNormal(TableParser.java:57) ~[toml-3.6.4.jar%238!/:?] {}
at com.electronwill.nightconfig.toml.TomlParser.parse(TomlParser.java:88) ~[toml-3.6.4.jar%238!/:?] {}
at com.electronwill.nightconfig.toml.TomlParser.parse(TomlParser.java:37) ~[toml-3.6.4.jar%238!/:?] {}
at com.electronwill.nightconfig.core.io.ConfigParser.parse(ConfigParser.java:113) ~[core-3.6.4.jar%237!/:?] {}
at com.electronwill.nightconfig.core.io.ConfigParser.parse(ConfigParser.java:219) ~[core-3.6.4.jar%237!/:?] {}
at com.electronwill.nightconfig.core.io.ConfigParser.parse(ConfigParser.java:202) ~[core-3.6.4.jar%237!/:?] {}
at com.electronwill.nightconfig.core.file.WriteSyncFileConfig.load(WriteSyncFileConfig.java:73) ~[core-3.6.4.jar%237!/:?] {}
at com.electronwill.nightconfig.core.file.AutosaveCommentedFileConfig.load(AutosaveCommentedFileConfig.java:85) ~[core-3.6.4.jar%237!/:?] {}
at net.minecraftforge.fml.config.ConfigFileTypeHandler.lambda$reader$1(ConfigFileTypeHandler.java:57) ~[fmlcore-1.18.2-40.0.32.jar%23229!/:?] {}
... 15 more

A detailed walkthrough of the error, its code path and all known details is as follows:

itsmeow · Answer 1 · 2022-03-29T10:07:49.000Z

This is not enough information to diagnose the problem. At least include the changes made to the config, what you tried, the required version info for a crash report, etc.

itsmeow · Answer 2 · 2022-04-08T19:29:39.000Z

Closing due to lack of information and likely user error.

Share to

A detailed walkthrough of the error, its code path and all known details is as follows: