Configuration with Valheim - valheim_plus.cfg initialization issue

Technical Support
, ,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 13 on x86_64
Product AMP ‘Proteus’ v2.8.0.6 (Mainline)
Virtualization Docker
Application Valheim
Module GenericModule
Running in Container Yes
Current State 정지됨

Problem Description

Issue

Is there no way to apply my own configuration file other than manually editing the UI within the ValheimPlus menu?
I had modified org.bepinex.plugins.valheim_plus.cfg to match my existing server settings, but during a server update or startup, AMP overwrote the file’s contents to align with the “ValheimPlus” section of the AMP configuration.
Based on the experiences of other users, it seems that each setting must be configured individually within the AMP UI.
This feels highly inefficient.
I really wish I could at least import my own configuration file.

Reproduction Steps

  • Create Instance
  • Server Basic Settings
  • Enable ValheimPlus in the configuration
  • Migration of all mods from the existing game server
  • ValheimPlus reverts to default settings after the server starts.

re : 원인을 발견했습니다.

아무도 대답을 하지 않아서 직접 찾았습니다.
찾는 동안 스트레스가 심해 환불도 생각했습니다만 찾아버렸습니다.
다만, 열받았으니 모국어로 남깁니다.
다른 분들은 이런 고생을 하지 않았으면 좋겠습니다.

  1. ampinstmgr를 통해 발헤임 인스턴스를 down 시킵니다.

  2. /home/amp/.ampdata/instances/{발헤임 인스턴스 폴더}/metaconfig.json 편집
    #valheim_plus.cfg를 덮어 씌우는 주범
    “AutoMap”: true, > “AutoMap”: false,
    #valheim_plus.cfg의 옵션을 임포트 할 수 없던 이유
    “Importable”: false, > “Importable”: true,

  3. ampinstmgr를 통해 발헤임 인스턴스를 up 시킵니다.
    이후 발헤임에 접속해보면 정상적으로 내 valheim_plus.cfg의 옵션이 적용됨을 알 수 있습니다.

2

My understanding is that when you enable Valheim Plus in the config menu then AMP becomes the “source of truth” and will always override manual changes. I’m not 100% certain of this since I have made changes manually and they are saved, but other times they are overridden.

Also, AMP does not respect the new org.bepinex.plugins.valheim_plus.cfg file. On instance restarts AMP will create a new valheim_plus.dll and valheim_plus.cfg file every time. The valheim_plus.cfg then overwrites your edited org.bepinex.plugins.valheim_plus.cfg

My recommendation would be to disable Valheim Plus in the instance configuration and just manage it manually. It should then respect your settings, but also means you will need to update the .dll manually when new versions are released.

3

You are correct that AMP serves as the reference point.
That configuration is defined in the metaconfig.json file that I modified.
Even if you select the “Disable Valheim Plus” option in the instance configuration as you mentioned, AMP still overwrites our org.bepinex.plugins.valheim_plus.cfg file with its own template (based on the Valheim Plus options in the UI).
Based on my testing, the method I proposed worked correctly prior to the AMP update.
However, after the AMP update, the metaconfig.json file gets replaced by the server’s version.
As long as you keep that in mind, all the mods I configured work properly.
Thank you for your feedback.