[1.19.2] Server configuration file dimstorage-server.toml keeps reverting DimTablet.allow_list to default on load / sometimes on edit.
DemifiendCruithne opened this issue ยท 4 comments
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
The world I am using here only has the following mods: DimStorage, edivadlib, and configured - configured is solely for data collection simplicity and has no effect on the results.
It is being run only on singleplayer and launched offline.
Whenever loading server configs, the key DimTablet.allow_list
in server configuration file dimstorage-server.toml
is reverted to its default with the following error; done here via configured for log simplicity, but it worked the exact same in-world.
[21:39:34] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:34] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key DimTablet.allow_list was corrected from [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone] to its default, [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone].
[21:39:34] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:34] [Render thread/INFO] [configured/]: Started editing 'dimstorage-server.toml'
[21:39:35] [Render thread/INFO] [configured/]: Stopped editing 'dimstorage-server.toml'
[21:39:40] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:40] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key DimTablet.allow_list was corrected from [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone] to its default, [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone].
[21:39:40] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:40] [Render thread/INFO] [configured/]: Started editing 'dimstorage-server.toml'
[21:39:41] [Render thread/INFO] [configured/]: Stopped editing 'dimstorage-server.toml'
I show it duplicated here because it happens every time - even if the config has not been changed. As you can see, the 'corrected' version and the default are exactly the same.
When checking the allow list in configured, the following occurs:
Here I just clicked edit on an existing entry, and it implies that it's invalid with being red and unable to apply changes (of which i made none).
When i have a tablet properly linked to a chest and with auto-pickup enabled, any item in DimTablet.allow_list
is picked up by it as expected. To me (a python user, so i may be wrong), this implies that the function is expecting the wrong type of variable, but is working as expected when given a list - but because the list isn't what the function expects, it reverts to the default, which is also a list and works as expected to the user.
Another interesting note is that using /dimtablet add
is immediately triggering the correction:
[21:54:38] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (4)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:54:38] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Item added to the list
[21:54:44] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Disabled autocollect
[21:54:44] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Enabled autocollect
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] These are the items that the DimTablet will move:
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:dirt
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:gravel
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:cobblestone
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:granite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:diorite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:andesite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:sand
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:sandstone
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:netherrack
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:end_stone
(The world number changed because i forgot to allow commands on New World 3 and made a new one with no changes besides allowing commands)
Here, I had a stick in my mainhand, and ran /dimtablet add
- the stick did not go into the tablet. I then disabled and enabled the autocollect to show that it was on, and ran /dimtablet list
to show that the list is still only the defaults.
(One interesting note i don't understand - something in my main world is preventing the [Thread-0/WARN]
messages throughout the whole log, and if i add something to the list it persists and thus works until the config is reloaded in some way. So I think both the Thread-0
and the Render thread
'correcting' messages are making the actual correction.)
I hope this is enough/good information to help with the problem, and thank you for your time :)
How can I reproduce this bug or crash?
- Run an instance of 1.19.2 with DimStorage and EdivadLib. Configured is helpful but not necessary.
- Open the world and check the logs - even if the config is already default, it will have been 'corrected' to default.
- If you don't have a dimensional tablet linked to a dimensional chest already, either make them or use /give, creative, or some other form of cheating for testing purpose. Make sure the tablet has autocollect on.
- Hold any item that isn't on the defaults list in your mainhand. Run
/dimtablet add
. - If the item remains in your mainhand - check the log again and/or
/dimtablet list
, you'll see that the item you attempted to add is not on the list, even as the mod outputs to chat saying it was added. - If the item is put into the tablet - log out of the world and back in, and get another of that same item. As the config will have been reset again, it now won't go into the tablet with autocollect on unless you add it agani.
Configuration
- Mod version: 7.2.0
- Lib version: 1.2.0
- Forge version: 43.2.14
- Minecraft version: 1.19.2
Relevant log output
[21:39:34] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:34] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key DimTablet.allow_list was corrected from [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone] to its default, [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone].
[21:39:34] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:34] [Render thread/INFO] [configured/]: Started editing 'dimstorage-server.toml'
[21:39:35] [Render thread/INFO] [configured/]: Stopped editing 'dimstorage-server.toml'
[21:39:40] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:40] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key DimTablet.allow_list was corrected from [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone] to its default, [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone].
[21:39:40] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:40] [Render thread/INFO] [configured/]: Started editing 'dimstorage-server.toml'
[21:39:41] [Render thread/INFO] [configured/]: Stopped editing 'dimstorage-server.toml'
[21:54:38] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (4)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:54:38] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Item added to the list
[21:54:44] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Disabled autocollect
[21:54:44] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Enabled autocollect
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] These are the items that the DimTablet will move:
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:dirt
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:gravel
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:cobblestone
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:granite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:diorite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:andesite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:sand
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:sandstone
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:netherrack
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:end_stone
Anything else?
No response
Edit is because i forgot to finish a sentence (re: running offline) after rewriting it. apologies
okay - would it be possible to request an update planned for 1.19.2 even if just for this issue and no other changes?
i would upgrade, but a lot of mods in my pack aren't updated beyond 1.19.2 - notably including thermal series, which is a vital component to many modpacks.
if you'd rather not for whatever reason though, i completely understand, and thank you for your time anyway :)
i'm also not 100% sure what the linked issue is for, unless it's just noting the commit with the fix? since onedrive is irrelevant (i'm on linux so it isn't even an accidental possibility)
in theory i can try and merge the fix in myself and that's why it's linked...
This bug has been fixed in the latest version of the mod and there is currently no update planned for 1.19.2 #50