Game Bot Creator · Loaded config → +

Getting Started

Everything from creating a config to watching the bot run your first scenario. Almost all of it works identically on Windows and Android — the toggle below switches the few parts that don't.

I'm running the game on
1

Create a config

A config holds one game's whole setup — its scenes, actions, and scenarios. Click the + button next to the Loaded config dropdown at the top of the window (or Create Your First Config… on the Start tab if you have none yet).

  1. Type a name for the config (the game's name works well) and confirm.
  2. Optionally type the name of the game it's for (shown later in the Configs tab).

Game Bot Creator then asks how the bot should reach this game — that's Part 2 — and which tools it needs: leave the extra ones unticked for a game you only click through menus in; tick Walk a character around using the minimap or Find things that move or look different each time for action games. This only decides what's shown — change it any time with Tools… next to the config selector. Nothing is saved until you finish these questions, so cancelling leaves no half-made config behind.

2

Connect it to your game

Pick Windows (a linked desktop window) or Android (emulator or device) — this can't be changed later without recapturing everything, so pick whichever matches how you actually play.

Windows

  1. Make sure the game is already open somewhere on screen.
  2. Pick it from the list of open windows, or click Later to link one afterward from the Scene Editor's Link Window… button, once the game is actually running.
For best results, run the game windowed or borderless-windowed rather than exclusive fullscreen — exclusive fullscreen can block the window from being captured at all. Use as large a window size as you comfortably can; bigger, more detailed captures hold up better if you ever move this config to a different PC/resolution.

Android

Pick where the game runs: LDPlayer, another detected emulator (MuMu, MEmu, BlueStacks), or Other ADB device for a phone or tablet. With LDPlayer, your game must already be installed inside it:

  1. Download and install LDPlayer (a button for this is right in the dialog if it isn't found automatically).
  2. Launch LDPlayer and install your game inside it — via its own app store, or an APK.
  3. In that LDPlayer instance: Settings → Other settings → ADB debugging, set to Enable local connection (one-time, per instance).
  4. Back in Game Bot Creator, click Continue — it picks up your LDPlayer install automatically.

Then:

  1. Pick which instance this config uses (skipped automatically if you only have one).
  2. Pick the game's package from the list of installed apps — or click Later to finish both of these afterward from the Configs tab's Link Devices… button.
3

Build your first scenes

After creating the config you land in the Scene Editor. A scene is one distinct screen or area of your game; here you teach Game Bot Creator to recognize each one, and what it can do there. This example builds two scenes — a Home scene and one it can navigate to and back from.

Android note: every capture below pulls a screenshot from your linked device instead of your physical screen — otherwise this whole part works exactly the same as Windows.

The pinned 🌐 Global entry at the top of the scene list isn't a real scene: actions added there work in every scene (handy for things like combat or picking up loot). You can ignore it for now.

The Home scene

  1. Click + Add, name it Home.
  2. The Scene Marker row is selected; click Capture: drag a box around a small, unique part of this scene that's always visible (a logo or title works well), then drag a slightly larger box around where it should be searched for (or press Esc to skip and search a little around it).
  3. Click Set as Home — the scene the bot treats as its home base and falls back to for recovery.

A second scene

  1. Click + Add again, give it a name (e.g. Farm).
  2. Capture its marker the same way — something only visible on this scene.
  3. New scenes already get a Back action that presses Esc. If your game leaves this scene some other way (a close button, a fixed point), delete it and add your own via + Add Action → Back.
  4. Click + Add Action, choose Click Image, and drag a box around a button that does something here (e.g. collects a resource) — name it. Press Esc when done; a short message confirms it's saved.

Wire the navigation

  1. Select Home in the list.
  2. Click + Add Action, choose Navigate, drag a box around whatever button on Home opens the second scene, name it, and pick that scene as the destination.

A scene shown in red with ✗ isn't usable yet — select it and the panel on the right says what's missing. Once both are ✓, the bot can path from Home to your second scene, act, and find its way back — automatically.

4

Build a scenario

A scenario is a list of steps — go to a scene, then run some of its actions — that the bot repeats. Open the Scenario Editor.

  1. Click + Add — a new scenario is created and selected.
  2. Name it, and set a Cooldown seconds — how long to wait after it finishes before it can run again.
  3. Under Flow, click + Add Step: set Navigate to: your second scene, and check the action you added there.

There's no Save button — every change autosaves within about half a second. Run Limit and Prerequisites below the flow are optional; open them when you need them. Each step's navigation computes the shortest path from wherever the bot currently is, so this scenario can run from anywhere reachable, not just from Home.

5

Run it

The Start page runs scenario sets: a set picks which of a config's scenarios to run, and where. While your config isn't fully set up, a checklist at the top of the Start page shows what's left, with a button for each step.

  1. Open Start and click + Add Scenario Set.
  2. Name the set. All of the config's scenarios start ticked — untick any you don't want this set to run.
  3. Pick the device it runs on. If you clicked Later back in Part 2, link one first via the Configs tab's Link Devices….
  4. Click Start on the set's row (or Start All).

The bot detects the current scene, paths to your second scene, runs the action, comes back, and waits out the cooldown before doing it again. Watch it happen live in the Logs pane on the Start page. A scenario that can't run is shown in red with the reason, and a set that can't start says why when you hover it.

Selecting a set lists its scenarios on the right. Each has a Run checkbox to switch it on or off for that set, even while it runs. Scenarios you create later aren't added to existing sets automatically — add them with the set's wrench button.

One at a time on Windows: only one Windows set can run at once, since they'd fight over the same mouse and keyboard.
Android scales further: link a config to several devices and give each its own scenario set — they run in parallel, one set per device.

Where to go from here