FollowBot setup

1. Install the Visual C++ 2015 x64 redistributable

   FollowApp is built against the Microsoft Visual C++ 2015 x64 runtime. Without it the application will not start: depending on your Windows version you get a missing-DLL dialog naming a .dll you have never heard of, or nothing happens at all when you double-click the exe.

   Install the x64 redistributable, not x86. If you are unsure whether you already have it, installing it again is harmless.

   !

   If FollowApp does nothing at all when you run it, this is the cause

   Check it before anything else on this page. A silent exit with no window and no error is this, by a wide margin, more often than it is anything else.

2. Extract and rename

   Extract the downloaded archive to its own folder. Do not run the executable from inside the zip — Windows extracts it to a temporary directory and several things break, including profile saving.

   Rename the executable. Give it any name you like. Keep it in its own folder, and keep that folder somewhere your antivirus is not going to reach into — a directory you have excluded.

   Do not extract into Program Files or Program Files (x86). Windows applies virtualised writes there and your profiles will appear to save and then silently vanish. A folder directly on a drive root, or under your user folder, is fine.

3. Log in

   Run the executable. You get a Login dialog with Username:, Password: and a Remember Password checkbox.

   FollowApp — Login

   Username

   XXXXX-XXXXX-XXXXX-XXXXX← your licence key

   Password

   ← leave it empty

   ☑ Remember PasswordSign in

   Use your subscriber credentials. Your licence key goes in Username and Password stays empty; an older forum username and password still works here too, and always will. Remember Password stores what you typed locally so you are not typing it every launch.

   !

   If login starts failing after it has been working, stop retrying

   A saved password that has gone stale is retried on every launch, and a burst of failures from one connection trips a temporary back-off. It is a wait, not a lock: your licence is untouched, nobody has to lift it, it clears on its own, and the refusal says so and tells you how long. One sign-in that works clears it outright. Clear the saved password, type it fresh once, and if it still refuses, ask. Retrying only makes the wait longer.

4. Pick a profile

   The main FollowApp window is a profile list.

   FollowApp — profile list A list of saved profiles with New, Copy, Edit, Delete, Load and Run down one side, and an Info: box underneath showing the selected profile’s summary.

   • New Profile — creates a profile and asks for a name.
   • Copy Profile — duplicates the selected profile. Use this for your second, third and fourth character; you almost never want to build each one from scratch.
   • Edit Profile — opens that profile’s inputs, triggers and settings.
   • Delete Profile — removes it.
   • Load — attaches the selected profile to a game client that is already running.
   • Run — starts the game client for the selected profile and loads the profile into it. It needs the client path set in Edit Profile → Tools → Keep Alive, and it is the way in when the profile’s HWID tab is enabled. See Keep Alive.

   The Info: box below the list shows the selected profile’s summary. Read it before loading — it is the fastest way to notice you are about to load the aurabot profile into your mapper.

   A profile holds everything for one character: its keybinds, its triggers, its follow distance and position, and its behaviour options. One profile per character you intend to run.

5. Match the keybinds to the game

   !

   This is where most “the bot does nothing” reports come from

   FollowApp does not read your Path of Exile keybinds. It sends the keys you configure. If the profile says movement is on Q and in game it is on W, the bot presses Q, nothing happens, and the character stands still while everything looks correctly configured.

   Go through Edit Profile → Settings and set at least:

   Setting	What it must match
   Movement Key:	The key your movement skill is actually bound to in game
   Inventory Key:	Your inventory keybind (I by default in Path of Exile)
   Close all interfaces key:	The key that closes open panels (Escape by default)
   Skill inputs on each trigger tab	The exact keys those skills sit on in game

   Then check the same for every input you have configured on the Manual tab — attack inputs, flask inputs, buff inputs, timed inputs. The Auto-Input tab is the exception: it reads the skill bar’s own keybinds, so a new profile fights with no inputs written. See Auto-Input.

   Do this per profile. Copying a profile copies the keybinds with it, which is correct when your characters share a layout and wrong when they do not.

   If you are unsure what a key is called, the Key Helper dialog tells you the name FollowApp uses for a key you press.

