Skip to content
Previewer

Server owners

Configure work budgets, understand persistence and support players with rules.

These steps apply to every update, including 0.2.x or 0.3.x to 0.4.0. Players in singleplayer follow the same steps.

  1. Keep the old mod version installed while every owner finishes or cancels unfinished paid jobs. A paused job is still unfinished.
  2. Make eligible return space available and settle all owed unused-input returns on that old version. Resolve any recovery condition before treating the work as closed.
  3. Stop the server or singleplayer instance cleanly and back up the complete world, including its schematic job data and server configuration.
  4. Install the new JAR matching the Minecraft version and loader on both server and clients, then reopen the world.
  5. Check Minecraft Controls: an old 0.1.0 K menu binding can remain after updating; the default has been V since 0.2.0.

Saved paid work records the runtime environment, including the mod version. Unfinished work crossing a version change can enter Recovery with an environment-changed message. An update does not discard its records, complete the job or settle an owed return.

Downgrade by restoring the pre-upgrade world backup and its matching old mod files. Removing 0.2.0 or later and opening the same upgraded world with 0.1.0 is unsupported: printer blocks and saved printer templates exist independently of active jobs and cannot be loaded by 0.1.0.

Version 0.7.1 joins 0.7.0 and 0.6.0 on the same Minecraft version and loader, in both directions, but 0.6.0 and later connect to no earlier build, so update the client and the server together when you can. Fabric also needs Fabric API, and the 1.21.8 and 1.21.10 builds need Fabric Loader 0.19.5 or newer. 0.7.1 changes no saved format. A world or Survival save written by 0.6.0 cannot be read by 0.5.0, so keep the backup from step 3 in case you want to go back. Saves written by 0.5.0 load in 0.6.0, 0.7.0 and 0.7.1. The Fabric 1.21.1 and 1.20.1 builds of 0.7.0 refused every vanilla entity (armor stands, minecarts, mobs, item frames), so update those servers to 0.7.1 if schematics with entities matter to you.

Moving a world from 1.21.1 or 1.20.1 to Minecraft 26.1.2, 26.2, 26.3, 1.21.8 or 1.21.10, or from 1.21.8 to 1.21.10, is like any mod update. Finish or cancel unfinished Survival builds on the old version first, because on those versions they go to Recovery with an environment-changed message and held materials are not refunded. Printers keep their settings and ask for a new Bind. Paste history from the older version cannot be undone there: the server moves those history files, unchanged, to data/simpleschematics/creative-archive/ in the world. On 1.21.8 and 1.21.10 the Survival index stays in data/simpleschematics_jobs.dat, where 1.21.1 keeps it. Saved work can require Recovery when the mod version changes, so do not treat updating as a way to clear a stopped job or an unpaid return. Printer owners should also review Stop, returns and restart behavior.

Install the same mod version on server and clients. A client and a server on the same Minecraft version and loader join each other with 0.6.0, 0.7.0 and 0.7.1 in either mix. A server and client on different Minecraft versions, or on NeoForge and Fabric, refuse each other. The one exception is Fabric 1.21.7 and 1.21.8, which use the same protocol, so the Fabric 1.21.8 build can serve 1.21.7 players. 0.7.1 adds no server settings, so a Fabric .properties file from 0.6.0 needs no new lines.

The world’s serverconfig/ folder contains:

Loader Configuration
NeoForge / Forge simpleschematics-server.toml
Fabric simpleschematics-server.properties
NeoForge 26.3 config/simpleschematics-server.toml, overridden for one world by syncedconfig/simpleschematics-server.toml in the world folder

NeoForge 26.3 has no serverconfig/ folder. The first time a world with a serverconfig/simpleschematics-server.toml starts on 26.3, the file is copied once to the world’s syncedconfig/ folder so the world keeps its values. The old file stays where it is, and an existing syncedconfig/ file is never replaced. NeoForge 26.1.2 and 26.2 and all Fabric versions use the table above. Defaults allow 4 ms / 8,192 Creative steps per tick, 2 ms of shared Survival work per tick and up to 200 paid groups per game second. Undo budgets default to 64 MiB per player and 512 MiB per world, measured as decoded data. Actual work is also limited by journal and storage operations.

If the server does not have Simple Schematics, what happens depends on the client:

  • Fabric 1.21.1, Forge 1.20.1, NeoForge 1.21.1 and every 26.x client with the mod are refused.
  • Fabric 1.20.1 clients can still join. Loading and previewing schematics still works. Creative paste, Survival builds, Materials, Rules and the Printer show a message that Simple Schematics is not on this server. The preview hint line says the same.

