Links
Tags
Creators
Details
1.0.0-mc1.21.1-eng
Compatibility
Changes
Cobblemon SaveGuard is a tool that prevents Cobblemon Pokémon data loss in case of disconnection by forcing synchronous saves and periodic automatic saves. It also allows you to manually trigger a save. You can also create manual backups, which will not be deleted unless you create another manual backup.
COMMANDS
For all players (no permissions)
/saveguard backup — creates a backup of your Pokémon (party + PC). A new backup overwrites the previous one.
/saveguard backup info — shows info about your backup (date, number of Pokémon).
Staff only (OP level 2)
/saveguard force [player] — forces a save. With no argument, saves all online players; with a name, saves only that one.
/saveguard status — shows the configuration (values are clickable to modify them on the fly).
/saveguard set <key> <value> — edits and saves a setting. Keys: autoSave, saveOnDisconnect, verboseLogging, extraDelay.
/saveguard reload — reloads the config from disk.
/saveguard inspect <player> party — shows the player’s party.
/saveguard inspect <player> box <1-50> — shows a specific PC box.
/saveguard verify <player> — integrity check: counts Pokémon in party/PC and checks that the factory is reachable (read‑only). /saveguard backups — lists all existing backups on the server, with date and Pokémon count.
/saveguard restore <player> — restores a player’s backup. Also accepts offline players (uses the name → profile). If the player is online, they are disconnected and will see their restored Pokémon upon rejoining.
This mod includes protection systems against duping. If a glitch is discovered, please report it immediately.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:U1gHYWbY:HmUcsPyB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:U1gHYWbY:HmUcsPyB"
}

