Tags
Creators
Details
Licensed Apache-2.0
Published 6 months ago
Updated 5 months ago
All versions
1.0.1
Release
xJobs 1.0.16 months ago 95
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
xJobs v1.0.1 - Release Notes
🚀 Engine & Core Stability
- Cross-Version Support (1.8 - 1.21.x): Fully compatible with legacy and modern servers. Integrated fallback systems for Hex colors and NMS components.
- Unified Database Driver: Fixed critical "No suitable driver" errors by removing library relocation conflicts.
- SQLite Support: Added support for SQLite as a stable alternative for local storage, alongside H2 and MySQL.
- Smart Reflection: Implemented a reflection-based player profile system for job icons, ensuring custom heads work on both Spigot and Paper without crashes.
✨ Premium Aesthetic & UI
- Refined GUI Dashboard: New premium dark theme with optimized spacing and improved lore readability.
- Dynamic Lore Placeholders: Integrated global placeholders (
{info_label},{workers_label}, etc.) across all job files for centralized editing inmessages.yml. - Icon Visibility Fix: Resolved issues where job icons wouldn't load correctly under certain configuration scenarios.
🛠 Management & Flexibility
- 100% Translatable: Every single message, menu item, and job description is now fully editable.
- Filenames as IDs: Removed confusing legacy ID migration. The plugin now detects jobs exactly by their
.ymlfilename, giving full control to administrators. - Anti-Italic Fix: Added automatic italic removal (
&r) to all default GUI labels for a modern, clean look.
💎 Premium Spanish Config (Included)
- Fully translated Professional Configuration with immersive descriptions for all 14 base jobs.
- Optimized for the new v1.0.1 engine.
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:t2LuwSY3:BJjTyjTL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t2LuwSY3:BJjTyjTL"
}