6. Load into the right game window

   With one Path of Exile client running, Load attaches to it directly.

   With more than one running, FollowApp opens the Process Selector:

   Multiple PoE processes found running, drag and drop the target over the window you want to load this profile into.

   FollowApp — Process Selector A small window with a draggable target icon and, underneath it, a box that fills in with the name of the window the target was dropped on.

   Drag the icon from the Process Selector onto the game window you want this profile to control. The box underneath fills in with the window it resolved, so you can confirm you got the right one before committing. Then press Load.

   This is per profile and per client. To run four characters, you run FollowApp four times, each time selecting a different profile and dropping the target onto a different game window.

   Get into the habit of checking the resolved window name before pressing Load. Dropping the wrong profile into the wrong client is the single easiest mistake to make here, and the symptom — a character doing something almost but not quite right — looks like a configuration bug.

7. Hotkeys

   Once loaded, three keyboard hotkeys control the bot. These are the defaults and they are configurable in Hotkeys.

   Key	Action
   INSERT	Activate — start the bot
   DELETE	Pause — stop it doing anything, stay loaded
   END	Unload — detach from the game client completely

   • Use DELETE when you want to take manual control for a moment. The bot stops acting immediately and resumes on INSERT.
   • Use END when you are done, before closing the game client.
   • Start Enabled in Settings makes the bot active as soon as it loads, without waiting for INSERT. It is on for new profiles. Turn it off while you are still configuring, because it starts acting before you have looked at the screen.
   • Enable bot when leader moves is the gentler version of the same idea, also on by default: the bot waits, loaded and inactive, until the character it follows starts moving.

   FollowApp — Hotkeys Three rows — Activate, Pause, Unload — each with a key capture field, and a Defaults button that puts all three back.

8. Set up the loot filter

   •

   Your loot filter is the looting configuration

   FollowBot works off the item labels the game draws on the ground. It has no item database of its own and it does not decide what is valuable — the filter decides, and the bot picks up what the filter leaves visible. A default or permissive filter has the bot collecting scrolls for the rest of the league.

   Three settings, all in the game’s own options, not in FollowApp:

   • Hide Filtered Ground Items — ON. Without this the game still draws labels for items your filter hides, and the bot will see and take them. This is the setting that makes the loot filter actually control the bot.
   • Key Pickup — bound to F. Item pickup happens by key rather than by click.
   • Item name display — OFF. The always-on label display is turned off so that the labels present on screen are the ones the bot should act on.

   Then set up the filter itself to show exactly what you want collected and nothing else. Test it by walking a character through a zone manually and looking at what is still labelled. Whatever you can see is what the bot will take.

   Also in Settings

   • Auto loot and Loot distance: — whether to loot at all, and how far the bot will divert to reach an item. Under it, on by default: Verify target before clicking (avoids shrine/altar misclicks), Only click the uncovered part of loot labels and Optimized label scanning.
   • Price Lookup for Looting Unidentified Unique Items, with a Minimum Price: in chaos and an Exceptions: list — so unidentified uniques are judged on value rather than picked up indiscriminately.
   • Auto Stash Loot, Stash Into Guild Stash and Stash tab index list: — leave the tab list blank for all tabs. Click delay: (ms) sets the stashing pace; lower is faster, and 30 is the recommended value.

Troubleshooting

FollowApp will not start at all, or exits immediately

The Visual C++ 2015 x64 redistributable is missing — step 1. This is the most common cause by a wide margin.

Login fails and it worked yesterday

Check whether your subscription has expired before assuming a password problem: an expired subscription and a wrong password look the same from the client. Do not retry repeatedly — repeated failures from one connection trip a temporary back-off, which is a wait rather than a lock, clears on its own, and says how long.

