Creating a client
Every field on the new-client form, and which ones you can change later.
A client is one game connection. Create it from the Clients page with New client, and it runs on our servers until you stop it.
You need an account first. If you have none, the form lets you add an offline-mode one on the spot, or sends you to the Accounts section for a premium one.
The basics
The form walks you through Account, Dedicated IP (on a plan) and Name and server.
| Field | What it is |
|---|---|
| Name | Your label for the client. Only you see it. |
| Account | Which account it connects with. One account drives one client at a time. |
| Server host | The address, e.g. play.example.com. |
| Port | Usually 25565. Leave it unless the server says otherwise. |
| Game version | Pin one, or leave it on auto to use whatever the server negotiates. See supported versions. |
| Flows | Tick every flow this client should run. Their triggers are merged into one document. Your plan sets how many flows one client can run. |
| Dedicated IP | Optional, and part of a plan. Without one the client connects through the platform's shared IPs. Each one shows its latency. See dedicated IPs. |
A Tag (display name) can be added later, in the client's settings: an optional short tag shown on the client row, for grouping at a glance.
Before you launch, the form says whether your plan has a free slot for this client. With Start it right away ticked, it starts as soon as it is created; if every slot is in use, the client is still created but will not start until one frees up or you add another. Running a client costs a slot, not coins. See how coins work.
On the free tier a new client runs on your phone. On a plan, the CubeMind app adds a Run on this phone box. See phone clients.
Advanced options
Everything here has a sensible default; open Advanced options only if you need it.
Auto-restart on crash. If the client drops, bring it back automatically. Turn it off to leave it stopped after a crash.
Auto-reconnect on disconnect. If the client is kicked or disconnected, it rejoins with backoff and re-runs its on-join flow. This is the setting that keeps a client online through a server restart.
Verbose debug logging. Adds a detailed trace to the console, for chasing a problem. See troubleshooting.
Run on a daily schedule. Pick a start time, a stop time and the active days. A stop earlier than the start wraps past midnight, so 22:00 → 06:00 means overnight. Times use your timezone, which you set in preferences.
What you can change while it runs
Flows can be changed while the client is running. Tick or untick them and it picks the change up straight away.
Everything else needs a stop. Host, port, version, account, dedicated IP and the advanced settings are locked while the client is up: Stop the client before editing it.
Many clients at once
On the Clients page, Select lets you pick several clients and act on them together: Start, Stop, Delete, Share these, and on the web set their Flows, Dedicated IP or Logins in one go. A start never goes past your plan: if fewer slots are free than clients picked, you are asked before only the ones that fit are started. Flows can be added, replaced or removed on running clients too; a dedicated IP or login cannot, so running clients are skipped and counted in the result.
To make clients from accounts you already have, select them in the Accounts section and use Make clients. See adding many accounts.
Deleting a client
Deleting a client keeps its parts. The account, the flows and the dedicated IP return to the Clients page as spares, ready for another client. Only the client itself and its logs go.