Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated last month
All versions
0.2.0
Release
Lodestone Warps 0.2.04 months ago 10
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
Lodestone Warps 0.2.0
Feature release for Minecraft 26.2.
Added
- Added LuckPerms-compatible permissions through Fabric Permissions API.
- Added
lodestone_teleport.usepermission. - Added
lodestone_teleport.renamepermission. - Added
requirePermissionsconfig option. - Added configurable command names:
commandNamefallbackCommandName
- Added default
/warpcommand. - Added safe fallback
/lodestone_warpcommand. - Added teleport by Lodestone display name.
- Added duplicate-name handling for
/warp tp <name>. - Added clickable duplicate-name destination choices.
- Added
serverLanguageconfig option for vanilla UI fallback text. - Added English and Spanish wiki documentation.
- Updated README for Modrinth and CurseForge usage.
Changed
- Lodestone Warps now always tries to register the safe fallback command.
- Clickable duplicate-name teleport choices now use internal custom actions instead of chat commands.
- Vanilla UI fallback text now defaults to English.
Fixed
- Avoided Minecraft's command confirmation screen when clicking duplicate-name teleport choices.
Compatibility
- Minecraft:
26.2 - Fabric Loader:
>=0.19.3 - Fabric API:
0.152.2+26.2 - Fabric Permissions API:
1.0.1+c3369b134c - Java:
25+
Notes
Servers that do not want permission checks can set:
"requirePermissions": false
Servers that want vanilla UI text in Spanish can set:
"serverLanguage": "es_es"
Commits Included
- Release Lodestone Warps 0.2.0 (c4e6406)
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:zLt1P8Tw:IsYiEeQX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zLt1P8Tw:IsYiEeQX"
}

