The dex, the S/A/B tier list, the independent element chart and the three Launch S1 teams have different maintenance histories. You can use them together if you check what each one actually establishes. This guide walks through that comparison using the teams already published on Lumi Master.
Editorial reviewed
Four useful tools with four different jobs
The dex answers entity questions: the current maintained English name, configuration range, recorded trait, skills and family links for a particular Lumi. The tier list answers a different question by preserving 45 selected placements across S, A and B. The teams preserve three curated launch-season ideas. The chart preserves a separate set of single-element relationships. None of those jobs requires pretending that all four records were produced by one live balance test.
When you move between them, keep the creature identity but recheck the mechanic. Stable detail links help you do that even when an old recommendation uses a previous English name. A historical suggestion can remain worth reading without proving a current skill assignment. The point of the comparison is to identify what still matches and which assumption needs verification in your own game.
The dex has more elements than the independent chart
The maintained roster includes 17 elements, while the separate chart contains 16. Divine appears in the dex without a corresponding chart relationship. That mismatch is a visible maintenance boundary, not permission to invent a missing row. When a creature or move falls outside the chart’s recorded set, the chart does not answer that matchup question.
For charted elements, arrows indicate direction rather than a numerical multiplier. The chart also does not define a verified dual-type combination rule. Use a row to investigate an attack and a column to investigate a defense, then return to the creature’s skill field. A historical team with a favorable-looking element still needs compatible current skill behavior and enough resources to execute its plan.
Use a placement to start a check, not finish it
The published list contains 15 S entries, 19 A entries and 11 B entries. An unlisted Lumi is unranked, not automatically a lower tier. The list records placements rather than a complete quantified scoring system. It does not supply verified matchup win rates, sample sizes or detailed reasons for every position, so do not present those as if they had been measured.
When a listed creature interests you, open its detail and identify the condition that matters for your team. A high placement cannot establish that a specific skill is available in your release or that the passive solves your missing role. Conversely, a worker or an unlisted variant may be relevant to a narrow task that the list was never intended to score. Keep that task visible.
Light Spirit Cycle: verify the resource handoff
The historical Light Spirit Cycle lineup links Unicorn, Jellistel and Fistune. Its notes describe building the relevant light resource, using Flicker Assist to lower the signature’s cost, and considering the order of a Light Spirit action before Magic Trick swaps it. Those are sequencing ideas. They should be checked against the skill descriptions shown by your current game.
The current dex still records distinct resource and departure traits: Unicorn has a skill-related Flickergy gain, Fistune gains Flickergy when taking skill damage, and Jellistel restores a portion of maximum HP on departure. Those conditions are not interchangeable. Do not convert the historical phrase Light Energy into an assumed one-to-one numerical equivalence with every current resource label. Check the expenditure, gain and handoff separately before relying on a rotation.
Defense Break: separate entry effects from the attack
The historical Defense Break lineup uses Charigon, Sandlord and Psykat. It describes swapping an enemy’s important Light Spirit skill, using control, repeatedly bringing Charigon in to lower Defense, and then attacking with Dragon Rage. The current Charigon trait records a Defense-level reduction on entry. That provides a specific event to investigate; it does not establish how many safe switches an actual battle permits.
Sandlord’s current Parting Gift concerns transferring Attack and Defense Levels when actively leaving. Psykat has sleep-related choices and a limited healing trigger. These records explain possible roles in the sequence, but they do not prove that every historical turn order will work. Check whether the enemy state, available resources and chosen departure action still meet the next step’s conditions instead of treating the entire team card as a guaranteed combo.
Defense and Sustain: keep the form warning attached
The third historical lineup links Muscledog, Petrokat and Sundoll. Earth Retreat is used as a defensive handoff, Petrokat supplies conditional protection against critical attacks, and Sundoll sets Harsh Sunlight before its healing and defensive role. The team also specifically warns to keep Sundoll unevolved. That warning belongs to the recommendation and should not disappear when the lineup is summarized elsewhere.
Current records give you concrete checks: Muscledog’s Bulky responds to skill damage and Defense Levels; Petrokat’s protection needs a positive Defense Level on the active ally; Sundoll’s team damage reduction needs Harsh Sunlight while it remains eligible. Read those as separate dependencies. Weather loss, the absence of the Defense condition or a different form can change the plan. The recommended Psykat substitution is a historical alternative, not proof of an identical replacement role.
Adapt one dependency at a time
If a recommended skill is missing from your current creature, first name the job it performed. Was it a departure effect, a resource discount, a defensive boost or an enemy-state change? Then look for a recorded alternative that addresses that job. Do not substitute a move solely because its name or Power resembles the historical choice; the enabling event may be completely different.
Keep the proposed replacement conditional until your game confirms the interaction. A useful adaptation note says which skill changed, which part of the plan is preserved and which benefit is no longer promised. This is more informative than quietly replacing the historical loadout and continuing to label it a proven launch team. It also makes later corrections easier because the changed assumption remains visible.
A short check before you invest
Open the current detail pages for every planned member, compare the trait and selected skill, and check the resources needed for the first two actions. Verify the intended form, weather and target condition. If the main reason for choosing a creature is its tier placement, write a separate reason based on the role your own team needs. That exposes gaps a simple ranking cannot answer.
If the game contradicts a record, include the page, game version or server, creature form and exact field when contacting the site. Avoid reporting a failed sequence as proof that every entry is wrong. The goal is to preserve useful historical context while making current decisions from checkable mechanics. A recommendation becomes more useful when its uncertainty is visible, rather than hidden behind a season label.