batch
Run up to 32 server tools in one round trip to reduce latency. Use step references and settle delays when actions need to observe previous results.
Instructions
Runs up to 32 server tools in ONE bridge round trip instead of one per call. A round trip costs about 0.4s, so any act-then-look sequence is dominated by transport unless it is batched. Each step reports its own ok/data/error; a step failing is data, not a transport error. IMPORTANT: with settleMs 0 every step runs in the SAME server tick, and some engine effects only land at the end of a frame -- a removed entity still reads as valid. Set settleMs (100 is usually enough) whenever a step must observe what an earlier one did. Any arg value may be {"__step": 1, "get": "index"} to read a field from an earlier step's result, so spawn-then-act still costs one round trip.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| steps | Yes | ||
| confirm | No | Required if any step is a guarded tool. Applies to every step. | |
| settleMs | No | Pause between steps, in ms. Needed when a step must observe the previous one. | |
| stopOnError | No | Stop at the first failing step and mark the rest skipped. |