The bot loads but does nothing when I press INSERT

Three candidates, in order of likelihood: the keybinds in the profile do not match the keybinds in game (step 5); the bot is paused (press INSERT, not DELETE); or you loaded the profile into a different client than the one you are watching (step 6).

It follows, but does not attack

The attack input’s key does not match the game, or the attack distance in Settings is shorter than the range at which you expect it to engage. Check Distance from host to start attacking and the Attack: input’s key.

It follows, but does not loot

Auto loot is off, Loot distance: is too small, or your filter is hiding the items — step 8. Hidden means not looted, which is usually what you want and occasionally is not.

It stops following in a new zone

Check Name of character to follow: in Settings. If it is set and the name does not match exactly — including case and any special characters — the bot has nobody to follow. Leaving it blank follows the party leader.

It will not take portals or zone transitions

Take entrances and the portal key configuration. If the portal key in the profile is not the key your portal is on, nothing happens.

Antivirus removed the exe

Exclude the folder and re-extract. Because the application injects into and reads another process, heuristic scanners flag it. Add the folder to your exclusion list rather than restoring the file individually, or it will be quarantined again on the next scan. Download only from the download page, so the file you exclude is ours.

It worked before the patch and does not now

Path of Exile updates move things the software reads. Check the changelog and Discord before troubleshooting your own setup — after a game patch the answer is usually a client update rather than anything on your machine.

Several machines, and remote setups

People run this in several ways. What works, and what to expect:

One machine, several game clients

The normal setup and the one the software is designed around. Each client gets its own FollowApp instance and its own profile, matched using the Process Selector. Your instance count is what limits how many you can run.

Mouse Without Borders

Works for controlling several physical machines from one keyboard and mouse. Be aware that it moves your real cursor between machines; if you have the game window focused on the wrong machine you will send inputs somewhere you did not intend. Bind the bot’s hotkeys to keys you do not otherwise use.

AnyDesk and other remote desktop tools

Usable. The common problem is that some remote desktop software drops or alters the input focus of the remote session when you disconnect, which can leave a client unable to receive input. If a session that was working stops the moment you disconnect, that is the cause — leave the session connected, or use a tool that keeps the remote desktop session alive.

Virtual machine plus VPN

People do this and it works, with one caveat worth knowing before you build it: the game is demanding of the GPU, and GPU passthrough in a VM is the part that will consume your weekend. Not a reason not to do it; a reason to plan for it.

Keep Alive — launching the client for you

Run on the main window starts the selected profile’s game client and loads the profile into it; Load attaches to a client that is already running. Keep Alive makes Run also relaunch the client whenever it closes, loading the profile back into the new process. Both are set up per profile in Edit Profile → Tools, on the Keep Alive tab.

Path: must be set — Run is greyed out without it. There is no Domain field; it is worked out from the user name. The swap checkbox’s full label is Swap this profile's captured config and login into the game folder on Run.

Several profiles, several accounts

Each profile can carry its own copy of the two client files that hold the saved login and the input and graphics config — production_Config.ini and production_login.credentials for Path of Exile, poe2_production_Config.ini and poe2_production_login.credentials for Path of Exile 2, in Documents\My Games\Path of Exile (or ... 2). To set it up for a profile:

1. Log into the game with the account this profile is for, with stay logged in ticked, and set the input config the way the profile needs it.
2. Close the game so the files are written.
3. Edit Profile → Tools → Keep Alive → Capture current. The capture is stored next to the profile, in Profiles\<name>.gamecfg\.

From then on every Run of that profile — and every relaunch after a crash — puts those two files into the game folder of the Windows user the client runs as, before the client starts, so it comes up logged into the right account with the right config. Log in as account A, close, capture into profile A; log in as account B, close, capture into profile B. Run profile A and the client comes up as A; run profile B and it comes up as B. Both can use the same Windows user, or each its own.

