rewards.yml
One-off rewards for reaching a level in a job.
Top level
| Key | Default | What it does |
|---|---|---|
rewards-version |
2 | Version tracker, leave it alone |
enabled |
true |
Off means no level rewards, and the rewards page shows plain level panes |
claim-all-detail |
true |
Claim All lists every reward it handed over |
claim-all-detail-limit |
10 | How many lines before the rest fold into “and 4 more”. 0 prints every line |
A reward
jobs:
miner:
10:
icon:
material: DIAMOND
name: "lang:content.rewards.miner.level-10.icon-name"
lore:
- "lang:content.rewards.miner.level-10.icon-lore"
custom-model-data: 0
itemsadder: ""
items:
shiny-diamonds:
material: DIAMOND
amount: 5
name: "lang:content.rewards.miner.level-10.item-name"
lore:
- "lang:content.rewards.miner.level-10.item-lore"
commands:
- "say {player} claimed the Miner level 10 reward"
| Key | What it does |
|---|---|
icon |
The item shown for that level on the rewards page. Without it, a default pane shows |
items |
Item blocks added to the inventory on claim |
commands |
Console commands on claim, {player} replaced |
Under each job id, the key is the level number. Only list the levels that give something.
Item fields
material, amount, name, lore, custom-model-data, itemsadder, and head-texture. The itemsadder id wins over material when set.
shiny-diamonds in the example is a label for you. It does not appear anywhere in game.
Commands only
25:
icon:
material: EMERALD
name: "lang:content.rewards.miner.level-25.icon-name"
items: {}
commands:
- "give {player} emerald 16"
An empty items: {} with a command list is a fine reward. Use it for ranks, money grants, or anything a plugin hands out.
Translated reward text
Any name or lore line written as lang:some.route is read from the player’s language file, so a reward reads in the player’s language and the Claim All summary names it the same way. The bundled rewards point at the content.rewards block in the three language files.
Write the text directly when you want one wording for every language at once.
Prestige and claims
prestige.reset-reward-claims in jobs.yml decides whether a job’s rewards unlock again after a prestige. On by default.
With reset on, a player who prestiges ten times claims the whole table ten times. Keep the rewards modest or turn the reset off for that job.
Adding a level reward
Pick the job and level
Add a numbered block under that job id.Give it an icon
Optional, but a plain pane on the rewards page reads as unfinished.Add items, commands, or both
Both run on the same claim.Save
auto-reloadpicks it up, otherwise/corejobs reload.Test it
/corejobs job setlevel <you> miner 10, then open the rewards page.
