Roblox-owned pages and public APIs for this exact universe. Strongest evidence; numbers print as read.
[W4] +1 Battle Cat Power Evolution Source Register
Every claim on this site traces to one of the sources below, each with its type, what it is used for, and the date it was last read (2026-10-03). When two sources disagree, the pages print both sides.
Source register
Named sources and what they support
Checked 2026-10-03. Official sources decide; trackers and videos only extend what official surfaces answer.
| Source | Type | Used for | Checked |
|---|---|---|---|
| Roblox games API (universe 10293967174) | Official | Title, description, visits, favorites, votes, server size, created/updated dates | 2026-10-09 |
| Roblox badges API | Official | Welcome and Reached world 2! badge statistics | 2026-10-09 |
| Official game page | Official | Player-facing description and store | 2026-10-03 |
| +1 Battle cat creator group | Official | Creator identity (group 943021972, verified creator field) | 2026-10-03 |
| Creator Exchange listing | Creator Exchange | CCU, like ratio, rank, owner PowerCoreLLC; 500-Wins code entry listed as 3777 on October 3 and as 3 on October 9 | 2026-10-09 |
| Roblox Den code list | Community tracker | Exact-game code list: 777, 666, and CCU with rewards and active state | 2026-10-09 |
| UrGameTips code list | Community tracker | Second current code list, checked October 7, 2026 by the source | 2026-10-09 |
| Rolimons listing | Community tracker | Live player snapshot and the +10 Pet (39 Robux) game-pass report | 2026-10-03 |
| Gameplay video, part 1 | Creator video | Exact-title gameplay reference; live values always re-checked in game | 2026-10-03 |
| Codes video | Creator video | Evidence that code strings circulate for this exact title | 2026-10-03 |
| Community Discord invite | Community tracker | Reported community server named like the creator group; ownership not creator-confirmed | 2026-10-03 |
Source and checked date: the register above, all rows read 2026-10-03. The two API rows are machine-readable endpoints, so numbers on other pages can be re-verified by anyone in seconds.
Evidence tiers
How each source type is weighted
The weighting explains why a page may print a tracker claim without adopting it as fact.
A third-party analytics listing built on the official universe ID. Useful for CCU, rank, and owner data the game page hides.
Independent trackers and listings. Claims keep the reporter's name and are re-checked before use.
Public videos of the exact title. Used to confirm that a feature or string circulates; values are always re-measured in game.
Exclusions
Sources this site refuses to cite
Same keywords, different games. These are excluded on purpose, and the exclusion is part of the method.
The Battle Cats (PONOS)
A different franchise with its own evolution trees; nothing from it describes this Roblox experience.
Battle Cat Evolution and similar-titled Roblox games
Different universes and creators; their codes, forms, and world gates do not transfer.
Secondhand stat tables
Per-click gains, rebirth multipliers, and world requirements circulate without a checkable origin; this site measures them in game instead.
Maintenance
How the register is kept current
A register is only as good as its refresh cycle. This is the exact one, so any reader can reproduce it.
The weekly API re-read
The two Official rows are plain HTTP endpoints. Each cycle re-reads the games API for universe 10293967174 (title, description, votes, visits, updated timestamp) and the badges API (award counts). A changed description line or update timestamp routes the edit to the updates page first.
The tracker sweep
Creator Exchange and Rolimons are compared against the official read the same day. A tracker that disagrees with the API keeps its name on the claim; a tracker that agrees graduates the number to cross-checked.
The in-game verification
Values the APIs cannot expose — per-click gains, rebirth panels, world gates, code redemptions — are verified in a fresh public server after every named update, then written back with their check date.
The conflict rule
When two sources disagree — 777 versus 3777 is the live example — neither is deleted. Both print with their reporters, and the recheck method travels with the table so the next reader can settle it themselves.
Using the register
Worked examples: from a claim to its source
Three claims from around the site, traced to their rows above — the same trace any correction request follows.
| Claim on this site | Register row | Reproduce it |
|---|---|---|
| “5,399,066 total visits and 12-player servers” (wiki, updates) | Roblox games API, checked 2026-10-03 | Query the endpoint with universeId 10293967174 and read the visits and maxPlayers fields |
| “329,477 players hold Reached world 2!” (world-2 guide, progression) | Roblox badges API, checked 2026-10-03 | Read awardedCount on the second badge row |
| “Creator Exchange lists 3777 for 500 Wins” (codes, resources) | Creator Exchange listing, checked 2026-10-03 | Open the listing for universe 10293967174 and read its codes block |
Code status
The conflict table built from the tracker sources above.
Update timeline
What each recheck found and when it happened.
Editorial policy
How the register is applied to every page.