The copy that was in the folder is kept beside it: <file>.followapp-original the first time only, and <file>.followapp-last every time. If the swap cannot be done — nothing captured, the capture is from the other game, the folder cannot be written — the client is not started and you are told why. Copying a profile copies its capture; deleting a profile deletes it.

login.credentials is the game’s own saved-login file, copied byte for byte. FollowApp never sees or stores your Path of Exile password. If a profile’s login stops taking, the game has rotated that account’s saved login — log in as that account once more and capture again.

If you only want relaunching and one account, leave Windows User: blank. The client then runs as you, no password is stored, and the login swap still works.

It is the password, not the PIN

Password: is the password Windows itself holds for the account — the one runas would take. It is not a Windows Hello PIN, fingerprint or picture password. A PIN is usually 4 to 6 digits; if what you typed is that short, it is almost certainly the PIN, and Windows answers “The user name or password is incorrect”. If the account is a Microsoft account, the password is that Microsoft account’s password — and Windows only learns a changed one after you sign in with it once by password rather than by PIN.

Test login settles it in one click. If it fails, the launch will fail the same way; fix the credentials before pressing Run.

When it does not work

• Nothing launches. Path: is empty or wrong. It must point at the client executable itself. The line under the field says whether it was found.
• “Keep Alive could not start the game client: The user name or password is incorrect.” Windows rejected the credentials. Nine times out of ten the field holds a PIN rather than the account password. Press Test login after changing it; pick the account from the dropdown rather than typing it. If you are already signed in as that user, clear Windows User: instead.
• “the config swap failed”. The message says which step. Most often nothing has been captured yet for this profile, or the capture was taken from the other game.
• It launches but the profile does not load. The relaunched client is a new process. Confirm the profile is attached to it, not to the window that died — step 6.
• It relaunches in a loop. The client is failing at startup for its own reason. Launch it by hand once and read the error before blaming Keep Alive.

The HWID tab

The Tools window has a second tab, HWID. It lists the hardware identifiers the game client hashes into the machine ID it sends at login — motherboard, CPU and every physical disk, in the exact order the client feeds them to that hash — and the resulting ID. Refresh re-reads them and Copy all copies the list for a support ticket.

With Enable ticked, the profile replaces those identifiers with a generated set (Generate new IDs), so the game sees a different machine for that profile. IDs are per profile, not system-wide, so generate a set for each one. Because the identifiers are recorded when the client starts, before login, this only works through Run: Load is greyed out while Enable is on, and Bypass "Load" disable (Not recommended) is the override for people who know why they need it. Set the client path on the Keep Alive tab, and a Windows user if the game should launch as another account. A client running as a different Windows user needs FollowApp started as administrator.

Instances and pooling

One instance is one character under the bot’s control — in practice one running game client with a profile loaded into it. Not one game account, not one computer; your own character counts if you run a profile on it. A five-instance subscription runs five clients under automation at the same time, on one machine or spread across several — the licence does not care where they run.

Input mode is a separate setting and never changes the count. The dropdown above Load in FollowApp has four options: Internal — the bot works from inside the client it is attached to, your real cursor never moves, and several instances run side by side while you keep using the PC (around nine in ten members run this — it has more features and is far faster); Global Inputs (recommended) — the bot takes the actual mouse and keyboard, so the driven client must be the front window and the PC is not yours meanwhile; Controller (recommended) — the bot plays through a virtual Xbox controller, which needs the ViGEmBus driver and the client in controller mode (right-click the dropdown in FollowApp for the setup guide); Controller (PlayStation) — the same, through a virtual PlayStation controller. Xbox emulation stops at four pads per machine; PlayStation has no such limit, so it is the one for a stack of controller-mode clients. In either controller mode, tick Unfocused input (CTR) in Settings and the clients can sit minimised behind each other while the bot plays them. The external modes carry the “(recommended)” label because running outside the client is generally the safer arrangement. Auto-Input and the Manual inputs work in all four. Older guides that say “global vs instance” mean Global Inputs versus Internal — the old checkbox became the dropdown option.

