Tags
Creators
Details
Licensed Apache-2.0
Published 6 months ago
Updated 5 months ago
All versions
1.0.2
Release
xJobs v1.0.25 months ago 198
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.3 - Multi-Job Support & Translation Fixes (Current)
🚀 Engine & Core Stability
- Multi-Job Support: Fully implemented support for multiple active jobs per player, driven by
max-jobs-per-playerinconfig.yml(e.g.,jobs.max-jobs-per-player: 2). Players can now join and progress in multiple professions simultaneously! - Database Schema Auto-Upgrade: Seamless, robust migration logic automatically updates the SQLite/MySQL/H2 storage tables to utilize a composite primary key (
uuid,job_name). - Simultaneous Job Progression: Experience points (XP) and leveling logic now iterate over all active player jobs, rewarding actions across multiple jobs in parallel.
🎨 Premium Aesthetic & GUI Redesign
- Redesigned GUI Dashboard: Polished, cleaner dark-themed GUI layout with dynamic placeholders.
- New Menu Placeholders: Fully integrated
{active_jobs}and{max_jobs}placeholders inside the GUI templates to display player stats like(1/2)active jobs. - Customizable Action Messages: Resolved the untranslatable
{join_action}issue. Admins can now customize and translate these action indicators throughgui-join-actionandgui-leave-actioninmessages.yml!
🛠️ Commands & Usability
- Leave Multi-Job Prompt: Updated the
/jobs leavecommand to guide players when multiple jobs are active. Players are notified with the customizablejob-leave-multiplemessage to resign via the interactive menu or specify the job. - Expanded Placeholders: Extended PlaceholderAPI integration to dynamically support listing active jobs and levels.
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:1NaECwFn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t2LuwSY3:1NaECwFn"
}

