CoreJobs | Jobs, Prestige & Farmpoints v1.5.0
Six configurable jobs with prestige, level rewards, boosts, drop tables, and a points shop.
v1.5.0
LatestCompatibility
Changes
A scoreboard line that names every boost a player has, and raw ids on the action bar so other plugins' placeholders can be built from what was just broken.
📊 Where the Boost Comes From%corejobs_external_xp_source% means other plugins only, so with just a CoreJobs boost running it reads as none. That is correct, but it is not what most people want on a scoreboard.
There is a new one that names everything:
%corejobs_total_xp_source%
A CoreJobs boost on its own reads CoreJobs. Add a gear bonus from another plugin and it reads CoreJobs, zCustomGear. Works for money and farmpoints too, and takes a job in the middle like the others: %corejobs_total_xp_miner_source%.
Rename what CoreJobs calls itself in your language file, so it matches whatever your players see in the shop:
placeholder:
self-source: "&bServer Boost"
The line then reads Server Boost, zCustomGear. Nothing you already wrote changed, %corejobs_external_xp_source% still means exactly what it did.
🧱 Raw Ids on the Action Bar{block} still reads as a proper name, oak log. Two new placeholders give you the raw ids instead: {block_id} is oak_log, and {job_id} is lumberjack.
xp-actionbar: "{job} &7+{gained} xp &f{block} &8| &f{block_id} &8| &f{job_id}"
Both are filled in before PlaceholderAPI runs, which is the point of them. You can build another plugin's placeholder out of whatever was just broken:
xp-actionbar: "{job} &f{block} &8| &b%someplugin_count_{block_id}%"
Use {block_id} for that, never {block}. A proper name has a space in it, and a placeholder with a space in it does not resolve.
That only builds the string. Whether it answers is up to the other plugin. A counter that groups materials, where cobblestone counts toward something called stone, will not answer to cobblestone unless that plugin resolves the material for you.
🎣 Fishing and Enchanting Name What They Got
Those two used to say fish on every catch and enchant on every enchant, whatever it actually was. Now a cod reads cod, a treasure catch reads what it is, and enchanting a diamond sword reads diamond sword.
This is the one thing that changes under you. If a line of yours relied on it always reading the word "fish", that line will now read the catch instead.
📦 Install
Stop the server, replace the old jar in plugins/, and start it again. Your language file picks up the two new keys on its own, with nothing to regenerate.
Read the documentation | Join the Discord
Enjoying the plugin? A ⭐ review goes a long way!
Dependencies
Statistics
Views
Purchases
Downloads
File size
Published
Updated
Info
Share & Earn
Share and earn part of the profits, an estimated €0.8 per product sale.