Tags
Creators
Details
Licensed ARR
Published last month
Updated last month
All versions
0.0.1
Alpha
Enlightened Lodestone 0.0.1last month 24
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Enlightened Lodestone v0.0.1
What's new
- Compass binding: Right-click a lodestone with a compass to link it and name your bearing.
- Candle ritual: Light 8 candles in the 3×3 around a lodestone to activate it.
- Linked teleport: Left-click an active lodestone with a linked compass to jump to another stone — even across dimensions.
- Bookmark return: Shift-right-click an active lodestone to go back to your last destination.
- Death recall: Right-click an active lodestone with an empty hand to return to where you last died.
- Unlink compasses: Use a grindstone to remove a compass link.
- Lodestone glow: Active stones glow on the client; nearby stones show candle progress as you get closer.
- Teleport feedback: Green pulse on success, soft blue pulse if teleport fails.
- Advancements — Lodestone Ways: 5 guide advancements from first bind through ritual, teleport, and return.
- Admin command:
/back(ops/creative) — return to your bookmark without needing the ritual active at the destination.
How it works (quick reference)
- Bind: Right-click lodestone + compass
- Activate: 8 lit candles in the ring
- Travel: Left-click lodestone + linked compass
- Go back: Shift + right-click active lodestone
- After death: Empty-hand right-click active lodestone
- Unlink: Grindstone
Notes
- Server required for all gameplay; client needed for glow and visual feedback.
- Linked lodestones and player bookmarks persist across restarts and respawn.
- Split from the larger Persistence mod — lodestone features only in this release.
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:scETggQ8:B3U5EwHQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:scETggQ8:B3U5EwHQ"
}

