First Run

A short pass to confirm the plugin works, then the order to configure it in.

Confirm it works

  1. Open the menu
    Run /jobs. Six job icons in a grid, your own head in the middle.

  2. Open a job
    Click the miner icon. The hub shows a leaderboard, an earnings list, your progress, prestige, and a rewards button.

  3. Earn something
    Break stone. You should see an action bar with the xp gained and progress to the next level.

  4. Check the money
    With Vault installed, your balance goes up. Without it, xp still moves and the console warned you at startup.

  5. Check farmpoints
    Break stone until a farmpoint drop fires, then run /farmpoints. The balance should match.

  6. Open the shop
    /farmpoints shop shows the six bundled entries: two items, a command-only entry, and one boost per category. Buying takes the points and hands the entry over.

All six passed

The install is good. Everything from here is tuning values, not fixing anything.

Set it up in this order

Working in this order avoids going back and redoing things.

  1. Pick a language
    language: en in config.yml. French and Spanish ship with the plugin. See Messages & Styles.

  2. Pick your storage
    SQLite needs nothing. MySQL needs credentials before players start earning, so switching later does not carry data across. See Storage.

  3. Set the time zone
    timezone decides when the monthly ranking rolls over. Set a time zone id like Europe/Paris if your host clock is not your clock.

  4. Price the jobs
    Money base, per-level, and the xp curve in jobs.yml. This is the part players feel. See jobs.yml.

  5. Tune the drops
    Chances and farmpoint amounts in drops.yml. Start low, they fire on every matching block. See drops.yml.

  6. Fill the shop
    Prices and items in shop.yml, so farmpoints have somewhere to go. See shop.yml.

  7. Wire up the ranking
    Webhook URL and the per-place rewards in config.yml. See Monthly Ranking.

  8. Style the menus last
    Slots, icons, and lore in menus.yml, once the numbers behind them are settled. See menus.yml.

Editing configs while the server runs

auto-reload: true in config.yml watches the plugin folder and reloads the moment you save a yml. Anyone with a CoreJobs menu open gets it rebuilt and reopened on the same page.

Live layout editing

Leave a menu open on a second client, save menus.yml, and watch the slot move. Turn auto-reload off if you edit configs by hand on a busy live server and would rather control the reload with /corejobs reload.

Turn on debug when a payout looks wrong

debug: true in config.yml prints a console line per block break: the material, the multi-block count, and what each job paid.

Noisy on a live server

One line per block per player. Turn it on to answer a question, then turn it back off.