Editing wings config.yaml resets to defaults

[MyDimeIsUp]

Current Behavior

When I change config.yaml, it will erase my changes and go back to default config.yaml

I am attempting to increase tmpfs_size via nano. When I change the file and restart wings, it will undo my changes and go back to defaults. I also tried adding "ignore_panel_config_updates: true" to config.yaml, but that also doesn't work and config.yaml is always set back to defaults. It seems it will always overwrite config.yaml given the inputs on the node's "Settings" tab on Pterodactyl web panel. It seems the code listed below always overwrites my config.

https://github.com/pterodactyl/wings/blob/develop/cmd/root.go#L157

Expected Behavior

Keep changes

Steps to Reproduce

Change config.yaml

Panel Version

1.11.11

Wings Version

1.11.13

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
• I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.

[TheBub10bge]

I can confirm that the config.yaml even with ignore_panel_config_updates: true .
That the config.yaml file resets to the previous state.

[MyDimeIsUp]

Yes it does. ignore_panel_config_updates is set to true at the bottom of my config.yaml

[TheBub10bge]

Yes it does. ignore_panel_config_updates is set to true at the bottom of my config.yaml

Sorry I meant to put “I can confirm “ in my post to try and help you get some attention to this mater. sorry for any confusion this may have caused. I also just went back and edited the original post to reflect this.

[matthewpi]

If someone could test one of the Wings binaries from https://github.com/pterodactyl/wings/actions/runs/17278359064 and report back it would help a lot. You will need to download them while logged-in to GitHub, you cannot curl the artifacts directly.