Inspect a client process
Inspects one existing daemon-managed client process. Prefer this when a client id is already known; it does not launch a new client.
Inspects one existing daemon-managed client process. Prefer this when a client id is already known; it does not launch a new client.
Response Body
application/json
application/json
curl -X GET "https://example.com/clients/{id}"{ "id": "string", "instance": { "id": "string", "version": { "id": "string" }, "loader": "string", "files": { "root": "string", "gameRoot": "string", "runtimeRoot": "string", "cache": "string", "mods": "string", "config": "string", "saves": "string", "resourcePacks": "string", "shaderPacks": "string", "screenshots": "string", "logs": "string", "artifacts": "string" } }, "profile": { "kind": "string", "name": "string" }, "presentation": { "window": "NONE", "audio": "MUTED" }, "state": "string"}{ "code": "string", "message": "string"}Launch a new client process POST
This operation launches a new daemon-managed real Minecraft Java client process. This is not a selector, retry, or reuse operation. Before calling it in an existing daemon or workspace, call GET /clients and GET /clients/{id} to reuse a suitable client. If replacing a failed attempt, stop the old client with POST /clients/{id}:stop first. Creating fresh timestamped ids for retries leaves multiple Minecraft clients running.
Download client artifact GET
Downloads a daemon-owned artifact for one client, such as media produced by a generated action. Artifact ids are resolved under the client's Craftless runtime artifact directory and cannot traverse outside it.