Startup and updates
What updates itself
| What | How it updates |
|---|---|
| Eggactyl launcher | On every start the server checks the latest release. If it's newer and passes a syntax check, the server swaps it in. If GitHub is unreachable it just starts with the copy it has. Admins can turn this off per server with Eggactyl Self-Update. |
| Paper / Purpur / Velocity | Newest stable build of the same game version on start (Auto Update = 1). |
| Bedrock | Latest release on start (Auto Update = 1); clients require it. |
| Bots from Git | git pull --ff-only on start (Auto Update = 1). |
| The egg itself (variables, startup) | Only when you re-import the egg JSON. Needed only when a release adds or changes egg variables; the release notes will say. |
Servers only ever move to a newer launcher, and the downloaded script must pass a syntax check before it's used. Releases are published only after the full test suite passes.
Layout on the server
eggactyl.conf chosen type/version/build (delete to re-run setup)
.eggactyl/eggactyl.sh launcher (self-updates; rewritten by Reinstall)
.eggactyl/runtimes/ Java / Node.js / Python, downloaded on demand
.eggactyl/venv/ Python virtualenv
Last updated 28 Oct 2026
Report an issue on GitHub