FAQ

No. Everyone works all six at once. There is no join command and no slot limit, so a player levels whichever job matches what they are doing.

Four usual reasons: the material is not in that job’s block list, the crop was not mature and require-mature is on, the player placed that block themselves and anti-placement-dupe is on, or drops are disabled. Turn on debug in config.yml and the console names which one.

Use money.per-block and xp.per-block in that job’s block. A material listed there uses its own value, everything else falls back to the base. See jobs.yml.

The whole plant is counted on one break, but each of those blocks is paid at the flat base unless you price them. Add the chorus materials to per-block.

Yes. Copy an existing block in jobs.yml, give it a new id and a free menu-slot, and add its name to all three language files.

Only for money. Without Vault, or with economy.use-vault: false, jobs still award xp, farmpoints, and drops. The console says money is off at startup.

Any that registers with Vault, so EssentialsX, CMI, and the rest. CoreJobs never talks to an economy plugin directly.

The balance is what a player spends. Ranking points are what the monthly board sorts on, and they only go up when farmpoints are earned. Spending in the shop does not lower them. See Farmpoints.

No. The reset zeroes ranking points only. Balances carry across untouched.

No. give counts as earned, so it raises ranking points too. Use /corejobs farmpoints set to correct a balance without touching the ranking.

One per category, so an xp boost, a money boost and a farmpoints boost can all run at once. Two of the same category never both run: the weaker one waits with its time frozen and starts when the stronger one ends. See Boosts.

Money is its own category, so an xp boost only touches xp. Set boosts.xp-also-money: true to bring back the old behaviour where it did both.

A clean shutdown does not. Each boost stores the time it has left, not an end time, and picks up where it stopped. A crash costs up to 30 seconds. Set boosts.pause-while-offline: false if you would rather downtime counted against a boost.

Yes. CoreJobs fires an event for every xp, money and farmpoints payout, and a handler can raise or cancel the number before it is banked. See the Developer API.

Shortly after midnight on the first of the month, using the timezone key in config.yml. Set a time zone id like Europe/Paris if the server clock is not your clock.

No. Rewards are staged and the player claims them at /farmpoints ranking, so nothing is lost to a full inventory or an offline player.

/corejobs resetranking confirm forces the whole cycle now. It is a real reset, so do it before your first live month rather than during one.

Yes. Every item takes custom-model-data for a resource pack model, or an itemsadder namespaced id which wins over the material.

Every button, icon, and filler has its own slot in menus.yml. Job icons carry their slot in jobs.yml as menu-slot.

No. auto-reload watches the folder and rebuilds open menus on save. /corejobs reload does the same on demand.

data.db in the plugin folder with SQLite, or your database with MySQL. See Storage.

Yes, point them at the same MySQL database with the same table prefix. Avoid one player being logged into two of them at once.

No. Changing the type points the plugin at an empty store. Decide before players start earning.