Staying online

Two built-in behaviours keep a client up without any flow at all. They are checkboxes on the client, under Advanced options. Everything else is a flow.

Auto-reconnect on disconnect

If the client is kicked or loses its connection, it rejoins by itself, with backoff between attempts, and re-runs its on-join flow.

This is the one that carries a client through a server restart. Leave it on unless you specifically want a disconnect to be final.

The retries are not endless. If the server stays unreachable, the client gives up after a set number of tries and shows error. With auto-restart on, it is then started again.

Because the on-join flow runs again on every reconnect, anything in it has to be safe to repeat. A /login is; a "claim your daily reward" is not.

Auto-restart on crash

If the client process itself drops, or a client meant to be running is not online and no longer retrying, bring it back. Turn it off to leave the client stopped after a crash, which is what you want while debugging something that crashes repeatedly.

Servers that kick idle players

Some servers do not allow idle players and disconnect them after a while. That is the server's rule to make. Run clients on servers that allow them to stay connected, and use a daily schedule when a client is only needed for part of the day.

Auto-login

There is no checkbox for this one, because what a server wants varies. It is a flow, and the editor has ready-made blocks for it:

The wait matters: plugins often ignore a command sent in the same instant as the join. The full version, including registering on first join, is in recipes.

A daily schedule instead of always-on

If a client only needs to be up at certain hours, a daily schedule is cheaper than keeping it online and stopping it by hand. Times are in your timezone, and a stop earlier than the start wraps past midnight.