Getting Started

Installing EcoHub and linking it to your account takes about a minute. This page walks through it, then explains what the plugin does once it is running.

Requirements

RequirementNotes
Java 25Or newer. The jar will not load on Java 21
Spigot or Paper 1.21.8Or newer
An EcoHub accountFree, at hub.auxilor.io

Quick start

  1. Put EcoHub-<version>.jar in your plugins/ folder.

  2. Start the server. The console prints a link and a short set of instructions.

  3. Go to hub.auxilor.io/link, log in, and copy the code shown.

  4. Run /ecohub link <code> in the console or in game.

  5. Run /ecohub status to confirm.

That is the whole setup. Once linked, the plugin gets on with it.

Step 1: start the server

EcoHub loads at STARTUP, before the rest of your plugins, so it can see every jar in the folder. On an unlinked server it prints a banner:

The console banner shown on an unlinked server

The same one-line reminder is sent to operators when they join, once per session, until the server is linked.

Log in at hub.auxilor.io/link. The page shows a short code for you to copy.

The link page on hub.auxilor.io showing a link code

Run the command in the console or in game:

/ecohub link ABCD2345

The API key EcoHub sends back is written to plugins/EcoHub/link.yml.

Step 4: confirm

/ecohub status
The output of /ecohub status on a linked server

You will see the account the server is linked to, the server ID, a redacted key, and when the plugin last checked for updates and last reported in.

What happens next

Once linked, EcoHub runs on its own:

WhenWhat happens
At startupChecks for updates, and installs them if auto-install-updates is on
Every check-interval-minutesChecks again (default 180 minutes, minimum 30)
Every 6 hoursReports server status, if send-server-stats is on
At any time/ecohub check and /ecohub update run a check immediately

Updates are staged into plugins/update/ and applied by Bukkit at the next restart. The console tells you how many are waiting.

Which plugins EcoHub manages

Every Eco plugin ships with a file called platform inside its jar, added when the jar was published. EcoHub reads that file out of every loaded plugin to work out which ones came from the Eco suite.

If a jar has no platform file, EcoHub leaves it alone completely. It is listed in the console output as unmanaged and is never downloaded, replaced, or removed.

An update check listing up-to-date and unmanaged plugins

It does not matter where you originally got an Eco plugin. A jar from Polymart or Modrinth updates the same as one from EcoHub, as long as your account owns that resource.

Where to go next

  • How updates are applied: How Updates Work.

  • Every command: Commands and Permissions.

  • Turn things off: Plugin Config.