Sentinel Settings

Remote configuration via the GnBots /settings API

Checking…

—

All setting changes require a GnBots restart to take effect. Editing is disabled while the bot is running, paused, or booting — stop the bot from the dashboard first, change settings here, then use Restart GnBots. Access is currently open — plan to restrict via nginx or a user system later.

Loading settings…

All settings

Edit each account’s Action Editor settings from the profile file (profiles/<profile>.json). Includes advanced settings, templates, and editable per-action schedule rules. Stop the bot before saving, then restart GnBots.

Account —

Choose a template

Apply a saved action preset to the selected account (same as GnBots template picker).

Template Description

Advanced settings

Assigned session and account menu rules (shuffle / custom).

Select an account to view advanced settings.

Actions

Per-action settings, schedules, and last-used times.

Select an account to view actions.

Edit every account’s Switch account name (Account Switch action) in one place. Each row keeps up to 10 recent names for quick selection. Stop the bot before saving, then restart GnBots.

Switch account names

—

Loading account names…

Change one setting or schedule timer on a GnBots action across many accounts at once — for example, set Beasts to level 27, replace schedule rules, or reset timers on selected accounts. Stop the bot before saving, then restart GnBots.

Bulk action settings

—

Action Setting / timer

Set selected to

Choose an action and setting to edit.

Create a new LDPlayer instance with recommended health settings, install the latest Whiteout Survival APK, and add a matching account to the active GnBots profile. The instance and account name are the same. Stop the bot before starting — restart GnBots when the job completes.

Loading provisioning options…

Account / LDPlayer name

Clone settings from

Copies action list, schedule rules, and advanced settings from a profile account or saved action template.

Provisioning progress

Recent jobs

No provisioning jobs yet.

Restore troubled LDPlayer instances from your configured backup folder, then install the latest Whiteout Survival APK from the GnBots cache. Restore is disabled while the bot is running — stop the bot from the dashboard first.

Backup folder

Absolute path to the folder with *.ldbk emulator backups. Saved in monitor/config.json.

Backups folder

—

Loading emulator restore options…

Instances to update Loading…

Choose emulator instances to update. Updating an instance updates Whiteout for every account on it.

Loading instances…

Edits monitor/config.json directly. Most dashboard and push values apply immediately; watcher settings need a watcher restart, dashboard port needs a monitor restart, and tray settings need the tray restarted.

Updates

Checking version…

Loading monitor settings…