Links
Tags
Creators
Details
All versions
1.8.0
Release
SignWarpX 1.8.06 months ago 24
Compatibility
Minecraft: Java Edition
26.1.x
1.21.8–1.21.11
Platforms
Paper
Purpur
Changes
New Features
- Economy Integration: Added economy system support for charging and refunding fees when creating warps and teleporting.
- New Commands: Added commands for clearing warp points and teleportation history.
- GUI Icon Customization: Integrated minecraft-heads.com support. You can now use the command
/wp seticon {warp} {Value}to replace the default sign icons in the GUI with custom player heads. - Player Head Caching: Implemented a caching mechanism for player heads to optimize GUI item rendering and performance.
- Custom Icon Generation: Added new predefined head values to support more default icon generations.
- Randomized Properties: Added support for randomizing private properties of newly generated warps.
Improvements & Refactoring
- GUI Optimization: Significantly optimized GUI item processing logic and improved the display logic for pagination navigation buttons.
- Localization Standardization: Standardized localization keys for warp and history commands to ensure better multi-language support.
- Code & Log Cleanup: Optimized error logging and removed redundant code comments to simplify system maintenance.
- Architecture Refactoring: Conducted deep code refactoring and standardized class documentation formats to align with system design requirements.
Bug Fixes
- Thread Blocking: Fixed critical bugs in CommandHandler that caused the main thread to block during command execution.
- Thread Safety: Resolved multiple potential thread-safety issues and internal logic bugs.
Dependency Updates
- Changed the mirror source for SignWarpXLoader.
- Updated jackson-databind and jackson-module-blackbird to 3.1.2.
- Updated org.xerial:sqlite-jdbc.
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:eUdkHg5G:wMih9CK7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eUdkHg5G:wMih9CK7"
}