Known quirks: Forge 1.20.1 shows Forge’s own “mismatched mod channel list” screen when versions differ or the server lacks the mod. NeoForge’s version-mismatch text shows the client and server versions the wrong way round; that is NeoForge’s wording. A 0.5.0 Fabric client joining an old 0.4.1 server may be told the mod is missing on the client; that is the old server’s text, so update the server.

When something is too big to send to the server, such as a large Rules save or a big paste, nothing is sent and nobody is disconnected. The screen says why, with the size and the limit.

Loading and previewing a schematic never sends it anywhere. The file stays on the player’s computer, and the preview is drawn only on their screen.

The server gets a copy only when the player asks it to act on that schematic:

  • Materials, including the shopping list and Inspect build, which need the server to check the world;
  • Build in Survival;
  • Paste in Creative;
  • Bind schematic on a printer.

Other actions, such as changing construction settings, loading a placement slot or saving a world rule, send the schematic again only if you are already using a Materials check.

The copy is kept in the server’s memory for that check, build or paste. It is never saved as a schematic file. What the world keeps is only what each job needs: Survival builds and printers keep their plan so they can resume after a restart, and Creative pastes keep undo history.

Every copy must fit the limits below. A broken file is refused. So is a file that is too large, or one that asks for operator-only blocks such as command blocks from a player without operator permission.

Set schematicSending in the server configuration. On NeoForge and Forge, write schematicSending = "operators" in the .toml file; the quotes are needed. On Fabric, write schematicSending=operators in the .properties file.

Value Who may send schematics
everyone (default) Every player who may build
operators Only players with operator permission level 2
nobody No one; players can still load and preview schematics
  • Blocked players: they see Materials, Inspect build, Build, Paste and Bind schematic greyed out, with a tooltip saying why. The server refuses them even if a modified client sends anyway.
  • Work already started: builds already running, and printers already bound, keep working. The setting only stops new schematics from being sent.
  • Misspelt value: it counts as operators, and the server log names the bad value. The log also records the setting in effect each time the server starts.
  • NeoForge and Forge: a change takes effect when the file is saved. On Forge 1.20.1 with some editors on Windows, a live edit may not be picked up (Forge 47’s file watcher drops some modify events), so restart the server to be sure.
  • Fabric: a change takes effect when the server restarts. A Fabric server that ran 0.4.0 or earlier already has a properties file without this line, so add it yourself, for example schematicSending=operators. Until it is added, everyone may send.
  • Singleplayer: the world’s owner counts as an operator only when cheats are on.

Added in 0.6.0. They share the file and the reload rules of schematicSending above. The generated NeoForge and Forge .toml gets the new lines with their defaults. A Fabric server that already has a properties file must add them itself (printerAutoResume=false, captureAccess=operators, survivalMinSecondsPerGroup=0); until then it uses those defaults, and the server log names each missing line at startup. Each setting has its own part below: capture access, printer auto-resume and slow builds.

Set captureAccess. On NeoForge and Forge, write captureAccess = "everyone" (with the quotes) in the .toml file. On Fabric, write captureAccess=everyone in the .properties file.

Value Who may capture
operators (default) Players in Creative mode with operator permission level 2
everyone Any living player who is not a spectator, in any game mode
  • Size, output and concurrency limits are the same for both values. Each player can have one capture running at a time.
  • Both corners and the origin must be within 128 blocks of the player on every axis, so nobody can read blocks or find loaded chunks far from where they stand. Within that range, everyone can still copy hidden blocks such as ores under the player.
  • Capture reads only chunks that are already loaded and never changes the world. It copies block states only: no chest contents, sign text or entities.
  • With everyone, the server does not check other mods’ claims. Any player can copy any loaded build, apart from areas under spawn protection, which still stop capture. Turn this on only if you accept that.
  • Players who may not capture see the Capture button greyed out, with the reason in its tooltip. The server refuses them anyway.
  • A misspelt value counts as operators, and the server log names it.

Set printerAutoResume to true (printerAutoResume = true on NeoForge and Forge, printerAutoResume=true on Fabric). The default is false, which keeps the old behaviour: after a chunk reload or a restart, the printer’s owner must press Resume.

With it on, a printer resumes by itself when its controller chunk ticks again, but only if:

  • it was running when it unloaded or the server stopped, and
  • the only thing that paused its job was the controller leaving its ticking range, or a controlled shutdown.

