The Merge a Nuke nukes page tracks the database fields players actually need: merge recipe, base bombs required, income role, raid value, cooldown, health, best commander, patch, and verified date.
Database fields
| Field | Why it matters |
|---|---|
| Nuke name | Prevents confusion when pages and videos use different labels. |
| Tier | Shows where the nuke sits in the merge chain. |
| Merge requirement | Explains which lower pieces are needed. |
| Base bombs required | Helps players decide whether the next merge is worth the time. |
| Cash per second | Measures passive income once verified. |
| Health and raid damage | Separates defense value from launch value. |
| Cooldown | Matters for raid planning and recovery timing. |
| Best commander | Connects the nuke to commander effects. |
| Patch and verified date | Shows whether the value belongs to the current version. |
Keep or merge?
The central Merge a Nuke nukes question is not simply “what is the highest tier?” A player also needs to know whether keeping several productive nukes earns more than rushing one higher nuke, whether a raid nuke is worth risking, and whether the next commander pairing changes the answer.
What is verified now
Public sources confirm the merge-and-upgrade loop, raid pressure, and the need for current code and update tracking. Public sources do not yet provide a complete official stat table for every nuke. This site therefore publishes the database framework now and holds exact individual nuke pages until values are checked.
Planned filters
The Merge a Nuke nukes database is designed for tier, income, raid damage, health, rebirth requirement, commander synergy, owned status, and “can merge now” filters. Those filters should be useful only after the values behind them are real.