• The limit counts what is running now, not what you have ever run. Close a client, start a different one, and the slot moves. There is nothing to release.
• If you are over the limit, the extra instance is the one that fails, not a random one. The instances already established keep working.
• Plans add together. Two five-instance subscriptions give you ten instances on one licence. If you want a plan kept separate — you are handing it to someone else, or isolating it on its own hardware — it can be split out into its own licence with its own key.

Machines are not limited

Nothing is locked to the PC the app signs in from. To run on another machine, put the key in the app there and sign in; the instance count is the only limit, however many PCs the key is on. The licence page lists the machines that have signed in with each key and when they were last seen. If one of them is not yours, re-issue the key from the same page — the old key stops working at once.

Choosing a plan

Count the clients you intend to run at the same time. That number is your plan. The leader you play manually counts too if it has a profile loaded into it, and does not count if you are simply playing that character. If you are unsure, start smaller — adding instances later does not require rebuilding anything.

Controller support

“Controller” means two different things in FollowApp, and they are frequently confused:

• Controller input mode — the bot plays through a controller of its own. Pick Controller or Controller (PlayStation) in the input dropdown above Load, and the bot drives a virtual pad instead of the mouse and keyboard. You are not holding anything; the bot is.
• Controller passthrough — you hold the controller, and FollowApp turns your stick and button input into keyboard keys for the client it is attached to. You are playing. Set up in the Hotkeys dialog, per profile.

They can be combined, but they are independent settings.

Controller input mode — the bot holds the pad

What it needs:

1. The ViGEmBus driver installed on the machine. It is what lets FollowApp present a virtual controller to Windows. Without it the bot cannot create the pad, and nothing moves. Right-click the input dropdown in FollowApp to open the setup guide.
2. The game client in controller mode. The bot’s inputs arrive as gamepad input, so the client has to be reading a gamepad.
3. Select Controller or Controller (PlayStation) in the dropdown, then load the profile as usual.

Your real mouse and keyboard are left alone, as with Internal.

• Xbox or PlayStation. They play the same; the difference is how many. Xbox emulation stops at four pads per machine, PlayStation has no limit, so a stack of controller-mode clients on one PC wants Controller (PlayStation).
• Unfocused input. Tick Unfocused input (CTR) in Settings and the game window does not need to be in front — controller-mode clients can be minimised behind each other while the bot plays them. Without it the client has to be the window in front.
• Player 2. Edit Profile has a Player 2 checkbox marked “Path of Exile 2 only”. It is read only in a controller input mode, and it makes that profile play the second local player. Leave it off unless you are deliberately running a two-player Path of Exile 2 session.
• Auto-Input works here too. In controller mode the bot reads the skills on the pad buttons and plays them with the same rules as on keyboard and mouse; pad slots run on their Auto defaults.

The rest of this section is about passthrough — you holding a controller.

Pick the device first

Set Device Index:, then move the left stick and watch the Left Stick X / Y: readout beside it. If the numbers move, you picked the right device. If the readout is dead, nothing downstream will work and there is no point configuring the mapping table — step through the indices until it responds.

The mapping table

Twenty-six controls, each sending one keyboard key: A, B, X, Y, LB, RB, LT, RT, the four D-pad directions, Select, Start, the two stick clicks, both sticks in four directions each, and Player 1: and Player 2:. There is a Clear button beside the heading and a Defaults button at the bottom of the dialog.

Player 1: and Player 2: switch which of your two profiles the controller is driving — Player 2 being the profile with the Player 2 box ticked in Edit Profile (Path of Exile 2, a controller input mode). In Path of Exile 1, where there is no Player 2 profile, these two keys do nothing. That is what makes a controller useful for multiboxing: one controller, and you swap which character it steers rather than reaching for the keyboard.

Three things that catch people

