Migration
Importing jobs and levels from Jobs Reborn, EcoJobs, ExcellentJobs and AdvancedJobs, and what each source gives.
/jobsadmin import <source> or the hub's Migration card. Sources: jobsreborn, ecojobs, excellentjobs, advancedjobs.
| Option | What it does |
|---|---|
| none | Opens a preview screen (the console prints it). |
-dry | Only prints the preview. |
-confirm | Imports. |
The preview reads off the main thread and writes nothing: players and standings found, jobs new and merged, old jobs with no match, and every entry of the old files with no place here. Importing asks for a confirmation in game.
What each source imports
| Source | Folder read | Imports |
|---|---|---|
| Jobs Reborn | plugins/Jobs | Job files (jobs/*.yml, or the old jobConfig.yml) and levels, from SQLite (jobs.sqlite.db) or MySQL (generalConfig.yml, table prefix honoured). |
| EcoJobs | plugins/eco | Levels, joined jobs and experience from eco's data.yml, SQLite or MySQL/MariaDB (and the legacy eco_data table). |
| ExcellentJobs | plugins/ExcellentJobs | Levels, from SQLite or MySQL (job_data and the older JSON data column). |
| AdvancedJobs | plugins/AdvancedJobs | Levels only, unverified: the plugin is closed source, so tables and YAML player files are read by guessing column and key names. MySQL is not read. |
EcoJobs data kept in MongoDB, PostgreSQL or Redis is not read: the console says so. Switch eco's data-handler to sqlite or mysql (eco moves the data) and import again.
How job files convert (Jobs Reborn)
Actions map to break, strip-log, place, kill (also mmkill, as mythicmobs:<id>), fish, craft, villager-trade, smelt, brew, enchant, repair, breed, tame, shear, milk, explore, eat and collect. The level equation becomes a formula curve when readable (else the default curve). Names are made plain and old item names updated. Not carried, and listed in the preview and in the new file's header: points, negative pay, from-level/until-level, sub-types (pay applies to any), items matched by display name, enchantment targets, exploring past the first player, and actions such as tntbreak, dye or custom fishing plugins.
Matching and writing
- A new job file is written as it is. A job that already has a file here is merged: only targets yours lacks are added and the old file is copied to
imports/backup/first. - Standings match jobs by id, a name synonym (fisherman, lumberjack, excavator, blacksmith, alchemist, breeder, fighter...) or the display name; the rest are listed as unmatched.
- Levels never add up: a standing is written only when higher (level, then experience) than what the player has here, so running it twice changes nothing. Online players are updated in memory. Imported jobs held there are joined here.
- It is logged in the audit log as
jobs-import. If the old plugin is still enabled you are reminded to remove it.
Something missing on this page? Tell us on Discord