Changes made to Structure Settings ingame are not saved to the config

[leiseg]

Minecraft version information

26.1.2

Mod loader information

Fabric

Mod loader version information

0.19.2

Mod version information

2.0.23

Expected Behavior

When editing properties of individual structures (e. g. Start height type, Minimum height, Maximum height etc.), the changes made should be saved to the structurify.json config file.

Actual Behavior

Currently, if you edit a structures' properties like mentioned above, the changes made aren't saved to the structurify.json config file. They are visually applied in the ingame config GUI, but after a restarting the game the changes made are reset.

Reproduction Steps

In my case:

1. Install Remnants 1.0 alongside Structurify
2. Start the game and open the config GUI of Structurify
3. Search for Remnants and open it's structure settings
4. Change the Minimum height to -54 and the Maximum height to -44
5. See that you probably have to enter -54 for Minimum height again (maybe this is another small bug)
6. Save these changes and restart the game
7. Open the structure settings for Remnants again
8. See that the changes made are reset

Screenshots & files

This is the config after doing the above listed steps:

{
  "config_version": "2.0.23",
  "config_datetime": "2026-05-14_16-50-08",
  "general": {
    "disable_all_structures": false,
    "prevent_structure_overlap": false,
    "enable_global_spacing_and_separation_modifier": false,
    "global_spacing_and_separation_modifier": 1.0
  },
  "structure_namespaces": [],
  "structures": [],
  "structure_sets": [],
  "structure_template_pools": []
}

[Faboslav]

Partially resolved with 2.0.24, values of the start_height still partially resets on change

[Samuel4El]

I can confirm that this is a big problem right now. Just lost over 3 hours of finetuning after closing my game. The override and manual biome editing settings are unbelievably broken, the config file I ended up with was an absolute mess.

[Faboslav]

I can confirm that this is a big problem right now. Just lost over 3 hours of finetuning after closing my game. The override and manual biome editing settings are unbelievably broken, the config file I ended up with was an absolute mess.

This was purely related to one field, in this case start_height, not the whole settings.

[Samuel4El]

This was purely related to one field, in this case start_height, not the whole settings.

Hmm, then there is another problem. I've encountered this issue many times now, your settings just reset if you open the config menu and edit settings more than once in a single game session. I don't know what settings are exactly affected but it's a lot of them.

[Faboslav]

This was purely related to one field, in this case start_height, not the whole settings.

Hmm, then there is another problem. I've encountered this issue many times now, your settings just reset if you open the config menu and edit settings more than once in a single game session. I don't know what settings are exactly affected but it's a lot of them.

Then provide reproduction steps, with more info and logs please. Make sure this happens on the latest version of the mod.

[Samuel4El]

Then provide reproduction steps, with more info and logs please. Make sure this happens on the latest version of the mod.

Okay, here you go.

1. install structurify and its dependencies.
2. launch the game and open the config menu.
3. make any edit to the biomes of any structure, save and exit the config menu (closing the game is not necessary).
4. open the structurify.json file to see if the changes went through.
5. open the config menu again and make any edit to an 'override global settings' of any structure, then save and close the config menu again.
6. open the structurify.json file again to see if your previous changes are still there.

[Faboslav]

2. e

I screwed up and forgot to do a release, can you please try with Can you please try with https://github.com/Faboslav/structurify/releases/tag/2.0.32?

[Samuel4El]

Is this still necessary? Saw the update was already out

[Faboslav]

@Samuel4El If you tested on 2.0.32 then not, but if you tested on older version, then another test on newest version would be appreciated, as the issue should be hopefully fixed there.

[stevekirby21]

it wasnt fixed on 2.0.32, i only notice biomes not saving not 100% sure about other settings
a few did save somehow though, when i look at the config, it looks like it only accepted the biomes of 1 structure from each set
so "towers" might have like 10 different towers with biomes i changed, but it only saves towers:dragon_tower #minecraft:is_forest. every other tower didnt save or has whitelisted_biomes "". i also only see #minecraft:is_forest in the whitelists that actually managed to save.
every set i modified is like this not sure if its related just something i noticed

[Faboslav]

it wasnt fixed on 2.0.32, i only notice biomes not saving not 100% sure about other settings a few did save somehow though, when i look at the config, it looks like it only accepted the biomes of 1 structure from each set so "towers" might have like 10 different towers with biomes i changed, but it only saves towers:dragon_tower #minecraft:is_forest. every other tower didnt save or has whitelisted_biomes "". i also only see #minecraft:is_forest in the whitelists that actually managed to save. every set i modified is like this not sure if its related just something i noticed

I finally reproduced this in little bit different way, but there is some kind of issue, thanks for the replies!

[Faboslav]

Note: Actually, this uncovered multiple other similar problems, which will be fixed in the next update

[Faboslav]

Release is out, please let me know, if it works now.