Unofficial fan-made wiki
The expandable home for Animon species, elements, skills, locations, and capture notes.
Official materials describe around 140 known Animon species, 13 elemental types, and 5 core attributes. This page is prepared for a full database while keeping species-level locations and skills marked as unverified until they are checked from gameplay or official sources.
The official LumenTale site shows these type names: Fire, Water, Geo, Grass, Electric, Ice, Aura, Chakra, Demon, Data, Virus, Ancient, and Anomalous.
| Type | Tracking priority | Notes to collect |
|---|---|---|
| Fire, Water, Grass | Starter-style coverage | Early route availability, damage profile, support moves |
| Electric, Ice, Geo | Route and matchup utility | Field interactions, dungeon uses, burst options |
| Aura, Chakra, Demon | Specialized battle roles | Weakness behavior, status effects, skill costs |
| Data, Virus, Ancient, Anomalous | Late or unusual systems | Unlock timing, rarity, hidden interactions |
Official materials group Animon by five attributes: Felicis, Mestus, Furor, Horrens, and Sereum. Treat the attribute as a battle-role clue, then verify the exact role from skills, stats, and real fights.
| Field | Purpose | Example status |
|---|---|---|
| Name | Canonical species name | Needs confirmation |
| Element and attribute | Type identity and likely role | Official system confirmed |
| Location and time | Where and when players can find it | Needs gameplay verification |
| Capture method | Holoken notes, battle trigger, or special condition | Needs gameplay verification |
| Role | Damage, support, sustain, utility, or field help | Needs testing |
| Anispace use | Training, bonding, and customization relevance | Needs testing |
For a first playthrough, collect data in small loops: enter a new route, check encounters, note the time of day, return after nightfall, then compare. This gives the wiki better search pages later, such as "where to find Fire Animon" or "night-only Animon locations."
The LumenTale Animon list should grow from verified records, not copied guesses. The first version therefore focuses on database shape: name, element, attribute, location, time condition, capture note, battle role, Anispace relevance, and source status. Once those fields are stable, every confirmed species can become its own page without changing the site structure. That matters for SEO because "where to find X Animon" and "best X build" searches need individual URLs, not one overloaded table.
For now, the safest public claim is the system-level scope: official material references around 140 known Animon, 13 elemental types, and 5 core attributes. Species-level details should be added only when a source or gameplay check confirms them. Each entry should show whether the information is official, gameplay verified, community reported, or still pending. Readers trust a wiki more when it explains what is known and what is not known yet.
Capture notes should be short but precise. A useful entry should say where the Animon appears, whether time of day matters, whether the player needs story progress, and whether the encounter behaves differently from normal field battles. If a capture requires a Holoken action, a battle trigger, a dungeon event, trading, or a special quest condition, that should be visible in the first table row. The point is to answer the player before they scroll through a paragraph.
| Capture field | Why it matters | Example status |
|---|---|---|
| Route or landmark | Players search by place when they are stuck. | Pending per species |
| Time condition | Day and night can change discovery routes. | Pending per species |
| Story gate | Prevents players from hunting too early. | Pending per species |
| Holoken or battle note | Separates capture setup from normal combat. | Pending per species |
The 13 elemental types give the database its first filter system. Fire, Water, Geo, Grass, Electric, Ice, Aura, Chakra, Demon, Data, Virus, Ancient, and Anomalous should each have a future hub page once enough entries exist. A hub can summarize known Animon, early availability, likely matchups, and useful team partners. The current page should keep those names present so search engines understand the scope of the wiki from launch.
The 5 core attributes create a second research layer. Felicis, Mestus, Furor, Horrens, and Sereum may influence role identity, but an attribute should never replace actual testing. A proper Animon profile should record what the Animon does in battle: burst damage, sustain, status, support, field utility, or flexible coverage. That makes the future list useful for both collectors and players preparing for captain fights.
Every Animon entry should eventually carry one or more role tags. Suggested tags are early route option, capture priority, 1v1 specialist, 4v4 support, defensive pivot, resource-efficient pick, dungeon utility, night encounter, rare encounter, and Anispace favorite. These tags are plain language, which helps new players more than unexplained competitive shorthand. They also create internal links for future guide pages such as "best early Animon for beginners" or "4v4 team examples."
When the wiki does not yet know a role, it should say "role pending" instead of forcing a ranking. Thin but honest structure beats a confident tier list with weak evidence. The first goal is to become the place players bookmark while the game is new; accuracy is part of that growth strategy.