Grow a Chicken Fighter Fighter list & acquisition
A partial fighter roster plus a safe method for tracing egg sources, rare targets, levels, roles, and visible traits.
Start With Documented Names
Astro Chicken, Commando Rooster, and Tsunami Hen are documented examples in the available source set. Keep them labeled as documented rather than complete.
The live index can contain additional or changed entries, so a partial record must point players back to the current pool.
- Astro Chicken — documented
- Commando Rooster — documented
- Tsunami Hen — documented
- Full roster — check live index
Attach Every Fighter to a Source
Record the egg or acquisition path displayed when the fighter is obtained. Save the source beside the exact fighter name.
A roster becomes actionable when players can trace a name back to the current pool instead of reading an isolated list.
Record the Visible Build
Capture current level, attack role, visible traits, and any fusion history before comparing the fighter.
Two fighters with different levels or traits cannot support a clean ranking from name alone.
Archive Changes
Date each roster entry and mark older names, pools, or traits as archived when the live interface changes.
A visible history prevents a stale screenshot from being mistaken for the current catalog.
Choose an Egg You Can Open
Open the live egg index and identify an available egg whose pool supports the role you need.
Availability and requirements can differ by account state or update, so the current interface comes first.
Read the Displayed Pool
Review the names and rarity labels shown for that egg before spending. Do not add unseen fighters to the pool.
The pool is the acquisition contract visible to the player at that moment.
Complete One Hatch
Confirm the egg identity and current cost, then complete one open action while protecting the planned reserve.
One documented action produces a clearer before-and-after record than an uncontrolled batch.
Inspect the New Fighter
Save the exact fighter name, source egg, starting level, and visible traits immediately after the hatch.
This turns a random-looking result into a useful roster entry and comparison candidate.
Define the Rare Target
Name the fighter, trait, or role you are actually chasing and confirm that it appears in the current displayed pool.
A vague desire for rarity cannot produce a useful budget or stopping rule.
Choose the Supporting Egg
Compare available eggs by the pool shown on your account, not by an old image or an unsupported best-egg claim.
The correct egg is the one whose current pool can produce the selected target.
Set a Protected Hatch Limit
Enter the live cost, total resource, reserve, and target actions in the planner before opening repeatedly.
A hard limit keeps the rare chase from consuming the next feeder, recycler, fusion, or rebirth step.
Log Results Without Inventing Odds
Record each outcome and stop at the target or limit. Treat the run as a personal sample, not an exact probability table.
Small samples are useful for history but cannot establish a permanent hidden rate.
Before you act
| Checkpoint | When to inspect | Safe response |
|---|---|---|
| Exact name | After acquisition | Match the live label |
| Source egg | Before leaving the hatch screen | Connect fighter to pool |
| Visible build | Before comparison | Record level, role, and traits |
| Check date | When publishing | Archive stale entries |
| Available egg | Before spending | Use current account state |
| Displayed pool | Inside the index | Choose a pool matching the goal |
| Live requirement | At confirmation | Protect the reserve |
| Fighter result | After hatch | Record source and traits |
| Target | Before choosing an egg | Name one fighter or role |
| Supporting pool | In the live index | Confirm target is displayed |
| Hatch limit | Before the first action | Protect the reserve |
| Result log | After each action | Do not infer exact odds |
Fighter list & acquisition questions
Is this the full fighter roster?+
No. It is a documented subset and a method for checking the current index.
Which fighter is strongest?+
Normalize levels and choose a job before comparing attack, traits, and results.
Why record fusion history?+
A transferred or preserved trait can change how the fighter performs a role.
Are fighters only obtained from eggs?+
This guide documents the egg route described here; any additional live acquisition method should be checked separately.
Should I chase one named fighter?+
Only when the current egg pool supports that target and the budget has a stopping rule.
What if I hatch a duplicate?+
Compare its visible build and possible fusion use before deciding its value.
Is there a guaranteed rare hatch?+
No guarantee is claimed here; use only guarantees explicitly shown by the current game.
How large should the reserve be?+
Protect the resource needed for the next known progression action.
Can a common fighter still be useful?+
Yes. Role, level, traits, and account goal matter more than rarity alone.