Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 9 months ago
Updated 7 hours ago
All versions
1.5.3+26.3-neoforge
Release
Latitude 1.5.3+26.3-neoforge7 hours ago 28
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
Stable release of Latitude 1.5.3.
NEW
- The analog compass can attach to the hotbar alongside the digital compass. The dial uses space beside the bar when available and moves above it when space is limited.
- Drag either attached compass to detach it and position it freely.
FIXED
- Switching compass styles no longer leaves analog dragging blocked by saved digital attachment settings.
- HUD Studio uses Minecraft 26.3's primary mouse-button mapping, restoring dragging for the compass, title, and detached location text.
- Both Latitude shortcuts are registered with the loader so Minecraft can list and rebind them in Controls.
- Biome fallback and reroll pools respect a saved world's original provider roster.
- Known legacy cold-wetland roster entries are migrated without admitting unrelated new providers into existing worlds.
- Obsolete spawn-picker networking has been removed.
IMPROVED
- Attached compass previews and hit bounds use the same placement rules. Detaching keeps the cursor grab point and updates the attachment switch.
- Development-only clipboard utilities are excluded from the packaged game JARs and Gradle sources JARs.
KNOWN ISSUES
- An underwater initial spawn has been observed in a new Creative-mode world on NeoForge 26.1.2. Its scope across seeds, game modes, and loaders has not been established. This release does not claim to fix it.
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:PBwujSsd:KJNQJKAp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PBwujSsd:KJNQJKAp"
}

