PlanyDocs
Playpute

Schematics

A game server captured with its build installed and its world generated, so a fleet's servers start in seconds.

projects/{project}/locations/{location}/schematics/{schematic}

A schematic is a game server's disk, captured: the build downloaded, the install script run, the world generated. An autoscaling group's members start from one and skip all of that. For a modded server that is the difference between minutes and tens of seconds.

Where they come from

A group makes its own. A group with a warmup_duration starts one server, lets it install and generate its world for that long, captures it, and removes it. Every member then starts from that capture. The warm-up server is not charged for — it exists so your members do not each repeat the same install. See Warm-up.

You can capture one from a running server, for example a world you have set up by hand, and give it to a group of the same game when you create it.

Servers → the server → Capture as schematic

The server keeps running while it is captured. Capturing a server with a world takes minutes, and returns a long-running operation. An ephemeral server cannot be captured — you asked for its data not to be kept.

StateMeaning
PENDINGThe capture is running.
READYCaptured, and a group can start from it.
FAILEDerror says why.
DELETINGBeing removed.

plany playpute schematics list, get and delete read and remove them; the console lists them at Schematics.

Giving one to a group

Set schematic when you create a group, through the API, to start its members from a capture you already have rather than warming up a new one. That is the faster path for a second group of the same game.

grpcurl
grpcurl -H "authorization: Bearer $PLANY_API_KEY" \
-d '{"parent": "projects//locations/",
"game_server_group_id": "modpack",
"game_server_group": {
"game": "games/minecraft-java-forge-1-20-4",
"schematic": "projects//locations//schematics/modpack-warm",
"policy": {"min_size": 0, "max_size": 10, "scale_on_waiting_connections": true}}}' \
api.plany.cloud:443 plany.playpute.v1.PlayputeService/CreateGameServerGroup

A schematic records the game and the build that were installed when it was taken, and a group can only be given a READY schematic of its own game — starting a Minecraft fleet from a captured Garry's Mod server is refused.

source_game_server names the server it was captured from, and is kept after that server is deleted.

Every server started from a schematic gets its own copy of it.

Deleting one does not disturb servers started from it

They are already independent.

Two servers from one schematic diverge immediately

They share nothing after they start.

A schematic is not a backup. It is a starting point, taken once and reused.

It is stored, so it is billed

A schematic is charged for storage from the moment the capture completes until you delete it, on its size_bytes, whether or not anything starts from it.

microvm-schematic-storage-gib-hour — $0.000032 per GiB-hour, with the first 20 GiB-hours each month free. A capture in progress, a failed one, and one being deleted are not charged.

Schematics count against microvm.plany.cloud/schematic_storage_bytes — 100 GiB on Hobby, 2 TiB on Pro, per project per region. A schematic is a whole installed game server, so expect tens of gigabytes each. See Quotas.