Behavior
When creating a backup on vanilla Minecraft 26.3+, Prime Backup fails to detect that the world has been saved. It waits until save_world_max_wait is reached and the backup is aborted.
Reason
Starting with vanilla Minecraft 26.3-snapshot-3, Mojang changed the log format for system messages.
Before:
[Server] [00:46:11] [Server thread/INFO]: Saved the game
Since 26.3-snapshot-3:
[Server] [00:46:11] [Server thread/INFO]: System chat: Saved the game
Prime Backup's default saved_world_regex does not match the new message.
To Fix
Add the new pattern under server.saved_world_regex in config/prime_backup/config.json:
{
"server": {
"saved_world_regex": [
"System chat: Saved the game"
]
}
}
The new complete default value should be:
{
"server": {
"saved_world_regex": [
"Saved the game",
"Saved the world",
"System chat: Saved the game"
]
}
}
Affected environment
- Minecrat >= 26.3-snapshot-3
- Prime Backup installtion with
config/prime_backup/config.json created Prime Backup < v1.14.0
Behavior
When creating a backup on vanilla Minecraft 26.3+, Prime Backup fails to detect that the world has been saved. It waits until
save_world_max_waitis reached and the backup is aborted.Reason
Starting with vanilla Minecraft
26.3-snapshot-3, Mojang changed the log format for system messages.Before:
Since
26.3-snapshot-3:Prime Backup's default
saved_world_regexdoes not match the new message.To Fix
Add the new pattern under
server.saved_world_regexinconfig/prime_backup/config.json:{ "server": { "saved_world_regex": [ "System chat: Saved the game" ] } }The new complete default value should be:
{ "server": { "saved_world_regex": [ "Saved the game", "Saved the world", "System chat: Saved the game" ] } }Affected environment
config/prime_backup/config.jsoncreated Prime Backup < v1.14.0