All versions
1.1.0
Release
MineZero - A Re:Zero Mod 1.1.02 months ago 376
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
MineZero v1.1.0
Changed
- Renamed commands, gamerules, and config keys to a unified, self-explanatory naming convention (see
docs/HowItWorks.md→ "Naming Convention"). Re:Zero terminology ("Subaru", "RBD") no longer appears in any identifier or user-facing message. - Commands:
/setSubaruPlayer→/setanchor/triggerRBD→/restorecheckpoint/setcheckpointis unchanged.
- Gamerules (constants in
ModGameRules.javanow mirror the registered keys):checkpointFixedInterval→autoCheckpointIntervalSecondsuseRandomCheckpointInterval→autoCheckpointRandomIntervalEnabledrandomCheckpointLowerBound→autoCheckpointRandomMinSecondsrandomCheckpointUpperBound→autoCheckpointRandomMaxSecondsfluteCooldownEnabled→artifactFluteCooldownEnabledfluteCooldownDuration→artifactFluteCooldownSecondssetCheckpointOnWorldCreation→checkpointOnWorldCreationautoCheckpointEnabledandartifactFluteEnabledare unchanged.
- Config:
[general] deathChime = "CLASSIC"|"ALTERNATE"→[sounds] restoreSound = "death_chime"|"alt_death_chime"(values now match the mod's sound IDs). The empty[checkpoints]section was removed. - Every gamerule now has a display name and description in the gamerule edit screen (
en_us.json).
Backward compatibility
- Commands: the old names
/setSubaruPlayerand/triggerRBDremain registered as deprecated aliases for one release cycle and will then be removed. - Gamerules: hard rename, no aliases, Forge gamerules are independent registrations, so an "alias" would be a second rule whose value silently diverges from the real one. Existing worlds keep the old entries in level.dat harmlessly; the renamed rules start at their defaults, so re-apply any non-default values with
/gameruleafter updating. - Config: hard rename, Forge regenerates the file with the new
[sounds] restoreSoundkey at its default. The legacy valuesCLASSIC/ALTERNATEare still accepted if set manually.
Added
- Localization: all player-facing messages now use translation keys, with translations for Simplified Chinese (zh_cn), Russian (ru_ru), Brazilian Portuguese (pt_br), German (de_de), Spanish (es_es), French (fr_fr), Japanese (ja_jp), and Korean (ko_kr).
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:MimW5tUb:x8QOnqn9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MimW5tUb:x8QOnqn9"
}