• The keys you map must be bound in game. Mapping A: to Q does nothing unless Q does something in Path of Exile. Check the mapping against your own bindings, not against what you assume the defaults are.
• For passthrough, put the game into keyboard-and-mouse mode, not controller mode. If the game's own controller support is active you get both interpretations at once and every input fires twice. (A controller input mode is the opposite case: there the client must be in controller mode.)
• Do not map anything to INSERT, DELETE or END. Those are activate, pause and unload — step 7. A stray thumb unloads the bot in the middle of a map, and it reads as a crash rather than as an input.

AutoBot setup

AutoBot runs maps unattended: it opens the map device, rolls and runs the map, explores, fights, loots, stashes, and starts the next one. It is the same download as FollowBot — if your subscription includes AutoBot it is a checkbox in the main window, and there is nothing separate to install.

Do the FollowBot setup above first. AutoBot builds on the same profile: the same keybinds, the same loot filter configuration, the same process selection. If those are wrong, AutoBot fails in ways that look like AutoBot problems and are not.

Turning it on

In the main FollowApp window:

1. Select the profile you want to run.
2. Tick Autobot.
3. Use the dropdown beside it to choose the AutoBot mode for this profile.
4. Press Load, then use the Process Selector if more than one client is running — step 6 above.

Two buttons are worth knowing about:

• AutoBot Options — the full configuration described below.
• AutoBot HUD — a live view of what AutoBot is doing, with the same options as a side panel. Use it while you are setting up. It is the difference between “it stopped” and “it stopped because there were no maps in tab 3”.

Map selection

Under Map Selection in AutoBot Options:

Roll regex: is how you express everything the three percentage fields cannot, including modifiers you refuse to run. Test the expression against real map text before leaving it running overnight: a regex that never matches means AutoBot rolls currency into a map forever.

Start with the percentage thresholds and no regex. Add the regex once the basic loop is working.

Map crafting

Device option: offers 20 choices: Don't set, Fortune Favours the Brave, Ambush, Blight, Domination, Harbinger, Settlers, Beyond, Essence, Torment, Ultimatum, Expedition, Ritual, Abyss, Heist, Anarchy, Breach, Delirium, Harvest and Legion. Don't set leaves the device option alone, which is what you want if you set it by hand and do not want AutoBot changing it.

Pick the option your build can survive unattended, not the one with the best return. A mechanic your character cannot handle is a death on every map.

Map device slots

Map Device Slots has six rows. Each row has a type — (empty), Map, Scarab, Currency, Fragment — and a name. Slot 1 is the map to run. Pick it from the list or type any name; the remaining slots take scarabs, fragments, currency and anything else the device accepts.

Type any name means exactly that. You are not limited to the list, which matters when a league adds something the list does not know about yet.

Replacing the built-in lists

The map and scarab dropdowns are built from lists shipped with the client — 30 maps and 58 scarabs. You can replace either without waiting for a client update. Put a file next to the executable:

One name per line, encoded as UTF-8. The file replaces the built-in list rather than adding to it, so include everything you want available, not only the new entries. Write the names the game uses, save the file, restart the application.

Exploration

Portal key: must match your in-game portal binding. If it does not, AutoBot finishes the map and then stands in it.

Materials and stash

Increase Delay ms: if stash operations are failing. Stash interactions depend on the server responding, and a short delay on a slow connection produces clicks that land before the panel has updated.

League mechanics and altars

League Mechanics (checked = engage) is a list of 13: Delirium Mirror, Abyss, Breach, Delve Sulphite, Essence, Heist Smuggler Cache, Legion, Settlers Ore, Shrine, Strongbox, Nameless Seer, Reflecting Mist, All-Flame Chests. Checked means AutoBot engages that mechanic when it meets it; unchecked means it walks past.

This list is AutoBot’s own. FollowBot has a separate league mechanics checklist with different entries — see FollowBot features. Setting one does not set the other.

Eldritch altars have their own section:

