Previous code list
Seven older reward strings are worth one quick test, including EVO60SPARK and EVO120HYPE.
These code strings read like older rewards, so use this page to separate older code history from live progression.
Try each code once, treat failures as old news, and keep one eye on the 240K-like milestone.
| Code | Try it for | If it fails | Use the reward on |
|---|---|---|---|
2K-LIKES | Previous reward string | If it fails, move on without rebuilding your route. | Use only after the live code box accepts it. |
THXFOR5K | Previous reward string | If it fails, move on without rebuilding your route. | Use only after the live code box accepts it. |
12klikes | Previous reward string | If it fails, move on without rebuilding your route. | Use only after the live code box accepts it. |
20000LIKES | Previous reward string | If it fails, move on without rebuilding your route. | Use only after the live code box accepts it. |
30K-LIKES | Previous reward string | If it fails, move on without rebuilding your route. | Use only after the live code box accepts it. |
EVO60SPARK | Previous reward string | If it fails, move on without rebuilding your route. | Use only after the live code box accepts it. |
EVO120HYPE | Previous reward string | If it fails, move on without rebuilding your route. | Use only after the live code box accepts it. |
Seven older reward strings are worth one quick test, including EVO60SPARK and EVO120HYPE.
Watch the 240K-like milestone before expecting a fresh reward string.
When a code works, spend rewards on the team route you are already building.
The live redemption box is final because code strings can expire before a player notices.
Hyphens and capitalization matter for codes like 30K-LIKES.
Previous-code history is useful for tracking developer cadence, not guaranteed inventory.
Do not assume that. Treat them as old reward strings and test them only inside the live game.
The next reward watchpoint on this guide is 240K likes.
Redeem only inside the live Evomon experience.
Previous codes help players recognize old reward strings and track the developer's code cadence.
Spend only when the reward supports your current capture, battle, or evolution route.