Anime Vanguards Familiars Dex

Familiars are a separate build layer in Vanguards: 2nd Anniversary. They can provide stats, passive conditions, element interactions, or effects designed for particular units. A Familiar is not the same thing as a trait, a unit’s individual stat ranks, or a Memoria. Compare the entire pairing before investing: exact unit form, Familiar effect, source, restrictions, Memoria, mode, and current patch all matter.

This hub is a working Dex rather than a fabricated list of permanent numbers. Public community pages prove the system and many historical sources, but effects and availability can move between updates. The live collection, inventory, source panel, equip preview, and event shop are the deciding evidence for the current anniversary build.

Start with these Familiar guides

Familiar Dex fields

Record every Familiar with the same fields. Unknown values should stay blank until verified.

This structure prevents a Familiar name from becoming a false promise. Two players may own the same companion but compare different rolls, paired units, or modes.

Familiar source types

Familiars can be associated with normal stages, Dungeons, Raids, event routes, shops, recipes, gifts, or limited update systems. Community history also describes special Vanguard and Demon Familiar groupings. Those labels help identify a source family, but they do not prove that a route is currently open or that every Familiar in the family shares the same restrictions.

Use the live source button whenever available. If it points to a closed event, record the Familiar as currently unavailable rather than deleting it from the Dex. If it points to a shop, check the currency, reset timer, stock limit, and prerequisites before choosing a farming route.

Compatibility and unit forms

Check the exact receiving unit. A Familiar may support a general role, a rarity or class, an element, or one named unit. The base and evolved forms can also be treated differently. An icon appearing in inventory is not proof that it can equip to every unit.

Open the equip preview and confirm the target before changing anything. For transformations, summons, clones, or shadow units, test whether the Familiar affects the main unit, the secondary entity, both, or neither. Do not infer inheritance from similar wording in another passive.

Reading Familiar effects

Break the tooltip into five parts: trigger, beneficiary, stat or mechanic, duration, and limit. “After attacking” is different from “after a kill”; “this unit” is different from “units in range”; and a temporary window should not be compared with a permanent panel bonus as if their uptime were equal.

For a damage Familiar, measure actual cycles on a stable enemy. For a support Familiar, confirm that the intended carry is inside the effect and that overlapping supports stack. For an economy effect, compare when its total return overtakes its placement or upgrade cost. A large tooltip number can still be a poor pairing when its condition rarely activates.

Memorias are a separate layer

Memorias can add another effect to a Familiar build, but the Familiar and Memoria should be logged separately. Record which slot carries each effect and whether moving or replacing one item changes the other. The Memoria Guide covers source and pairing checks; the Memoria Maker page covers the reported inheritance workflow.

Do not consume duplicate Memorias simply to imitate a showcase. Put the effect you refuse to lose in the guaranteed base position shown by the current maker interface, and treat other offered effects according to the live percentages.

Build by role, not rarity alone

Start with the job the unit performs:

• Main carry: sustained output, attack-cycle reliability, coverage, or a condition that matches its strongest window.
• Burst unit: effect timing that overlaps the active ability or transformation.
• Area clearer: repeatable coverage and wave control rather than boss-only peak damage.
• Support or control: range, uptime, team effect, or status reliability.
• Economy unit: faster payback measured against the slot and upgrade budget.

Rarity can describe acquisition, not universal combat value. A common, flexible effect can outperform a rare restricted Familiar on the wrong unit.

Test a Familiar pairing

Choose one repeatable stage, one unit form, and one upgrade path. Run a baseline without the Familiar, then repeat with it equipped. Keep placement, targeting, support, and timing consistent. Record clear time, boss damage window, leak wave, or economy breakpoint—whichever metric matches the unit’s role.

Repeat enough runs to separate the Familiar from critical hits or targeting variance. If the result disagrees with the tooltip, reconnect to a current server and keep the entry marked unverified. One screenshot is evidence of an interface state, not a complete performance sample.

Limited, corrupted, and recipe decisions

Never place the only copy of a limited Familiar into a recipe without reading the result preview. Community descriptions of Demon Familiar recipes and corruption outcomes can be useful for locating the mechanic, but an old recipe image may not represent the current anniversary version.

Write down every consumed input and possible result. Lock protected copies. If the preview is ambiguous, cancel and test with replaceable materials or wait for direct evidence. Scarcity makes recovery harder, not the gamble more reliable.

Trading and transfer checks

Trading eligibility can vary by Familiar class and update. If a Familiar appears in the trade picker, inspect whether its Memoria, roll, corruption state, or unit attachment transfers with it. A community report about Vanguard Familiar exceptions should be treated as a prompt to inspect the final panel, not a rule to assume.

Price only the state the recipient can see. If the final confirmation does not display an attached effect, do not add that effect to the trade value.

Common Familiar mistakes

• Equipping by rarity without matching the unit’s role.
• Copying a build that uses a different evolved form or Memoria.
• Treating an old event source as currently open.
• Assuming summons or transformations inherit the main-unit effect.
• Combining a scarce input before reading the full recipe preview.
• Comparing peak tooltip numbers without measuring uptime.
• Calling an untested anniversary Familiar best in slot.

What needs live verification

For every current Familiar, verify the exact effect, roll range, source, availability, compatible unit forms, Memoria rules, crafting or corruption result, transfer behavior, and last-checked date. New Vanguard Familiars introduced around the anniversary should remain provisional until the collection and repeatable tests agree.

The Dex is most useful when it preserves uncertainty instead of filling gaps with guesses. Record what the game shows, choose a pairing for a real role, and retest whenever the experience update timestamp or Familiar tooltip changes.