Fast answer
The answer before the background
The current mobile storefronts advertise more than 50 playable gods, each with a unique card and passive skill. A useful roster record must also name the selected class, card pool, artifact, investment and mode because those fields can change a character's result. Do not count a new artifact as a new playable god or combine the paid Steam roster with mobile without checking the client. Recent mobile history identifies Nüwa, Jiang Ziya, Ra, Nefertem, Wukong and Leishen as character additions, while the 1.22.0 Hel, Frigg and Loki entries are artifacts.
Roster scope
Separate the product, patch and object type
| Field | Verified first-party evidence | Editorial rule |
|---|---|---|
| Mobile roster size | Apple and Google Play say 50+ gods | Use 50+ as a floor, not an exact permanent count. |
| Steam roster size | Steam description says 30+ characters | Do not import mobile additions without PC confirmation. |
| Character identity | Unique card and passive skill | Record both before comparing performance. |
| Class | Chosen separately to craft the deck | Do not treat a class name as a character. |
| Artifact | Separate system expanded in 1.18–1.22 | Attach it to a test; never add it to the roster count. |
Current names
Use patch notes as a dated change log
Apple's mobile history records Wukong and Leishen in 1.15, Ra and Nefertem with the Oracle class in 1.16, and Nüwa and Jiang Ziya in 1.17. Later notes concentrate on artifacts: Zeus, Hades and Poseidon in 1.18; Skadi, Heimdall and Seth in 1.19; Quetzalcoatl, Horus and Thor in 1.20; Tezcatlipoca, Xolotl and Inari in 1.21; and Hel, Frigg and Loki in 1.22.
Those names prove a dated addition, not a current tier. A character passive, card wording, class interaction or artifact cost can be reworked after release. The current client tooltip is the authority for the live value; the store history explains when and why a field changed.
Database schema
Record enough fields to reproduce a result
- Platform, complete version, mode and difficulty.
- God name, passive wording, unique card and current level or upgrade state.
- Chosen class, starting deck, custom-deck state and important card removals.
- Artifact name and level, plus any event or temporary modifier.
- Outcome over several attempts: clear rate, turns, damage taken and the repeated failure point.
Update policy
Retire stale rows instead of silently rewriting them
When a balance patch changes a passive, class or card, preserve the prior row as historical and start a new versioned row. This prevents an old screenshot from appearing to describe the current game. It also makes disagreement useful: two guides may both be correct for different patches, modes or investments.
A complete roster is not a copied list of names. It is a maintained set of identities and test conditions. Until a value can be read in the current client, mark it Unknown rather than filling the gap from an undated wiki, video title or search snippet.
FAQ
Common questions
How many characters are in Ancient Gods?
The current mobile store descriptions say 50+ gods. Steam's separate product description says 30+, so an exact count must be platform- and version-specific.
Is every named god a playable character?
No. Patch notes also name gods as artifacts. Confirm the object type in the current character or artifact menu.
Are mobile and Steam rosters identical?
The official pages do not establish full version or roster parity. Verify a named character inside the platform being documented.
What should a character comparison include?
Use the passive, unique card, class, deck, artifact, investment, mode, difficulty and version.
Sources
What we checked
Official listings establish current availability and product facts. Community pages are used for mechanics and build history, then labeled separately.