Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 3 months ago
All versions
1.4
Release
New Features and Bug Fixes3 months ago 457
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.8β1.8.9
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
π X-SetWarps v1.4 - Changelog
β¨ New Features
- Debug system: New
/xsw debugcommand to toggle debug mode at runtime, plus aDebugLoggerthat logs detailed internal operations for easier troubleshooting. - 1.8.8 support: Now compatible with Minecraft 1.8.8 servers.
- PlaceholderAPI expansion: Added
%xsetwarps_total%,%xsetwarps_last_warp%,%xsetwarps_cooldown_<warp>%,%xsetwarps_has_<warp>%,%xsetwarps_warp_world_<warp>%, and%xsetwarps_warp_desc_<warp>%placeholders. - Config auto-update with backup: When the config version changes, the old config is backed up as
config_old.ymlbefore generating the new one. - Update checker: Checks the SpigotMC API for new versions on startup.
- Adventure MiniMessage color support: Internal color system upgraded to use Adventure's MiniMessage for better formatting.
- Shared dependency directory: Libby now downloads runtime libraries to
plugins/X-API/so all X plugins share dependencies instead of each having their own copy. - Updated startup messages with standardized logging format.
- Tab-completion command hiding: Own namespaced commands (
xsetwarps:*,x-setwarps:*) are now hidden from player tab-completion. - Standardized plugin lifecycle (onEnable/onDisable) with proper error handling and graceful degradation.
π Bug Fixes
- Debug system now sends messages to the player who toggled it via command, and to console only when enabled via config. Command responses now use the prefix from
config.yml. - Debug messages now include the plugin name in the format:
[DEBUG] [X-SetWarps] [Category] message.
Optional dependencies
Any compatible version
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:fzglRV5u:g60C6c6o"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fzglRV5u:g60C6c6o"
}

