Eight things, in order. Each one is finishable in a sitting, and nothing later depends on you having read anything except the step above it. Tick them off as you go — the page remembers where you are.
The build of 26 Sep 2026. Works with Path of Exile 3.29 and Path of Exile 2 0.5.5. One download covers FollowBot, AutoBot, CraftBot and the Overlay — your subscription decides which of them will load, not which file you fetch.
Tick Remember Password and you type the key once on this machine, not once a launch. After its first sign-in the machine is listed under Hardware; nothing is locked to it.
One instance is one character under the bot’s control — one running game client with a profile loaded into it. Not one account, not one computer; your own character counts if you run a profile on it. Your Main licence has 10 — so ten clients under automation at once, on one machine or spread across several. The eleventh is the one that fails, not a random one.
Plans add together. Main holds two FollowBot 5-instance plans, which is why it reads 10. If you want a plan kept separate — you are handing it to someone, or isolating it on its own hardware — it can be split into its own licence with its own key, the way Guild — Ryn was.
Nothing renews on its own. There is no card on file and no automatic charge. A subscription runs to its date and stops, and you renew it when you choose to. Main expires 14 Sep 2026; Guild — Ryn expires 27 Aug 2026, which is 6 days away.
Step 4. Your key has signed in from four machines and there are four instances live right now, so steps 1 to 3 are genuinely done — the app is installed, signed in and attached.
What is not done is a profile per character. You have four running; the fifth, sixth and beyond are what step 4 and step 5 buy you.
Read: licence Main · allowance 10 · 4 instances live · 4 machines signed in · first sign-in 4 Mar 2026.
The step marked You are here on the page above — and three of those ticks are not guesses: whether a machine has ever signed in with your key, whether more than one client is under automation right now, and whether the renewal reminder is on are all read from your account. The rest are yours to tick when you have done them.
If a tick looks wrong, it is the account that is right and the tick that is stale — the page re-reads it every time you open it.
All Knowing
Expect it. The application injects into and reads another process, which is the exact behaviour heuristic scanners exist to catch, so a flag is not evidence of anything either way.
What to do: make sure the file came from the download page and nowhere else, then exclude the whole folder, not the single file. Restoring the file on its own gets it quarantined again on the next scan.
If the exe is simply missing after extraction, that is what happened: it was removed silently. Re-extract after the exclusion is in place.
Read: faq.md → “Antivirus deleted it” · current build released .
All Knowing
Three causes, in order of likelihood. The key is in the wrong field — the key goes in Username, and Password stays empty. A typo — the key is four groups of five letters and digits with dashes between them, so copy it from your dashboard. Or Remember Password on that machine kept an older entry — clear both fields and paste the key in fresh once.
Yours is not an expiry: Main runs to 14 Sep 2026 and the server has not refused a sign-in from this key in the last 24 hours. So the refusal is happening before the key reaches us.
Worth ruling out first: an expired subscription looks identical from the client. Your dates are in step 8 and on the Overview — check them before you assume it is the password.
A wrong try costs nothing. A key has no account lockout, which is the point of it — nobody can lock you out by guessing.
Read: licence Main · authState ok · expires 14 Sep 2026 21:04 UTC · 0 failed auths in 24h · 4 machines signed in.
All Knowing
From the game's own executable, with a separate game login for each client. No virtual machine, no sandbox, no second Windows user — the game does not stop you running more than one.
Then one FollowApp per client. With more than one client running, FollowApp opens the Process Selector: drag the target icon onto the window you want that profile to own, read the resolved window name in the box underneath, and only then press Load.
Machine specs are the real constraint, not the software: several clients is a RAM and GPU question. Your DESKTOP-RIG is running three and LOFT-B450 one.
Machine specs are the real constraint, not the software: several clients is a RAM and GPU question. How many of your instances are live right now is on the Overview.
Read: DESKTOP-RIG 3 live · LOFT-B450 1 live (stalled) · allowance 10, 6 free.
All Knowing
Edit Profile → Settings → Name of character to follow:. Leave it blank and the follower follows the party leader, which is what most people want. Fill it in and it is an exact match — case and special characters included.
Position is separate, and it is two ranges rather than a point: a min–max Right and a min–max Forward. Position Helper sets both visually, with twelve presets — Back, Forward, the four diagonals, Back Half, Forward Half, Left Wing, Right Wing and the two Quads.
A follower that stops following in a new zone is almost always this setting with a name that no longer matches exactly.
Read: running under Main — Kaleth_Ignis, Vashti_Aura, Orin_Curse, Sabre_Totem (stalled 9 min).
Character names live in the app, not here — the portal only ever sees that an instance is running, never who it is.
All Knowing
Possibly none. A new profile’s Auto-Input tab plays the character from its skill bar — main attack held, other skills as they come off cooldown, flasks on charges — with nothing written. The Manual tab is for what its per-slot rules cannot say. Auto-Input.
If you are writing Manual inputs, two to start: a Timed Input on your utility flasks, and a Health / ES Trigger on a life flask. That is a follower that survives and keeps its buffs up, and it is enough to watch behave in a real zone before you add anything else.
After that, in the order people actually add them: Attack, then Buff Input for anything with stacks, then Link Input if you run a support.
Set Elapse: (ms) on everything that fires often, and turn on Humanize Inputs so the timing is not an exact cadence. On a Buff Input, use the buff ID rather than its name — names change with the client language.
From the reference: 11 input types · Auto Cooldown / Vaal Skill is on 8 of the 11 — not On New Zone, On Respawn or Auto Flask.
All Knowing
Yes. All three live in the Hotkeys dialog and each is a key-capture field: INSERT activate, DELETE pause, END unload. There is a Defaults button that puts all three back.
They are stored in the profile, so a rebind travels with Copy Profile and does not follow you to a profile you built separately.
One rule, whatever you choose: do not map a controller button to any of them. A stray thumb on unload in the middle of a map reads as a crash and is not one.
One instance is one character under the bot’s control — one running game client with a profile loaded into it. Not an account, not a PC; your own character counts if you run a profile on it. Main gives you 10 of them because two 5-instance plans are pooled into it, and right now 4 are live — three on DESKTOP-RIG, one on LOFT-B450.
One instance is one character under the bot’s control — one running game client with a profile loaded into it. Not an account, not a PC; your own character counts if you run a profile on it. Plans on the same licence pool into one allowance, and the number you have is in step 7 above.
Machines are not a limit. Four PCs have signed in with Main’s key and Hardware lists them, but nothing is locked to them; sign in on a fifth and it is listed too. Instances are how much runs at once, wherever it runs.
Machines are not a limit. Hardware lists the PCs that have signed in with your keys, but nothing is locked to them; sign in on another and it is listed too. Instances are how much runs at once, wherever it runs.
Nothing needs releasing. Close a client and its instance frees immediately.
Read: licence Main · allowance 10 (2 plans pooled) · 4 live · 4 machines signed in.
All Knowing
Guild — Ryn on 27 Aug 2026 — 6 days. Main runs to 14 Sep 2026. Nothing renews on its own, so both of those are dates you act on, not dates something happens to you.
When Ryn lapses, its two running instances stop and the client says the subscription expired. The key and the settings all survive; renewing turns it straight back on.
Your dates are in step 8 above, read from your account when this page opened. Nothing renews on its own, so each of them is a date you act on, not a date something happens to you.
When one lapses, its running instances stop and the client says the subscription expired — not “no subscription found”. The key and the settings all survive; renewing turns it straight back on.
I can turn on the reminder for you — it is the same operation as the button on this page.
Proposed actionset_renewal_reminderoffer expires in 4:58
Applies to
Main and Guild — Ryn
When
5 days before, and again on the day
Where
Your Discord account — no email needed
Running now
Nothing affected
Reversible
Yes — turn it off any time
Applies to
Every licence on this profile
When
5 days before it ends
Where
Your Discord account — no email needed
Running now
Nothing affected
Reversible
Yes — turn it off any time
Only this click commits it. The server checks the licences are yours before anything changes.
All Knowing
Yes. FollowApp reads a controller and sends keyboard input to the client it is attached to. Configure it in the Hotkeys dialog.
Set Device Index: and move the left stick — the Left Stick X / Y: readout beside it shows live values. If the numbers move, you picked the right device. If they do not, nothing further will work, so change the index first.
The mapping table covers 26 controls, each sending one keyboard key. Player 1: and Player 2: switch which of your two profiles the controller is driving — that is what makes it useful for multiboxing.
Two things catch people: the keys you map must be bound in game, and the game must be in keyboard-and-mouse mode, not controller mode, or every input fires twice.
Do not map anything to INSERT, DELETE or END — a stray thumb unloads the bot mid-map.
From the guide: controller support — device index, the full mapping table, Player 1 / Player 2.
All Knowing
Yes — Run on the main window starts the profile’s game client and loads the profile into it; Load only attaches to one that is already running. Tick Keep Alive - relaunch the game when it closes on Edit Profile → Tools → Keep Alive and Run also relaunches it whenever it closes. Path: must point at the client executable or Run is greyed out.
Leave Windows User: blank and the client runs as you, with no password stored. Test login tells you whether Windows accepts the pair before you press Run.
Several accounts: log into the game as the account the profile is for with stay logged in ticked, close it, press Capture current. Every Run of that profile then swaps that config and saved login into the game folder before the client starts. FollowApp never sees your Path of Exile password; the saved-login file is the game’s own.
From the guide: Keep Alive — Run and Load, the fields, the per-profile capture, the password rules. Source: keep-alive.md.
All Knowing
(Design mock — in the live portal she answers here from your account and the support knowledge base, and proposes any action as a button you click.)