Tags
Creators
Details
1.1.0
Compatibility
Changes
New Features:
- Teleportation Costs: Introduced teleportation costs that can be configured in the
config.yml. Players are charged a set amount of in-game currency to use warp signs. - Soft Vault Dependency: Vault is now a soft dependency. The plugin will still function without Vault, but economy features will be disabled if Vault is not present.
- Vault Dependency Error Handling: If
teleport-costis enabled and Vault is not installed, players attempting to use a warp sign will receive an error message.
Bug Fixes:
- Resolved an issue where teleportation costs or item costs were deducted even if the teleportation was cancelled.
- Fixed errors related to the absence of Vault when
teleport-costis configured.
Enhancements:
- Improved the handling of player interactions with warp signs, ensuring smoother operation and better error feedback.
- Added messages to
config.ymlfor teleportation cost notifications and Vault dependency errors. - Optimized teleportation logic to ensure costs are only deducted after successful teleportation.
We hope these new features and improvements enhance your SignWarp experience. As always, thank you for using SignWarp! If you encounter any issues or have feedback, please reach out on our discord server.
Update Instructions:
- Stop your server.
- Replace the old SignWarp.jar with the new version.
- Restart your server to apply the changes.
- Ensure Vault is installed if you plan to use teleportation costs.
Note: The plugin will automatically handle new configurations. Your existing warp data will remain intact.
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:1QUtO3R9:QHQo3sqm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1QUtO3R9:QHQo3sqm"
}

