If ExoPanda is not detecting the game you're sitting in — it says “In Roblox Menu” or “Unknown Game” while the macro refuses to load — it's almost always a stale memory pointer, not a broken install. This page is the restart order that clears it.
You boot ExoPanda, jump into your Roblox game, and the app's current-game indicator never updates. It keeps saying:
The downstream effect is that the macro for your game won't load — ExoPanda gates macro start on detecting the right game first, so if the detection's wrong, nothing happens when you press start.
ExoPanda figures out which game you're in by reading Roblox's memory and following pointers to the relevant fields. Most of the time that works the first try. Occasionally a pointer goes stale — it still points somewhere valid, just not where the current game data lives — and the app keeps reporting the old state forever.
Stale pointers don't fix themselves on their own. You have to give Roblox or ExoPanda a fresh starting point so they re-link correctly.
Sometimes the detection just hasn't caught up yet, especially if you joined the game milliseconds after launching ExoPanda. Wait 10–15 seconds and watch the indicator. If it's going to update on its own, that's when it does.
If it's still stuck after that, move on to the restart sequence.
Try each of these in order. Most users land on the second one.
Fully exit Roblox while leaving ExoPanda running. Then re-launch Roblox and rejoin your game. This re-creates the Roblox process from scratch, which gives ExoPanda a clean pointer target.
If A didn't work, quit ExoPanda properly — from the system tray (see the next section), not just the X button. Reopen it. Then join your Roblox game. Most stuck cases resolve here.
Close ExoPanda and Roblox. Reopen ExoPanda first. Once it's loaded, open Roblox and join the game. This is the nuclear option and almost always works.
Clicking the X on the ExoPanda window does not close the app. It hides it to the system tray on purpose — that little upward-arrow on the right side of your Windows taskbar. Individual macros, the auto-clicker, and any helper tools rely on the main process staying alive in the background, so the X has to be a hide rather than a quit.
That's also why so many “ExoPanda not detecting game” reports come down to two ExoPanda processes running — the user clicked the X, reopened the app, and now there are two of them quietly fighting over the same memory targets.
To actually quit:
From a clean tray, the restart sequence above will work the first try.
If the restart sequence doesn't clear it, the next most common cause is that Roblox is on a build that ExoPanda's memory layout doesn't match. That's the same root cause as ERR-OFFSET — the easiest fix is to get on the current live Roblox build, either manually or by letting the ExoPanda bootstrapper handle launches for you.
The other half of the same problem — outdated Roblox build means stale offsets.
Read guide →Why the optional bootstrapper exists and what it does for you.
Read guide →The hub page for every common ExoPanda issue and how to clear it.
Read guide →Drop a screenshot of the detection indicator in our Discord and we'll point you at the cause in minutes.
