All posts
InvestigationBy Jim Liu

The Anime RNG Defense Roster Confusion, Explained

Why the 84-plus-unit tier lists and rarity ladders you'll find for "Anime RNG Defense" belong to a different Roblox game entirely, and how we caught it.

If you've searched for an Anime RNG Defense tier list, unit roster, or rarity ladder, you've probably landed on a page listing 80-plus units across Common through Mythic rarities, complete with roll rates and reroll mechanics. We almost built our tier list from that same data. We didn't, and this post is about why, because the mix-up is easy to fall into and we don't think we're the last site that will.

Two Roblox games, one very similar name

The game we cover, [JJK⛩️] Anime RNG Defense, runs on Roblox universe ID 9940812243, developed by a group called Mera., created March 26, 2026 and last updated July 11, 2026 according to the first-party Roblox games API. The Fandom wiki at animedefenserng.fandom.com and most of the third-party "EMD" (everyone-must-die-style tier list) sites that show up for the same search terms are describing a Roblox game on universe ID 6616093493 — a different title that happens to share almost the same name and the same tower-defense-plus-gacha genre.

Roblox doesn't stop two developers from picking near-identical titles, and search engines don't distinguish them either — both games show up interchangeably for queries like "anime rng defense codes" or "anime rng defense tier list." A reader has no easy way to tell which game a given wiki page is actually about, and neither, it turns out, did several of the sites we checked while building ours.

How we caught it

The tell wasn't subtle once we went looking, but it wasn't obvious from a first read either. We pulled the current unit list our game shows in-session and it didn't match a single name on the Fandom roster — not a rarity, not a unit name, nothing. At the same time, the codes we were independently verifying against six trackers (see how we verify codes) all correspond to badges and world names that exist in the actual game we play, which told us our code data was sound even while the roster data clearly wasn't.

Cross-checking Roblox universe IDs directly confirmed it: the Fandom wiki's own game link resolves to 6616093493, not 9940812243. Same genre, similar name, different game, different developer, different everything past the title.

Why we're not just relabeling their data as ours

The tempting shortcut here is obvious: take the 84-unit roster, keep the rarity tiers, swap the branding, and ship a tier list on day one. We're not doing that, for the same reason we don't publish a code the moment we see it mentioned once online. A tier list is a claim about which units are good, and a claim needs something backing it. We have zero verified units for this specific game right now, so our tier list page says exactly that instead of a borrowed roster, and our guides hub lists the guides we're not writing yet and names the missing data each one needs.

That's slower than copying an existing list. It also means when we do publish a roster, it will be built from screenshots of this actual game's roll screen and inventory — the kind of first-party evidence a search engine, and a reader, can actually trust.

What would fix this, and how you can help

The fastest path to a real roster is a screenshot: a photo of your unit inventory, a box-opening result, or the in-game luck menu. Anyone who sends one through the contact page gets credited on the page the data lands on. Until then, we'd rather our tier list and unit pages stay honestly empty than quietly become the ninth site repeating a roster that was never about this game to begin with.

We ran the same "which game does this actually belong to" check on a different search term recently — see does Anime RNG Defense have an egg hunt event? for what we found.