There is a TLDR in this post. Cheers.
With The Pokémon Company and TiMi announcing that Pokémon UNITE is officially shutting down on March 23, 2027 (leaving behind only a non-playable "Library" mode for viewing records and models), a lot of people are wondering if modern AI coding agents and reverse-engineering tools can be used to rebuild or preserve the game as an open-source project.
Specifically, tools like REA (morluto/rea — Reverse Engineer Anything) on GitHub have been gaining traction. If you’re wondering whether we can just point an AI agent at the UNITE APK and get a playable open-source clone out the other side, the short answer is: not automatically—but AI agents can do a massive amount of the heavy lifting if a community team takes the right approach before the servers go dark.
Here is a breakdown of how tools like REA work, what Pokémon UNITE looks like under the hood, and the two realistic ways the community can actually save the game.
How REA + AI Agents Actually Work
REA is an open-source Model Context Protocol (MCP) server and CLI that bridges AI coding agents (like Claude Code, Cursor, Gemini CLI, and Codex) directly with disassemblers and decompilers like Ghidra, Hopper, and IDA Pro.
Instead of magically spitting out original source code, REA uses a Decompile → Understand → Recreate loop:
Decompile: REA unpacks an Android APK or native binary, pulling symbol names, strings, control-flow graphs, and decompiled pseudocode via Ghidra or Hopper.
Understand: It logs findings into structured "Evidence v2" records so the AI agent can trace how a specific game mechanic or network call works without hallucinating.
Recreate: The AI coding agent rewrites that logic from scratch in a target engine or language (like C# in Unity, GDScript in Godot, or Rust in Bevy).
What AI Can (and Cannot) Recover from Pokémon UNITE
Because Pokémon UNITE is a live-service mobile and Switch game built in Unity, different parts of the game present very different hurdles:
Client Code & Move Mechanics (YES, with effort): UNITE is compiled with Unity IL2CPP, which strips the original C# code and converts it into native C++ assembly (libil2cpp.so) alongside a global-metadata.bin file. Fortunately, because UNITE includes an offline Practice Mode and local bot matches inside the client APK, move state machines, hitbox timings, dash physics, and damage formulas exist locally in the binary. Pairing Il2CppDumper with REA/Ghidra lets an AI agent trace and rewrite those exact mechanics.
Live 5v5 Multiplayer Backend (NOT from the APK alone): Matchmaking, account login, lobby state, and 30 Hz UDP battle synchronization live on TiMi's remote cloud servers. REA can only inspect files on your machine. However, it can read the client's network serialization and Protobuf schemas to see what packets the client expects to send and receive.
3D Models, Animations & Audio (Requires community decryption first): Assets are stored in custom-encrypted Unity AssetBundles (ResPackerInfoSet.bin) using salted keys, AES/SM4 encryption, and Zstandard (zstd) compression. REA won't crack custom asset encryption out of the box, though existing community tools (like forks of UntieUnite) and runtime memory dumpers can decrypt the bundles so an agent can map them.
Stats, Cooldowns & Scaling (Already public): We don't even need AI decompilation for the raw math. Community projects like unite-db (py-unite-db) have already datamined and documented held item formulas, Battle Item cooldowns, and level-scaling curves.
Two Realistic Ways to Preserve Pokémon UNITE
If a community team uses AI agents to keep UNITE alive past March 2027, there are two practical paths—each with strict legal boundaries to avoid getting nuked by Nintendo/TPC lawyers:
1. The Server Emulator Route (Keeping the Original App Alive)
Rather than rebuilding the whole game in Unity from scratch, preservationists can use REA to inspect the Android APK's authentication, lobby, and match-server handlers.
Why the March 23, 2027 deadline is critical: While official servers are still online, developers need to record live network packet captures (PCAPs) of logins, lobby creation, and 5v5 matches.
The AI Agent's Job: By feeding both the REA client decompilation and recorded packet traffic to an AI coding agent, the agent can help write an open-source replacement backend server (in Go, Rust, or Python). Players would then sideload a patched Android APK or modded Switch build pointed at the community server—the exact method used to revive shut-down mobile games like Dragalia Lost.
2. The Clean-Room Open-Source Clone ("Bring Your Own APK")
If someone uploads an open-source GitHub repo containing ripped Pokémon 3D models, Holowear textures, audio, or copyrighted names, Nintendo will issue a DMCA takedown immediately.
To keep an open-source clone 100% legal:
Clean-Room Code Only: Use REA and AI agents to extract the functional behavior—how scoring zones, tall grass stealth, jungle buffs, and two-branch move upgrades work—and generate clean, original code in Unity (building on educational foundations like Marcy4000/Unite), Godot, or a custom engine.
Asset Extractor Architecture: Just like major open-source game decompilations (such as Ship of Harkinian for Ocarina of Time), the open-source repository distributes zero copyrighted assets. Instead, it includes a local script that requires the user to supply their own legally obtained Pokémon UNITE APK to unpack the 3D models and animations locally on their own machine.
TL;DR:
AI reverse-engineering tools like GitHub's rea + Ghidra won't let you one-click clone Pokémon UNITE, and hosting Pokémon assets on GitHub is an instant DMCA. However, combining Il2CppDumper + REA + live packet captures before March 23, 2027 makes building either a Dragalia-style private server emulator or a "Bring Your Own APK" clean-room Unity/Godot clone way faster than traditional reverse engineering.
Is anyone in the modding/datamining community already capturing match packets or setting up a preservation Discord before the March 2027 shutdown?
