
LodestoneTP Plugin
LodestoneTP is a survival-friendly teleporter network plugin that lets players and admins create, manage, and use teleporters by building simple multiblock structures (Lodestone + Blackstone Bricks). Everything is done through in-game Dialog GUIs.
Tags
Creators
Details
1.2.0
Compatibility
Changes
[1.2.0] - 2026-05-22
Added
adminBypassconfig option to control whether OPs andlodestonetp.adminbypass teleporter gameplay restrictions (cooldowns, costs, access checks, creation fees). Admin commands and admin GUIs are unaffected.- In-game admin GUI panel to toggle admin gameplay bypass at runtime.
- Magnetic Discovery advancement (
lodestone_discovery) for obtaining a Lodestone, withLodestoneAdvancementListenergranting it on join (if already in inventory), craft, pickup, or inventory click. - Split permission helpers for admin tools vs gameplay bypass (
hasGameplayBypass,canUse/canCreatewith plugin context,canAccessNetwork,bypassCooldown).
Changed
- Updated supported server version to Paper 26.1.2 (Minecraft 26.1.2).
- Raised minimum Java version to 25 for building and running the plugin.
- Teleporter flows (use, teleport, favorites, network access, creation fees) now respect
adminBypassinstead of always treating admins as exempt. - Warmup bypass now requires an explicit permission node (
lodestonetp.warmup.bypassby default) unless admin gameplay bypass applies. - Engineer advancement now requires Magnetic Discovery instead of the root advancement.
- Updated README, CONFIGURATION.md, and PERMISSIONS.md for the new bypass behavior.
- Plugin version bumped to
1.2.0.
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:x2Sw0e37:BYIzOL3D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:x2Sw0e37:BYIzOL3D"
}
