After looking through the logs I noticed that during the execution of the backups the script is not able to confirm the final command from the console: "save resume":
2022-02-08 17:24:52,102 DEBG 'backup-script' stdout output:
[info] Waiting for Minecraft console message 'Changes to the level are resumed', 5 retries left...
2022-02-08 17:25:02,109 DEBG 'backup-script' stdout output:
[info] Waiting for Minecraft console message 'Changes to the level are resumed', 4 retries left...
2022-02-08 17:25:12,115 DEBG 'backup-script' stdout output:
[info] Waiting for Minecraft console message 'Changes to the level are resumed', 3 retries left...
2022-02-08 17:25:22,122 DEBG 'backup-script' stdout output:
[info] Waiting for Minecraft console message 'Changes to the level are resumed', 2 retries left...
2022-02-08 17:25:32,129 DEBG 'backup-script' stdout output:
[info] Waiting for Minecraft console message 'Changes to the level are resumed', 1 retries left...
2022-02-08 17:25:42,135 DEBG 'backup-script' stdout output:
[warn] Minecraft console did not confirm message 'Changes to the level are resumed', giving up waiting...
[info] Minecraft worlds backup complete
Since the actual backup was successfull I ignored it for a while, but now after checking I found the issue:
The message that it is checking for "Changes to the level are resumed" has been changed with version 1.18.0.2 of BDS to "Changes to the world are resumed".
Would be great if you could correct this for the next release.
After looking through the logs I noticed that during the execution of the backups the script is not able to confirm the final command from the console: "save
resume":
Since the actual backup was successfull I ignored it for a while, but now after checking I found the issue:
The message that it is checking for "Changes to the level are resumed" has been changed with version 1.18.0.2 of BDS to "Changes to the world are resumed".
Would be great if you could correct this for the next release.