
TeleportBlock
This mod adds a Teleport Block that allows teleportation between two linked ports, making travel faster and more convenient. Teleport distance and cooldown duration can be fully customized through a separate config file to fit different playstyles.
neoforge_2.0.0
Compatibility
Changes
Version 2.0.0
Ender Pearl Teleport Improvements
- Ender pearls hitting a linked Teleport Block now respect a cooldown, configurable via
pearl_cooldown_seconds(default: 1 second) - Ender pearls now work with Waystone-linked blocks, not just block-to-block links
- Ender pearl teleports use the same unified logic as click and passive teleports, ensuring consistent behavior across all teleport methods
Tick-Based Cooldowns
- Cooldown system now uses server tick time instead of real-world clock time
- Prevents cooldowns from expiring early during server lag (low TPS)
- Cooldown no longer consumed on a failed teleport (blocked destination or FTB Chunks protection)
JourneyMap Waypoints
- Waypoints now appear immediately when blocks are linked, without requiring a rejoin
- Waypoints are now created in the correct dimension instead of always defaulting to the Overworld
Map Markers
- Removed the oversized name plate bar beneath map marker icons that obscured map content
Recipe Viewer Support
- EMI and REI plugins now display the item description, matching the existing JEI integration
Internal Improvements
- Unified all teleport paths (click, passive, ender pearl, waystone) into a single method, eliminating three copies of the same logic
- Replaced
java.awt.Color.HSBtoRGBwith a custom implementation for compatibility with headless dedicated server JVMs - Fixed a potential null pointer exception in cooldown time remaining calculation
- Waystone teleport coordinates now correctly pass through Sable sub-level conversion
- Removed unused import in block registration
- Added
pearl_cooldown_secondsto the config file
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:9oxmCyus:Nv4X7MPf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9oxmCyus:Nv4X7MPf"
}
