AMP would be perfect when.....

[Ir3nicuz]

I confirm that

• I have searched for an existing feature request matching the description.

Feature Description

the automatic repair and auto-update features would be reliable controlable ( and deactivateable) and
the documentation would reflect and explain transparently all possibilities of the json and kvp data structures.

Actually it's just guessing and reverse engineering to pin down the available functions.

[IceOfWraith]

You'll need to explain yourself better if you want anything changed.

AMP doesn't have an automatic update functionality for AMP itself. You have to follow the update guide at this time. If you're referring to game servers getting updated automatically, please explain what's not working.
https://discourse.cubecoders.com/t/how-to-update-amp-to-the-latest-version/2297

If you're referring to the generic templates needing an adjustment, there's documentation for that as well.
https://github.com/CubeCoders/AMP/wiki/Configuring-the-'Generic'-AMP-module

[Ir3nicuz]

I talk about the automatic double and triple triggering of updatestages for no reason and serverrestarts after clicking "stop", not restart. There are running much intransparent supervision logics in the background nowhere documented.
I don't talk about AMP updates.

And the linked documentation not nearly explains half of the functions and dependencies between kvp and Json settings, AMP behaviour and panel control elements.

Trying to trace problems is just a mess since AMP fires some unknown automatics in between.

[IceOfWraith]

Unfortunately, I think there's a language barrier here. I'm still unsure what the exact issues are you are seeing. AMP doesn't update a game server when you push the stop button and I've yet to hear others report that behavior.

If you can share your logs from that instance it might help. You can click the folder icon for the instance and they are under AMP_Logs. Share one where you see the issue.

[Ir3nicuz]

I wrote some templates you can find in my repository.
I bypass and don't configure the steamcmd stage and I defined a powershell script to call steamcmd because I want live logging by a conhost wrapper call.

AMPLOG 2026-02-07 13-56-50.log

In the log you see three runs of my updatestages. The first is triggered by clicking "update". Then I don't set the exe settings correctly to cause a server startup fail at clicking "launch the server". Clicking "launch the server" calls the updatestages two times again. I want to disable this behaviour. I dont want a "auto-repair-logic" and I don't see any settings or variables for this in the web panel or documentation.

The second is a little bit difficultier to reproduce. If the server is stuck in some launch exception error, clicking "stop" does not stop the server. It just triggers a restart. To stop the server I have to kill the whole instance. Since I repaired the cause by installing the missing dependencies it is difficult to reproduce now.

And all these is more difficult since the json settings structure and genericmodule possibilities seems intransparent compared to what settings in the panel are available.

[IceOfWraith]

It sounds like your server is failing to start if it's automatically running the update stages again. Here's the setting that controls how many times AMP will try to restart the app if it fails.

Limits.AutoRetryCount=2

[IceOfWraith]

Search in the top right of AMP for Show Development Information to enable the setting names as they are in the kvp files.

[Ir3nicuz]

In the GenericsModule.kvp of my instance the settting is "Limits.AutoRetryCount=5". Since the Value is "5" this can not cause the "double" update. And I would assume "AutoRetry" is applicable for server run fails, not "Updates". But if I click manually "stop the server", AMP should know that this was a "wanted click to stop" and not apply autorestarts. :)

In my Panel is no "Advanced" or "Developer" switch. I searched for it multiple times at all submenus i could find.

[IceOfWraith]

Yes, I need the logs mentioned above to understand what you're seeing there. You have to search for what I put exactly in the top right of AMP in the search box.