Unscathed RNG community guides currently describe Basic, Light, Fire, Water, Earth, Night, and Demon-related Aura or biome categories. They do not agree well enough to publish every weakness and damage modifier as fact. This element chart therefore separates documented labels from relationships that still need a repeatable live test.
Use the enemy panel and action card as the current source. Record a relationship only when the same setup produces consistent weakness, resistance, or damage feedback.
Currently documented element families
Basic, Light, Fire, Water, Earth, Night, and Demon recur across current progression, biome, and combat guides. Biome coverage commonly maps Cyber to Basic, Eden to Light, Inferno to Fire, Monsoon to Water, Overgrown to Earth, Rapture to Demon, and Night to Night.
These labels are Community corroborated, while the complete combat weakness matrix is not. Confirm spelling and category on the live Aura and enemy cards.
An Aura can exist in current community data without proving how its element interacts with every defender.
Verify one matchup
Choose a repeatable Story enemy and record its displayed element. Use one attacker and one action under a stable account setup. Establish a neutral baseline, then use the claimed advantaged or resisted element.
Record hit or miss, displayed damage, critical state, weakness or resistance message, and active buffs. Repeat enough times to control for accuracy and variation. If the client produces a clear relationship message, mark it In-game verified with the date.
Do not infer a modifier from color, animation, or one critical result.
Build coverage without a complete matrix
Carry more than one element. Give the first slot a dependable action, the second a contrasting element, and the third a flexible answer. If the current mode uses a different lineup size, preserve the diversity principle.
When a fight stalls, swap one Aura and repeat. If the change improves results, determine whether element, skill kit, accuracy, or account support caused the improvement.
Keep alternate elements even when a tier list ranks them lower; coverage can matter more than global rank.
Connect elements to farming
Choose the target Aura element before a biome session. Align the active state, skill-tree branch, Gem, Trait, equipment, and potion only when their live descriptions apply to the same element.
Do not assume a biome bonus equals a combat weakness. One affects rolling or farming; the other affects a battle relationship. Record them as separate systems.
Use Biomes and Luck for target setup.
Handle conflicting charts
Check publication date, direct game evidence, and whether two pages copied the same underlying claim. Prefer the current live message over a static chart. If two independent current sources agree but the client cannot be tested, label the relationship Community corroborated rather than Official.
Leave unsupported cells unknown. A smaller chart with honest confidence is safer than a complete cycle invented from genre conventions.
After a balance update, re-test the equipped team’s most important matchups first.
Use the chart in each mode
Story lets you repeat an enemy and build reliable records. World bosses may have phases, adds, or other mechanics that complicate the comparison. PvP opponents can switch Auras and support, so carry a backup instead of relying on one counter.
Record the mode with every result. A relationship may be consistent while the practical build value changes between PvE and PvP.
The Combat Guide covers the action loop, and Best Builds turns coverage into a lineup.
Troubleshoot an unexpected result
When a claimed advantage produces ordinary or reduced damage, verify that the intended Aura and action were selected, the defender’s element was read correctly, and no critical, status, equipment, or temporary effect changed the comparison. Repeat the neutral baseline in the same encounter rather than switching to another enemy.
If the client displays no weakness or resistance message, keep the relationship provisional. A difference can come from action power, accuracy, account upgrades, or random variation. Preserve the alternate Aura until the result is understood; do not sell it because one chart expected another outcome.
After an update, retest the relationships used by the active team before spending on an element-specific Gem, Trait, skill branch, or potion. Those commitments can remain expensive even when the combat modifier changes.
Verification status
Community corroborated: the currently documented element families and their common biome pairings. Community reported: individual weakness claims found in launch guides. Needs in-game testing: complete attacker-to-defender matrix, exact damage modifiers, immunity, neutral exceptions, critical interaction, and mode-specific rules.
Record date, attacker, defender, action, result, and buffs before treating a cell as verified.