A manual Pause, a Stop, owed items, Recovery, a rules change or any failure still waits for the owner. So does a printer job saved before 0.6.0. A running printer between two prints just carries on. Redstone is not needed again. Required chunks are never force-loaded, so the printer still waits until they are loaded and ticking.

survivalMinSecondsPerGroup is the least time, in seconds, between paid groups for each Survival build and printer. It ranges from 0 to 3,600. The default, 0, keeps today’s speed. For example, survivalMinSecondsPerGroup = 30 makes every build place at most one group every 30 seconds.

  • Players can choose a slower rate in Build options, never a faster one. A new build or printer cycle starts with no head start, so its first group waits the full time.
  • With a value of 1 or more, players see a disabled rate slider that says “This server places one group every N s”.
  • The server still runs at most 8 unfinished builds at once, so slow builds can fill the slots. When they are full, the message says builds on this server run slowly on purpose.
  • A value outside 0 to 3,600 is not accepted, and the default is used instead.

Added in 0.6.0. A modpack can hide some library files until a player earns them, for example to match quest progress. Locks only hide files in the Library, its search and the layout piece picker. A folder always stays visible, and a file no pack locks is always shown, so files players add themselves just work. The files live on each player’s own computer, and the server never refuses a schematic because it is locked. Locks are for progression, not security.

Put JSON files in data/<namespace>/simpleschematics/locked_blueprints/:

{ "locked": ["factory/smelter", "tier2/*"] }

A blueprint’s id is its path inside the player’s schematics/ folder: lower case, / between folders and no file extension (Factory/Smelter.schem is factory/smelter). * matches within one folder level; ** matches across folders. Foo.schem and foo.nbt have the same id and share a lock. Locks load with the world and on /reload. A bad entry is skipped and logged.

These commands need operator permission level 2.

Command What it does
/simpleschematics unlock <players> <id> Shows the matching locked blueprints to those players.
/simpleschematics lock <players> <id> Takes back an unlock, so the pack’s lock applies again.
/simpleschematics unlock team <team> <id> The same for a vanilla scoreboard team. lock team takes it back.
/simpleschematics unlock ftbteam <name> <id> The same for an FTB Teams team. Only available when FTB Teams is installed. lock ftbteam takes it back.
/simpleschematics unlocks <player> Lists the patterns data packs lock (the first 20, then how many more) and what is unlocked for that player.
  • The <id> can be a pattern such as tier2/*.
  • lock removes only an unlock granted with exactly that id or pattern, and says so when nothing matched.
  • A player sees their own unlocks plus those of every team they are in. The server checks teams about once a second, so a player who joins a team sees the new blueprints within about a second.
  • Unlocks are saved in the world in data/simpleschematics/unlocks.json. If that file cannot be read, nothing is unlocked and the commands say why until you fix or remove the file.
  • If a data pack locks nothing, nothing is hidden.

Players can view rules; operator permission level 2 is required for world-rule edits. Datapack rules reload with /reload. The Rules guide covers field discovery, costs, precedence and invalid files.

Check claim compatibility on your server. Native events and Simple Schematics’ extension events support permission decisions; private claim APIs may require integration.

There is no fixed 4,096-block or one-million-block cap. Whether a schematic fits depends on its format, palette, saved data, occupied sections and available memory. The budgets below apply independently of block count.

Budget Limit
Compressed input 64 MiB
Decoded NBT 512 MiB
Section arrays 256 MiB
Estimated placement working storage 256 MiB
Cached preview GPU geometry 128 MiB
One saved block / complete entity group 256 KiB
Root entities 4,096
Passenger group 256 members; 16 nesting edges

The root-entity limit is not a block limit. Sparse regions do not allocate every empty cell in their bounding volume. Fit depends on source format, palette, saved data and memory.

World mutations run on the server thread. Parsing and history I/O use workers. Versioned journals are written before mutations. Interrupted or ambiguous operations keep evidence for the recovery inspector and require fresh validation before resolution.

A clean reload that offers the printer owner Resume is different from an ambiguous operation after a crash or interrupted write. If the screen reports Recovery, inspect the recorded state first and follow the available recovery actions. Do not assume a second start or a refund is safe solely because the server is back online.

Unknown schemas can be archived explicitly while preserving their original bytes. Old jobs with verified ownership can remain closable in Recovery after leaving the recent-history index. Closing preserves evidence and does not refund items.