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 might be hard to understand #363

Closed
SGZ-Creations opened this issue Jul 27, 2021 · 2 comments
Closed

Config file might be hard to understand #363

SGZ-Creations opened this issue Jul 27, 2021 · 2 comments
Labels

Comments

@SGZ-Creations
Copy link

  • Versions
    Minecraft: 1.16.5

Scaling Health: 4.0.5+5
Silent Lib: 4.9.6
Forge: 36.2.0
Modpack: ATM6 + custom added mods to pack. custom are not on list won't works so these are the custom on image:
image

  • Expected Behavior + Actual Behavior:
    Hey. I started a game while doing so I saw the difficulty in game increase. So I went to look for config in game, but only option was by files. So I started reading trough changed all the thing I wanted to change as of planning a server where it can't have health increase because the save will be unplayable when mobs reaches a specific health value. Since they won't die of fire damage because of to much health during the day and that cause it lag out.
    Tho back to the config. I changed the part about mobs health increase. Then when I was about to start up the save it only come to this point on Image: (1) and stood there for about 5-15 min before giving up thinking it was corrupted. So I started a new save saw that hearts was still the same as on Classic + Scaling = Awesome. just missing some tweaks. #362 look for any solution about post Classic + Scaling = Awesome. just missing some tweaks. #362. Sadly I couldn't find much but still changed something that again made the same hang on load. Just for 3-8h instead of 5-15 min. and even after that it still was stuck loading on save. And today {27/07/21} I noticed on a new save that the config file (game_setting.toml) was partially changed back to it's defaults by just loading the modpack it is placed in/on. Images: (2) Before changes not 100% default + not all settings. Image: (3) After putting the setting I want to play with (4) after launching the pack again + reload of file in use warning.

  • Links/Images

image
2.
image
3.
image
4.
image
image

  • Steps to Reproduce the Problem:
    The images +The total explanation about issue hopefully gives u the answer u need.

  • End note:
    Might have fond some fix and got to understand the file better but I'll post to be 100% sure that what might be an issue get's solved and what's not an issue is just dropped.

@Mr-Syntax
Copy link

if you edit the files even while being in the minecraft menu some of them will instantly make a copy that you are editing instead, try sorting your folder by file extension and see if there are any backup file extension related to scaling health, delete them + close minecraft completely -> edit the config and save -> run minecraft

alternately if this isent working, create a blank pack and copy all the mods and configs into that folder and edit i there then it has to work!

but i just found some settings in the config that are straight up not working so that might be what your experiencing

@SGZ-Creations
Copy link
Author

if you edit the files even while being in the minecraft menu some of them will instantly make a copy that you are editing instead.

Answer: have been aware since before the post.

Tho my issue where that i edited numbers that still changed after logging out, changing the file then logging back in still
it changed back. automatically
Exampel 1
image

Exsampel 2
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants