Adding plugins
Drop plugins into your server to extend Endstone.
Endstone loads plugins on startup from the plugins/ folder inside your server directory. There's no install command - put the file in the folder, restart the server, and the plugin is live.
Where to find plugins
- endgit.dev - the community plugin index. Search, filter, and download release artifacts.
- GitHub - plugin authors often publish releases directly on their repos. Look on the project's Releases page for the prebuilt artifact.
GitHub's code search surfaces every public plugin by signature:
- Python plugins declare an
endstoneentry point inpyproject.toml- searchproject.entry-points."endstone". - Native plugins register with the
ENDSTONE_PLUGINmacro - searchENDSTONE_PLUGIN.
If you build from source, the project's README will say how to produce the artifact (pip wheel, cmake --install, or similar).
Plugin formats
Endstone supports two plugin runtimes. Both go into the same plugins/ folder and load side-by-side.
| Type | Extension | Built with |
|---|---|---|
| Python | .whl | A Python wheel produced by the plugin's pyproject.toml. |
| Native C++ | .dll (Windows) / .so (Linux) | A shared library built against the Endstone C++ headers. Platform-specific - download the artifact that matches your OS. |
Install
- Stop the server if it's running.
- Copy the plugin file into
<server>/plugins/. - Start the server. The plugin loads during boot - watch the console for the plugin's load message.
To remove a plugin, stop the server, delete its file from plugins/, then start again.
Per-plugin data
Plugins that persist state usually create their own folder under plugins/ on first run (for example, plugins/<plugin-name>/). Configuration files, databases, and caches live there - back them up alongside your world saves.