All versions
1.0.2
Release
Warp Signs 1.0.22 months ago 6
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Client and server
Changes
WarpSigns 1.0.2
Added
- Added
[Spawn]signs.
Usage
- Place
[Spawn]on the first line of a sign. - Right-click the sign to teleport to the global server spawn set with
/setspawn. - The remaining sign lines can be used for optional display text or decoration.
Changed
[Spawn]sign headers are colored based on the player’s current dimension:- Blue when the player is already in the Overworld.
- Green when the player is in another dimension and will travel to the Overworld spawn.
Protection
[Spawn]signs now receive the same protection as valid[Warp]signs.- Protected
[Spawn]signs and their supporting structure cannot be destroyed by:- Non-operator players
- TNT explosions
- Creeper explosions
- Piston movement or manipulation
- Operators must crouch to edit or remove protected
[Spawn]signs and their supporting blocks.
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:vj6pDgTd:8bgdlTRk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vj6pDgTd:8bgdlTRk"
}

