Raid Revamp Guide: Waves, Crystals, and Merchant

§Official event status#

§Enter and prepare#

• Open the current Raid entry and record the portal, map, and difficulty labels shown in your session.
• Keep one early attacker, one grouped-target or splash answer, one single-target answer, and one support or economy plan when your roster allows it.
• Save a short note of the team, traits, party size, and difficulty before starting.
• Treat any five-player or difficulty multiplier detail as a video report until the current lobby confirms it.

§Reported post-rework loop#

Two October videos describe a different route from the September pre-rework guide.

§Team and failure log#

Raid reports emphasize a longer route with repeated setup decisions. A useful test changes one variable at a time so a failure can be tied to a map transition, a leak, a trait choice, or a placement gap.

• Write down the first unsafe wave, the map segment, the enemy type, and the unit that failed to cover it.
• After a map change, rebuild the path coverage before spending the full refund on economy.
• Keep the carry and support roles visible in your notes, even when unit names differ between reports.
• Retry the same difficulty after one adjustment before changing the entire roster.

§Reported rewards and crystal spending#

The official event record does not publish a reward table, trait cost, or crate price. Keep enough crystals for the current team plan, then verify the live cost before treating any video value as current.

§Merchant and new content#

• Two videos point to a merchant cave behind the lobby or play area. Use the current stairs and visible shop marker as the route check.
• The official event description mentions a new unit in the Raid merchant and evolutions, without naming the unit or publishing its cost.
• Do not use the HAVI title percentage as a drop-rate claim. The video supports a rare Deer card report and card-stat observations only.
• Record the shop rotation, unit name, cost, and reset time together if the live panel exposes them.

§Do not mix pre-rework and post-rework reports#