Pack data export
Items, tags, every recipe, advancements, loot tables and the names of things, out of a running server into one zip - only when asked, and nothing leaves the machine. New in 0.2.8.
This page is older than Keystone 0.4.3, released 15 November 2026. Something may have changed since.
On this page 3 parts
The export module, export.toml. It writes what a modpack actually contains, as the running game sees it after every mod and datapack has loaded: items, tags, every recipe, advancements, loot tables and the names of things, in one zip. Tools for pack authors read it (STYGION Workbench builds its recipe and quest views from it).
Only when asked
#The module is on, but a server where nobody asks does nothing here at all: no file, no thread, no work on the tick. Two ways to ask:
- At start:
-Dkeystone.export=<file.zip>(or the environment variableKEYSTONE_EXPORT) writes the dump once the server is up. With-Dkeystone.export.stop=truethe server stops afterwards — handy for a test server that exists only to read a pack. - On a running server, with a key holding
pack.read(an owner scope):POST /v1/exportstarts a dump into the module's folder and answers with its id; one at a time.GET /v1/export?id=…says how it is going: running, done with its size and counts, or failed with why.GET /v1/export/zip?id=…hands over the finished zip.
The references are taken on the server thread (a few milliseconds); the reading and the writing — seconds in a big pack — happen on a worker. The last 4 dumps are kept.
Nothing leaves the machine
#The dump is a file on the server's disk. The API gives it only to whoever holds the key, on the loopback port like the rest of the local API.
Settings
#max-mib (512) — the largest dump written, in MiB. A dump that would be larger is abandoned and its half-written file deleted; a big modpack with tens of thousands of recipes is far below.
Did this page help?
Opens the feedback panel with this page attached. It lands in the same queue as everything else.