1.3.0
Compatibility
Changes
A big QOL and management update for Lattice. This release introduces a configurable in-game rulebook that players must accept before playing, a major command refactor with extended admin controls, improved config/date handling, and several compatibility and reliability fixes.
Short summary
- New: Enforceable Rulebook — display rules as an in-game book and require players to accept them.
- New: Powerful
/latticeadmin command with subcommands for config, MOTDs, illegal/allowed mods, pvp, rules, nick, status, and open dates. - Improved: Now supports per-dimension open dates (server, nether, end).
- Improved: Illegal-mod detection now supports an allowlist and improved mod/resource-pack sharing.
- Client+Server: Lattice must be installed on both server and client for full functionality (rules flow, mod sharing).
- Build & compatibility: Updated mappings/deps/build tooling for Minecraft 1.21.10 mappings and modern APIs.
Breaking changes / upgrade notes (must-read)
- Backup your existing config.json before upgrading.
- New
rulesarray expects JSON text components. See the README example for formatting. If you add rules, players will be prompted to accept them on join. - The mod must be installed on both server AND client for full rulebook and mod-sharing features to work.
- If you have automation or scripts that rely on the old
/latticesubcommand layout, update them: the admin command was expanded and refactored. - If you build Lattice from source, update your toolchain to match the versions in gradle.properties (Gradle 9.2, updated fabric/neoForge/parchment versions) and increase JVM heap if needed.
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:UQBDUlXi:1sJ28Phe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UQBDUlXi:1sJ28Phe"
}

