Minecraft backup uses live save-off/save-on while "Backup While Running" is disabled

[wildwestdigital]

Operating System

Ubuntu 24.04.4 LTS

AMP Version and Build Date

2.8.0.4 - built 24/07/2026 17:13

AMP Release Stream

Mainline

I confirm that

• I have searched for an existing bug report for this issue.
• I am using the latest available version of AMP.
• my operating system is up-to-date.

Intended Action

I am trying to configure a scheduled local backup of a Minecraft Java/Paper server where AMP shuts the running game server down before taking the backup.

I created a new scheduler trigger and added "Backups - Take a backup" with:

• Local: Enabled
• S3: Disabled
• Sticky: Disabled
• Dirty Only: Disabled
• Backup While Running: Disabled
• Restart Even If Not Running: Disabled

The scheduler task was recreated from scratch in AMP 2.8.0.4 to rule out an older task created before the recent backup changes.

Expected Behaviour

With "Backup While Running" disabled, I expect AMP to gracefully stop the Minecraft server before staging/taking the backup.

If the server was running before the backup, I expect AMP's normal backup workflow to restore the appropriate running state afterward.

I would expect the Minecraft live-backup/quiesce procedure (save-all/save-off/save-on) to be used only when "Backup While Running" is enabled.

Actual Behaviour

The Minecraft server never shuts down.

Instead, AMP performs a live/quiesced backup while the server remains running. The Minecraft console shows:

Saving the game (this may take a moment!)
Saved the game
Automatic saving is now disabled

Automatic saving is now enabled

There is no normal Paper shutdown/startup sequence.

This behavior occurs even though "Backup While Running" is disabled.

I deleted/recreated the scheduler trigger and backup task from scratch in AMP 2.8.0.4 and tested it again. The behavior remained the same.

I have a screenshot of the newly created backup task showing "Backup While Running" disabled.

Reproduction

1. Install/update AMP to version 2.8.0.4.

2. Create or use a Minecraft Java Edition instance running Paper.

3. Start the Minecraft server and confirm that it is online.

4. Open the instance Scheduler.

5. Create a new trigger.

6. Add the task "Backups - Take a backup".

7. Configure the task as follows:

   • Local: Enabled
   • S3: Disabled
   • Sticky: Disabled
   • Dirty Only: Disabled
   • Backup While Running: Disabled
   • Restart Even If Not Running: Disabled

8. Save the newly created task.

9. Trigger the backup while the Minecraft server is running.

10. Watch the Minecraft console.

11. Observe that the server does not shut down. Instead, the console displays:

    Saving the game (this may take a moment!)
    Saved the game
    Automatic saving is now disabled

    Automatic saving is now enabled

12. Confirm that no normal Paper shutdown/startup sequence occurs.

Expected: with "Backup While Running" disabled, the server should be stopped for the backup.

Actual: AMP uses the live save/save-off/save-on backup procedure while the server remains running.