Tags
Creators
Details
1.1.3
Compatibility
Required content
Changes
๐ VRX JobSystem MMO 1.1.3
Version 1.1.3 expands the political and company systems while improving configuration structure, stability and server compatibility.
๐ Mayor & City Hall
- Completely redesigned City Hall dashboard
- Added Public Projects funded through the City Treasury
- Added Player Referendums
- Added Mayor Approval Rating
- Added Election History
- Added Political Statistics
- Added election start, reminder and winner notifications
- Admins can manually end elections
- The candidate with the most votes wins the election
๐ข Companies
- Redesigned Company Settings GUI
- Clearer management sections
- Improved role and permission visibility
- Improved payroll, profit sharing and tax management
โ Configuration
- Reorganized the configuration structure
- Removed duplicated and obsolete configuration options
- Moved features into their proper module configs
- Removed unused legacy configuration files
- Improved migration support for existing installations
- Cleaner and more professional default configs
๐ก Stability & Performance
- Improved anti-exploit protection
- Improved Folia and concurrency handling
- Safer Treasury and Referendum operations
- Fixed multiple race conditions
- Improved persistence and restart handling
- General performance and code cleanup
โ ๏ธ Upgrade Notice
Before updating, make a backup of your plugins/JobSystem/ folder.
Some legacy configuration files are no longer used in 1.1.3 and should be removed after backing them up:
configs/settings.ymlconfigs/quests.ymlconfigs/gui.ymlconfigs/boosters.ymlgui/achievements.ymlgui/missions.ymlgui/stats.yml
Their settings have been moved into the new modular configuration structure.
Optional dependencies
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:tQtkphmA:Wwp06Tgn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tQtkphmA:Wwp06Tgn"
}

