
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.
Links
Tags
Creators
Details
1.9.0
Compatibility
Changes
Version 1.9.0
Passive Portal Mode
- Toggle a linked Teleport Block into passive mode by Shift-right-clicking it with a Teleport Block item in hand
- In passive mode, simply stepping on top of the block teleports you - no right-click needed
- Both blocks in a pair share the same mode (toggling one toggles the other)
- Sneaking cancels the trigger, so you can safely stand on or walk past a passive block without teleporting
- Passive blocks emit a distinct "suction" particle effect instead of the normal idle particles
- Only players are teleported this way - mobs, projectiles, minecarts, and items are unaffected
Redstone Signal Relay
- Linked Teleport Blocks now relay a direct redstone signal to each other, separate from the existing comparator output
- Signal strength is halved (rounded up) across the link
- Signal resets to 0 automatically when a link is broken
Per-Link Cooldown
- Teleport cooldown is now tracked per link instead of globally per player
- Using one Teleport Block no longer blocks teleporting through unrelated pairs
- A minimum 1-tick cooldown is enforced for passive mode regardless of config, preventing spam if cooldown is set to 0
Linking Fixes
- Re-linking an already-linked block now properly unlinks its old partner instead of leaving a dangling connection
- Fixed a bug where toggling passive mode or updating the redstone signal could incorrectly unlink a block's partner
- Fixed a memory leak where pending links and cooldown data could accumulate indefinitely on long-running servers
Other Changes
- Removed a leftover debug log from the FTB Chunks compatibility check
- Minor stability fixes to item interaction handling
- 14 languages updated with new passive mode translation keys
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:UJOSEWf7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9oxmCyus:UJOSEWf7"
}
