Before the attempt
- Save or record a layout that clears ordinary waves consistently.
- Note the first location where normal enemies leak.
- Keep protected damage behind the front layer.
- Do not change luck, placement, and the entire object mix together.
- Check the live interface for the current checkpoint and crafting state.
During the boss
Watch the first boss action that changes the run. If the front disappears before weapons contribute, durability or spacing is the test. If the boss remains exposed while damage stops, inspect range, placement, or uptime. If ordinary enemies create the leak, keep boss and crowd problems separate.
After the attempt
| Record | Why it matters |
|---|---|
| First failure point | Defines the next single change |
| Boss action | Separates custom pressure from ordinary waves |
| Reward screen | Provides current relic evidence |
| Crafting screen | Provides current recipe evidence |
Relic and crafting boundary
The official public description has referenced bosses with custom attacks and relics used to craft stronger objects. It does not provide a complete public recipe table. Record the exact in-game name, quantity, and resulting object before adding a recipe to a database.
Comparable retest
Move, add, or upgrade one boss-facing object, then repeat the attempt with the rest unchanged. Keep the change when the same failure occurs later or the clear becomes repeatable. A spectacular single result is a lead, not a universal best-base claim.
Frequently asked questions
Is Wave 20 a boss checkpoint?
Recent gameplay reporting describes a Wave 20 boss checkpoint. It is a community-observed detail and should be rechecked after updates.
What should I change before the boss?
Keep the ordinary-wave layout that already works and change only the first boss-facing failure: durability, coverage, or damage uptime.
What relic does the boss drop?
Use the current reward and crafting screens. A complete creator-published drop table was not found in the checked public sources.