Installation

What you need before you start, and how to get CoreJobs running.

Requirements

Requirement Notes
Spigot or Paper 1.18, 1.19, 1.20, 1.21, and the 26.x releases
Java 17 or newer Whatever your server already runs on, as long as it is 17 or above
Vault plus an economy plugin Optional, only needed for money payouts
The first start takes a moment longer

CoreJobs loads a few libraries on first start instead of shipping them inside the jar, so the first boot is slower than the ones after it. They are cached with your server files, so it only happens once.

Install

  1. Download the jar
    Grab it from PixelEast, the recommended store. It is also on SpigotMC and BuiltByBit.

  2. Stop the server
    Dropping the jar into a server that is already running does not work, it has to be a fresh start.

  3. Copy the jar into plugins/
    Remove any older CoreJobs jar in the same folder so you do not run two copies.

  4. Start the server
    Console prints the enable line, creates plugins/CoreJobs/, and writes the default config files.

  5. Check the console
    No red errors, and a warning about Vault only if you have no economy plugin.

  6. Run /jobs
    The head grid should open with six job icons.

Optional integrations

Vault

Needed for money. Install Vault plus an economy plugin such as EssentialsX or CMI, then leave economy.use-vault: true in config.yml.

PlaceholderAPI

Exposes job levels, farmpoints, and the leaderboards to scoreboards and holograms.

Placeholders
ItemsAdder

Any menu item, drop, or reward can use a namespaced ItemsAdder id instead of a vanilla material.

All three are soft depends

CoreJobs enables with none of them installed. Add one later and it is picked up on the next restart, no config migration needed.

Updating

  1. Stop the server
    Same as a fresh install.

  2. Swap the jar
    Delete the old jar, drop in the new one from the store you bought it on (PixelEast, SpigotMC, or BuiltByBit). Leave the plugins/CoreJobs folder alone.

  3. Start and read the console
    Config files are migrated in place by their *-version key. New keys are added with their defaults and your values are kept.

Do not hand-edit the version keys

Every yml starts with a key like config-version or jobs-version. That is how the updater knows which migration to run. Changing it by hand can either skip a migration or run one twice.

Next

Walk the First Run checklist, then look at the Plugin Folder to see what each file is for.

Previous Overview Next First Run