Aero / Tutorial
Check in this order
“It stopped working” is usually a new Roblox client build, a key in a non-valid state, or the bot being down.
1 · Find out which Roblox client is live
Roblox ships a new client build roughly every week. When the hash the bot sees differs from the last one it announced, it posts to the announcer channel — that post is the signal that an executor needs a patch.
- Open Roblox, click the avatar in the top-right, then Settings. The version line shows the build you are running.
- Compare it against the changelog page, which is built from Roblox's own client-settings endpoint: /changelog.
- If the announcer posted a newer hash than yours or yours is newer than Aero's patch, stop here — nothing on your machine will fix that.
Built against: Windows version-02c37bc51a384b8f, macOS version-3bc33ee7ffad426f. Client builds change more often than this page is rebuilt — /changelog is the live answer.
2 · Confirm your key is valid
Run /key info <key>. It does not consume the key and it prints the state. Every state and its meaning is on the key page; the short version: valid, expired, revoked, already redeemed.
3 · Per-OS steps
Download, Defender exclusions and injection order differ by platform — and are the parts not published yet.
Windows
Operating system: Not announced
Injection order: Not announced. Do not copy another product's order and expect it to match.
Antivirus: Not announced.
macOS
Version tracking works today; app-side steps are not announced.
Android / iOS
Not announced. Anything claiming otherwise is a clone — fake mobile builds are actively phished.
4 · Match the failure text to a cause
| You saw | Cause | Fix |
|---|---|---|
| Roblox has updated! Aero is not patched. | A newer client hash landed and the executor has not caught up. This is an announcement, not an error. | Wait. The announcer posts again when the version changes. |
| Invalid key | No key with that string exists in this server — usually a typo or a key from a different server. | Re-type it; verify with /key info. |
| Key expired | Past the duration the issuer chose. | Ticket for a new one; expired keys are not revived. |
| Key revoked | Staff killed it with /key revoke. | Ticket it if you think that was wrong. |
| Already redeemed | Single-use key, spent by the first account that ran /key redeem. | If it was not you, ticket it with the timestamp. |
| Bot offline on /status | No heartbeat younger than 120 s. Discord may be perfectly fine; the bot process is not beating. | Nothing you can do; the site's alerting covers this. |
5 · What a ticket needs
A ticket is only useful if it can be matched to a record. Include:
- the key, exactly as issued;
- the verbatim reply text — every failure branch in the bot has its own wording, and that wording identifies the cause;
- the Roblox version line from Settings, and your OS build (
winveron Windows, About This Mac on macOS); - whether /status showed the bot online at the time.
Closing a ticket writes a transcript, so a decision can be reviewed instead of re-argued.