Familiars are equippable companions that can add stats, passives, element interactions, or unit-specific mechanics. They are separate from Memoria, named traits, and individual stat ranks. Always record the eligible unit, source, passive text, roll range, corruption state, and patch before comparing a Familiar.
Familiar types
Community references group Familiars under Mythic, Secret, Exclusive, and special Vanguard forms. Update 14.5 added three Vanguard Familiars and Demon Familiars. Vanguard Familiars can be restricted to particular units; Demon Familiars are connected to demons in the Lunar Bridge Dungeon and a Demon Controller unit category.
Update 14.5 examples
The official changelog names Rose Bundle as a Vanguard Familiar for Lfelt (Love) from the Dungeon Shop. It also names Petrified Soul for Yehowach (Almighty) from the Rift Shop and Candy Ball as another new Vanguard Familiar. These entries are useful identity anchors, but the changelog warns their passives can change.
Demon Familiars drop from demons across Lunar Bridge floors. The official entry describes recipes and notes that unsupported pairings can produce a Harpist outcome. Check the current recipe panel before combining anything; a recipe image from launch may not reflect a later balance pass.
Choose a Familiar
Start with the unit’s job. A damage carry may benefit from output or condition synergy. A support may value Range, uptime, or a team effect. A control unit needs a Familiar that improves its actual status window rather than an unrelated panel number. A farm unit should be compared through payback timing.
Then check restrictions. Confirm the exact form, because a Familiar tied to an evolved name may not equip to its base form. Inspect whether the effect uses unit element, attack meter, kills, critical hits, debuffs, summons, or a named ability.
Source and availability
Use the Codex to trace the Familiar to a stage, shop, event, or recipe. A Wiki may still list unavailable mail or seasonal Familiars for historical completeness. Current availability requires the source to appear in the live game.
For a shop Familiar, compare the currency grind with other limited stock. For a drop, inspect pity and daily caps. For a recipe, list every input and valid pairing before consuming anything.
Corruption decisions
Odyssey and other systems can interact with Familiar corruption. Treat corruption as a tradeoff, not a free upgrade. Record the current Familiar, possible outcome, cost, failure or replacement rule, and whether the change can be reversed. Do not experiment on the only copy needed by your main team.
If a guide promises a guaranteed “best corruption” without showing the live choices and version, stop. The useful question is whether the result supports the unit and mode you play.
Compare Familiars fairly
Keep unit form, upgrade, trait, stats, Memoria, stage, and support fixed. Test one Familiar at a time. Measure the condition that matters: attacks in a fixed period, boss phase time, control uptime, path coverage, income, or survival. A large listed percentage can have low uptime.
Familiar mistakes
- Confusing a Memoria with a Familiar.
- Ignoring the eligible unit or form.
- Farming an unavailable event source.
- Copying launch passive values after a patch.
- Corrupting or combining the only useful copy.
- Calling a broad stat roll better than a unit-specific mechanic without testing.
Familiars FAQ
Are Vanguard Familiars a unit rarity?
No. This page uses Vanguard Familiar for the equipment tier introduced or expanded in 14.5, separate from Vanguard units.
Where should I verify a Familiar now?
Use the live Codex, unit equipment panel, source stage or shop, and recipe interface.