Only whitelist takes an altar only when a whitelisted modifier is on offer, and the whitelist is ordered, so the entry nearest the top wins when more than one is available.

Aurabot

The Aurabot section supports a supporting character following the mapper:

Leave Name: blank to disable aurabot monitoring entirely.

The AutoBot HUD

A live view of what AutoBot is doing and why. Open it with AutoBot HUD in the main FollowApp window. It is independent of whether AutoBot is running: open it first and watch the whole session, or open it later to find out what a session that has been going for an hour is currently stuck on.

Automation that has stopped and automation that is waiting look identical from across the room, and they are fixed completely differently. A stopped bot needs a restart. A waiting bot is waiting for something specific that is often never going to arrive — an empty stash tab, a map that will never roll well enough, a portal key that does not match. Restarting it produces the same wait.

Four panes:

• Banner — current zone, connection state, uptime, and how much of the map has been revealed. The reveal percentage is the fastest way to see whether exploration is progressing or the bot is circling.
• Status — connection and slot, character vitals, and the live job stack: what it is doing now and what it intends to do after that. A job stack that has not changed in two minutes is the first sign of a stall.
• Map — a live map with markers for monsters, loot, objectives, portals, entrances, gravestones, shrines, chests, the current navigation target and dead zones. Pan, zoom, rotation, isometric squash, follow mode, a legend and a reveal-distance control, all persisting between sessions. A navigation target that keeps being reset, or a route that keeps ending in a dead zone, is a terrain problem rather than a settings problem.
• Thinking — the decision trace: what it decided, and what it decided it from. Filter by category chip.

Turn everything off except the category matching your symptom. A bot that is not moving is a NAV question. A bot that never enters a map is a JOB and ZONE question.

The full AutoBot Options set is embedded in the HUD as a scrolling column — same controls, same settings, no second window. Change a setting and watch the Thinking pane react; that loop is faster than opening AutoBot Options, changing something, closing it and guessing. Window position and size are stored in Crafts\AutoBotHUD.cfg beside the executable.

Reading a stall

The order that resolves most of them:

1. Status — has the job stack changed at all?
2. Thinking, filtered to JOB — what did it last decide, and what is it waiting on?
3. Banner — is it in the zone you think it is in?
4. Map — is there a navigation target, and is the route to it sensible?

Most stalls resolve at step 2, and the answer is usually a stash tab index, a threshold that can never be met, or a key that does not match the game.

Before you leave it running

Run through this the first time, and after every game patch:

1. Watch a full map with the AutoBot HUD open. Do not walk away from the first one.
2. Confirm it rolls a map, opens the device, enters, explores, kills, loots, portals out and stashes. If any step fails, it fails on every map.
3. Confirm the stash tab indexes are right by watching a stash cycle.
4. Confirm it survives. Watch its life bar through one map with your actual mechanic settings.
5. Check the loot filter is doing what you think — step 8 above.

When AutoBot stops

• It opens the stash and stops. Wrong tab indexes, or the tabs are empty. Indexes are zero-based.
• It rolls maps forever and never runs one. Your thresholds or your regex can never be satisfied. Lower the percentages, or test the regex against text from a map you would actually run.
• It runs the map and then stands in it. Portal key: does not match your in-game portal binding.
• It dies repeatedly. League mechanics, altars, or map modifiers you have not excluded, in that order. Turn all three off, confirm it survives, then add them back one at a time.
• It stopped after a game patch. Check the changelog and the announcements in the community before troubleshooting your own setup. Game updates move what the software reads, and the fix is a client update.
• It works for a while then does nothing. Open the HUD and read the last thing it logged in the Thinking pane. “Nothing is happening” and “waiting for something specific that is never going to arrive” look identical from outside.
• The map or scarab I want is not in the dropdown. Type the name into the field — it is editable. For a permanent change, replace the list with Crafts\NavMapList.txt or Crafts\NavScarabList.txt.
• I want to run it on Path of Exile 2. AutoBot runs Path of Exile only.

Related