Farever Companion Guide

System overview

For now, this wiki uses Companions as the main system name. Pet appears in player guides as an informal synonym, but the safer UI-facing term is Companions until a separate Pet tab is verified.

The companion loop currently has three strong anchors: H. Catchum as the critter quest NPC, Large Butterfly Net as the capture tool, and Collections or Collection Menu as the management area. Those anchors are enough to build a useful guide without inventing unverified combat bonuses.

Companion evidence table

Entity or term	What we know	Proof status
H. Catchum	Critter Trainer tied to Gotta Catch One and Hidden Critter data	Confirmed
Large Butterfly Net	Rare CaptureNet that tries to capture companions	Confirmed
Companions tab	Reported as part of Collections	Reported
Buttontail / Buttontain	Name conflict across sources	Needs verification
Grassflopper	Reported frog companion name	Reported
Sparkling Woolly Bell	Reported hidden companion from Crystal Mall route	Reported

How to think about companions

Do not build a combat guide around companions yet. The available evidence supports capture and collection, but it does not prove current companion stats, damage, gathering bonuses, or passive effects. If a guide says companions are cosmetic, treat that as a reported state, not a final rule. If a guide says they fight, ask for a tooltip or combat UI frame.

This matters for player trust. A companion page that says “best pet for DPS” before showing UI proof will age badly. A better page helps the player catch and equip companions now, while making it clear which mechanics still need proof.

Best first companion goal

The best first goal is not a tier list. It is completing Gotta Catch One and learning how companion capture works. After that, players can chase named companions such as Buttontail or Grassflopper when locations are verified.

What to verify next

The single most valuable proof item is a readable Collections screen. It should show the tab label, companion entries, category icons, and whether any tooltip has stats or bonuses. That one screenshot would answer multiple questions at once: whether Pets are a separate system, whether companions are cosmetic, and how names are spelled.

Naming policy

Use Buttontail only with a note that Buttontain appears in at least one guide. Use Grassflopper as reported, not final. Use Sparkling Woolly Bell as reported until the collection entry confirms exact capitalization and category.

Capture route priorities

A companion guide should prioritize repeatable player actions over a speculative tier list. The first repeatable action is getting a capture tool. The second is finding valid world companions. The third is opening Collections and checking whether the captured companion appears in the expected tab.

This order matters because players often arrive with one of two problems: they either cannot complete Gotta Catch One, or they caught something but do not know where it went. A good page should answer both without claiming unverified stats.

Companion names to handle carefully

The safest name policy is conservative. Large Butterfly Net and H. Catchum are strong. Grassflopper is useful but still needs a UI entry. Buttontail is probably safer than Buttontain, but the spelling conflict should stay visible until a Collections screenshot resolves it. Sparkling Woolly Bell has a strong narration lead, but the category is not locked.

Avoid creating a “best companions” table until there is proof of function. If companions are cosmetic, a tier list is mostly preference. If they provide bonuses, the tier list needs tooltip stats. If they fight, the tier list needs combat behavior. Those are three different page types, and mixing them would confuse players.

How this page should evolve

Once the UI is captured, this page can become a true database tool. Each companion row should include exact name, creature type, location, capture method, collection category, proof status, and whether the companion has visible stats. Until then, keep location rows short and proof-labeled.

The next strongest companion page would be a child page for Gotta Catch One, because that quest has a clear player problem and confirmed entity data. A separate Pets Guide should wait unless the UI proves that Pets are a distinct category from Companions.