jobs.yml
The six jobs, what they pay, how fast they level, and their prestige settings.
Shape of the file
defaults:
max-level: 100
xp-curve:
base: 100
factor: 1.12
prestige:
...
jobs:
miner:
...
lumberjack:
...
defaults applies to every job. A job block only has to list what it changes.
The defaults block
| Key | Default | What it does |
|---|---|---|
max-level |
100 | Highest level a job can reach |
xp-curve.base |
100 | XP cost of level 1 to 2 |
xp-curve.factor |
1.12 | How much steeper each level gets |
xp-curve.formula |
"" |
Your own curve instead of base and factor, empty uses them |
xp-curve.levels |
{} |
Exact xp for single levels, wins over everything else |
Cost to go from a level to the next is round(base * factor ^ (level - 1)) unless you set a formula. A job can carry its own xp-curve block with only the keys it changes. See Levels and prestige for the formula syntax.
Prestige defaults
| Key | Default | What it does |
|---|---|---|
enabled |
true |
Prestige available at all |
max |
10 | How many times a job can prestige, 0 turns it off |
announce |
broadcast |
broadcast, player, or none |
reset-reward-claims |
true |
Level rewards become claimable again after a prestige |
requirements.max-level |
true |
Must be at the cap first |
requirements.money |
50000 | Vault money, 0 skips the check |
requirements.xp-levels |
25 | Vanilla xp levels, 0 skips the check |
requirements.farmpoints |
0 | Farmpoints, 0 skips the check |
requirement-growth |
1.5 | Every requirement multiplied once per prestige already earned |
consume.money |
true |
Meeting the requirement also spends it |
consume.xp-levels |
true |
Same for xp levels |
consume.farmpoints |
true |
Same for farmpoints |
scaling.xp-cost |
1.35 | XP needed per level, per prestige |
scaling.money |
1.25 | Money paid per action, per prestige |
scaling.farmpoints |
1.0 | Farmpoints dropped while working this job |
scaling.drop-chance |
1.0 | Chance of a drop firing at all |
commands |
[] |
Console commands on prestige, with {player} {job} {prestige} {level} |
Full explanation on Levels & Prestige.
A job block
miner:
display-name: "&bMiner"
description:
- "&7Break stone and ores to earn."
- "&7Level: &f{level}&7/&f{maxlevel}"
- "&7Next level: &f{xp}&7/&f{xpnext} xp"
- "&7Pay: &a{money}&7 each"
how-to-earn: []
menu-titles:
hub: ""
rewards: ""
menu-items:
hub: {}
rewards: {}
menu-slot: 19
icon:
material: IRON_PICKAXE
head-texture: ""
custom-model-data: 0
itemsadder: ""
trigger: BLOCK_BREAK
blocks:
- STONE
- COAL_ORE
money:
base: 0.10
per: 10
per-level: 0.05
xp:
per-action: 1.0
| Key | What it does |
|---|---|
display-name |
English fallback. The jobs.<id>.name entry in each language file wins |
description |
Lore under the job icon |
how-to-earn |
The “How to earn xp” lines for this job. Empty lists its blocks or mobs instead |
menu-titles.hub |
Job hub title. Empty uses job-hub-menu.title from menus.yml |
menu-titles.rewards |
Rewards title. Empty uses job-tier-menu.title from menus.yml |
menu-items.hub |
Partial look overrides for items and frame parts in job-hub-menu |
menu-items.rewards |
Partial look overrides for items and frame parts in job-tier-menu |
menu-slot |
Where the icon sits in the /jobs grid, 0-indexed |
icon |
Material, head texture, model data, or an ItemsAdder id |
trigger |
What the job listens for |
money.base |
Payout before level bonuses |
money.per |
Charge the base once per this many actions |
money.per-level |
Added to the base for each job level |
xp.per-action |
XP granted each time the action fires |
Lore placeholders
{level} {maxlevel} {xp} {xpnext} {progress} {money} {prestige} {maxprestige} {job_id} work in every job’s description. {job_id} is the job block key, such as miner.
Per-job menu titles and item overrides
menu-titles lets one job use a resource-pack title while other jobs keep the shared title. {job}, {job_id}, lang: routes, and PlaceholderAPI work there.
menu-items.hub mirrors job-hub-menu and menu-items.rewards mirrors job-tier-menu. Write only the field you want to replace. For example, menu-items.rewards.frame.border.material: AIR keeps every other frame setting from menus.yml.
Writing the how-to-earn lines
The how-to-earn button in the job hub lists the job’s blocks or mobs on its own. Fill in how-to-earn on the job to write those middle lines yourself:
farmer:
how-to-earn:
- "&7Harvest any crop when it is ripe."
- "&7Pay: &a{money}&7 per crop"
{job}, {money} and {xp} work in a line, and so does a lang: route. {money} is what the job pays the viewer for one action right now, {xp} its xp per action.
A job’s own list wins over how-to-earn.lines in menus.yml, which is the same thing written once for every job. Leave both empty for the generated list.
Triggers
| Trigger | Fires on | Extra keys |
|---|---|---|
BLOCK_BREAK |
Breaking a listed block | blocks, require-mature, harvest-blocks, per-block maps |
ENTITY_KILL |
Killing a listed mob | entities, money.per-heart, xp.scale-by-hearts, per-entity maps |
FISH |
Reeling something in | per-catch maps |
ENCHANT |
Enchanting at a table | per-item maps |
blocks: [ALL] counts every block. entities: [ANY] counts every mob.
Per-block pricing
money:
base: 0.05
per: 1
per-level: 0.0
per-block:
CHORUS_FLOWER: 0.10
CHORUS_PLANT: 0.05
xp:
per-action: 1.0
per-block:
CHORUS_FLOWER: 1.0
CHORUS_PLANT: 0.5
A material listed under per-block uses that value instead of the base. Anything not listed falls back. money.per-level is still added on top, and prestige still scales it.
Per-source pricing for the other jobs
The same idea works for every trigger, under its own key:
| Key | Job | Keys inside |
|---|---|---|
per-block |
BLOCK_BREAK |
Materials, or ItemsAdder block ids in quotes |
per-entity |
ENTITY_KILL |
Mob types. A listed mob pays that flat amount per kill, never times its hearts |
per-catch |
FISH |
Materials like COD, ItemsAdder ids, or the groups fish, treasure, junk |
per-item |
ENCHANT |
The material of the item being enchanted |
money:
base: 5.0
per-catch:
COD: 4.0
PUFFERFISH: 10.0
treasure: 25.0
junk: 0.5
"myfish:golden_carp": 50.0
xp:
per-action: 1.0
per-catch:
COD: 2
treasure: 10
junk: 0
On a catch the most specific entry wins: ItemsAdder id, then material, then group.
ItemsAdder blocks
List the id under blocks and price it under per-block, both in quotes:
blocks:
- STONE
- "myores:ruby_ore"
money:
per-block:
"myores:ruby_ore": 12.0
Custom blocks are matched on their id alone. A ruby ore drawn as a note block pays as the ore, never as a note block, and a listed NOTE_BLOCK never pays for it. drops.yml does not roll on custom blocks.
One break can count a sixteen block chorus tree. Without per-block, every one of those blocks pays the flat base.
Mature crops and harvests
| Key | What it does |
|---|---|
require-mature: true |
Only pay when the crop is fully grown, so replanting or trampling does not |
harvest-blocks |
Materials picked by right-clicking when ripe, like sweet berries |
Harvest blocks pay xp, and money only if the material has a money.per-block entry.
Sugar cane, cactus, bamboo, kelp, and chorus never report as mature. They are handled by multi-block in config.yml instead.
Per-heart jobs
hunter:
trigger: ENTITY_KILL
entities:
- ANY
money:
base: 0.10
per: 1
per-level: 0.10
per-heart: true
xp:
per-action: 1.0
scale-by-hearts: true
per-heart multiplies the payout by the mob’s hearts, which is max health divided by two. scale-by-hearts does the same for xp.
Adding your own job
Copy an existing block
Pick the one with the trigger you want and paste it under a new id.Give it a free menu slot
menu-slotmust not collide with another job in the/jobsgrid.Add its name to every language file
jobs.<id>.nameandjobs.<id>.descriptioninen.yml,fr.yml, andes.yml.Save
Withauto-reloadon it appears straight away, otherwise run/corejobs reload.
Deleting a job block leaves that progress orphaned in the database. Set prestige.max: 0 and empty its block list if you want to retire a job instead.