BOTLOBBIESCan I send several bot commands at once?
For predictable results, let the current command finish before sending another instruction to the same bot. The web client coordinates pending saves and direct commands, and it can ask you to wait rather than accepting overlapping actions.
Finish pending edits first
A direct command can depend on the bot's currently saved configuration. The client therefore tries to finish pending saves before sending the instruction and checks that the selected bot has not changed in the meantime. If you see a message asking you to save changes, resolve that state first. Rapidly clicking a different command does not make the original save complete sooner. It can instead leave you unsure which draft or selected record the next instruction was intended to use.
Do not treat repeated clicks as retries
The interface can hold a per-bot command in progress and reject another click with a wait message. That is a coordination behavior, not automatically a lost connection. Read the current result or error before deciding whether a retry is appropriate. A command may have reached the service even if the browser briefly loses its response, so repeat only after checking the visible state. Sending a burst of outfit, emote, and readiness instructions makes the final game observation harder to connect with any single request.
Use a deliberate sequence for a setup
For an appearance session, choose the outfit, confirm the save or application status, then adjust another slot and inspect the lobby. For party setup, confirm membership and leadership before readiness. Keep each instruction tied to a visible checkpoint. If one stays pending or returns an error, note its name, time, and message instead of continuing the sequence blindly. This approach preserves a useful troubleshooting history and avoids interrupting a working bot merely because several actions were competing for attention in the same browser tab.