Tags
Creators
Details
All versions
1.0.0
Release
TeleSign 1.0.03 weeks ago 18
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
26.2
Platforms
Paper
Purpur
Changes
Added
- Both sides of a sign can teleport, each to its own destination: write
[TELESIGN]on the front, the back or both. Clicking a sign uses the side the player is facing.
Changed
- Renamed from atsSignTeleport to TeleSign. The plugin folder is
plugins/TeleSign, the command is/telesign reloadwith the/tsignsalias, and the permissions aretelesign.use,telesign.create,telesign.breakandtelesign.reload(all part oftelesign.*). Teleport signs made with atsSignTeleport are not recognized anymore. - The first line that turns a sign into a teleport sign is
[TELESIGN]instead of[TELEPORT]. - Requires Paper (or a fork such as Purpur) 26.2 or newer and Java 25. Spigot is no longer supported.
- The sign lines in
config.ymluse the MiniMessage format instead of&color codes, with the<world>,<x>,<y>,<z>,<yaw>and<pitch>placeholders instead of%WORLD%,%X%and the like. A world name is always shown as written, never read as formatting. /telesign reloadchecks the config before applying it. An invalid file or alineslist without exactly four lines is not applied and the command says what is wrong with it; on startup it stops the plugin with that message. Before, fewer than four lines silently stopped signs from being created and refreshed.- Licensed under the Apache License 2.0.
Fixed
- Refreshing the signs no longer overwrites the front of a sign that was made a teleport sign on its back.
- Clicking a sign whose world does not exist anymore tells the player so instead of failing with an error.
- Region protection plugins are respected: clicking a teleport sign where such a plugin blocks the interaction no longer teleports, and a sign does not become a teleport sign where it blocks the change.
- The version shown by the server is the released version; it was fixed at 0.2.1 in
plugin.yml. - The server no longer downloads the JetBrains annotations library on startup; it is only needed to compile.
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:7VN6bx7n:I3IN97Hx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7VN6bx7n:I3IN97Hx"
}

