NIKKE July 31 Union Raid Guide: Boss List, Team Planning, Cube Allocation, and Pre-Raid Checklist
The next GODDESS OF VICTORY: NIKKE Union Raid is scheduled to begin on July 31, 2026 at 12:00 UTC+9 and end on August 6 at 04:59 UTC+9. This pre-raid guide explains how to turn the announced enemy list into five practical teams, allocate limited Harmony Cubes and equipment, coordinate daily attempts, and avoid locking resources into untested assumptions before the raid opens.
The next GODDESS OF VICTORY: NIKKE Union Raid is scheduled to begin on July 31, 2026 at 12:00 UTC+9 and run until August 6 at 04:59 UTC+9. As of July 28, the raid is still upcoming. That means players can prepare teams and resources, but final enemy levels, behavior, phase timing, and practical damage requirements must be confirmed after the live mode opens.
Union Raid is not a single-team damage check. A union clears a sequence of raid enemies across increasing levels, members use limited daily attempts, and a Nikke used in one attempt cannot simply be reused without regard to the mode's restrictions. The strongest preparation therefore combines account depth with union coordination.
The official announcement includes an enemy-list graphic. Use that list as the starting roster, but do not assume a portrait reveals every live mechanic. Boss versions can differ from campaign, interception, Solo Raid, or earlier Union Raid appearances. The guide below explains how to convert each announced enemy into a testable plan on July 31.
Record the Official Schedule Correctly
The announced period uses UTC+9:
Start: July 31, 2026 at 12:00 UTC+9.
End: August 6, 2026 at 04:59 UTC+9.
Convert both times to the union's common time zone and post them before the raid. The first daily reset can be especially confusing for international groups because members may think “July 31” means their local midnight. It does not.
Union leaders should also record the game's daily attempt reset. Do not rely on a member's memory from a previous raid. A missed final-day window cannot be repaired after the event closes.
Build an Enemy-List Worksheet
The announcement graphic identifies the enemies planned for the raid, but a useful boss list needs more than names. Create one row per boss and fill the details that the live client confirms.
Field | What to Record on July 31 |
|---|---|
Boss name and level | Exact live version and current raid level |
Element and weakness | Whether code advantage meaningfully affects the plan |
Parts | Location, durability, respawn, and damage value |
Red circles | Timing, number, and weapon types that can hit them reliably |
Dangerous attack | Trigger and prevention method |
Cover pressure | Whether cover repair or shielding is valuable |
Preferred range | Close, mid, or far behavior in the live arena |
Team status | Tested, provisional, or needs a specialist |
This worksheet prevents a familiar error: assigning a team because it worked against a similarly named boss months ago. The first members to encounter each live boss should update the row with evidence.
Five Teams Do Not Mean Five Identical Teams
Union Raid preparation often begins with five Burst-chain cores, but those teams should not be copies. Limited supports, burst cooldown reduction, elemental attackers, healers, and Harmony Cubes must be distributed according to each boss.
Start by identifying the account's irreplaceable units. Some Nikkes enable a specific damage dealer. Others provide universal attack buffs, cooldown reduction, healing, shields, or part damage. Mark which teams collapse when a unit is moved and which teams have workable substitutes.
A lower-paper-damage team can be correct when it handles red circles, survives an unavoidable attack, or destroys parts consistently. Damage calculated against a stationary training target is not the same as successful Union Raid damage.
The First Three Team Archetypes
Most accounts should begin with three reliable archetypes before creating specialized fourth and fifth teams.
The first is the primary boss-damage team. It uses the account's best-supported carry, stable Full Burst rotation, and strongest compatible buffers. Save it for an enemy where its range, element, and weapon pattern actually work.
The second is a part-breaking team. It values accurate weapons, distributed damage, and effects that benefit from destructible parts. This team should face a boss whose parts are reachable and worth destroying.
The third is a sustain team. It sacrifices some theoretical damage for healing, shielding, cover support, or defensive consistency. Use it when a boss can end an attempt early. A complete lower-damage run usually contributes more than a high-damage team that dies halfway through.
Creating Fourth and Fifth Teams
The final teams expose roster weaknesses. Instead of forcing an incomplete meta composition, build around the best remaining carry and supply only the support required for that carry to function.
Check Burst stages first. Every team needs a legal and practical Full Burst path. Then check cooldowns. A team that completes one rotation but stalls before the next may need cooldown support, a second Burst I option, or different timing.
Do not overlook older or lower-investment Nikkes with a useful niche. A unit that provides survival, elemental advantage, or reliable projectile coverage can outperform a higher-ranked character whose mechanics do not fit the boss.
The fifth team should be tested for minimum reliability, not benchmark perfection. If the union will clear early levels quickly, weaker accounts may never need all five teams on day one. Still, having legal formations avoids panic after stronger teams are locked.
Harmony Cube Allocation
Harmony Cubes are limited and cannot be equipped everywhere at once. Assign them based on each Nikke's bottleneck, not only a generic tier list.
Reload-related cubes help units whose damage collapses during long reloads or whose kit rewards ammunition flow. Bastion-style ammunition recovery can be valuable for sustained attackers when their weapon and team can trigger it consistently. Resilience-style reload speed can be better for units needing shorter downtime. Other cubes can support charge behavior, hit rate, or survivability depending on the available set and upgrade level.
Create a cube map before the raid:
Priority | Cube Decision |
|---|---|
Primary carry | Give the cube producing the largest tested damage gain |
Mechanic-dependent support | Equip only if the cube enables reliable skill timing |
Secondary carry | Use the best remaining compatible cube |
Survival bottleneck | Consider defensive value when death ends attempts |
Bench units | Leave unequipped until assigned to a live team |
Avoid moving cubes after preparing screenshots or presets without updating the plan. A formation copied from a guide can perform differently when its cube is missing.
Equipment and Overload Checks
Equipment preparation should fix obvious failures, not trigger a last-minute reroll spree. Confirm that primary attackers wear their intended gear, levels are complete where affordable, and Overload lines have not been accidentally left on a temporary configuration.
For damage dealers, evaluate ATK, elemental damage, ammunition, charge stats, and Crit only in the context of the weapon and kit. A universally perfect line does not exist. For supports, survivability and skill uptime may matter more than personal damage.
Do not reroll a strong usable line merely because a theoretical optimizer prefers another. Custom Modules are scarce, and the live boss may reveal a different need. Lock valuable lines before rerolling and preserve enough resources for post-launch correction.
Skill Investment Before the Raid
Spend skill manuals only when the upgrade benefits multiple modes or closes a confirmed breakpoint. Raising a primary carry's central skill can be sensible. Maxing a niche support solely because an unverified raid composition includes it is risky.
Read skill descriptions for trigger conditions. Buffs can depend on Full Burst, last bullet, charge completion, healing, shield status, target parts, or squad position. A support with the correct label may still fail to buff the intended carry.
If a new Favorite Item or balance adjustment is involved, use the current post-adjustment text. Old videos and calculators may reflect previous behavior.
Practice Before July 31
Union Raid enemies are not available in a permanent exact simulator, but players can still test team fundamentals. Use shooting range or comparable content to verify Burst order, cooldown continuity, ammunition stability, manual control, and survivability.
Practice the actions that commonly cause lost attempts: switching control to hit a red circle, withholding Burst for a dangerous phase, breaking a specific part, recovering aim after an animation, and using cover without losing the next rotation.
Record a short baseline for each team. Damage numbers from another mode are not raid predictions, but they reveal whether a change unexpectedly reduced performance.
Raid-Day Scouting
The first attempt against a newly reached boss should generate information for the whole union. Record attack order, red-circle timing, part behavior, damage spikes, and whether the proposed team survives.
A competitive union may assign a designated scout with a stable account. A casual union can simply ask the first attacker to post a screenshot and two sentences. The goal is to prevent several members from repeating the same avoidable failure.
Do not rush all daily attempts immediately after reset unless the strategy is already known. Waiting for one report can save more damage than acting early.
Daily Attempt Coordination
Union leaders should post which boss is active, approximate remaining health, and which team types are needed. Members should report before using a powerful team on a nearly defeated target if overkill would waste most of its damage.
Use finishers intelligently. A developing account can clear a low-health target, preserving an endgame member's full team for the next boss. Conversely, do not force a weak account to attack a mechanic it cannot survive merely to avoid overkill.
International unions need asynchronous instructions. A pinned message should be understandable without live officer supervision. Include the active target, forbidden mistakes, and deadline.
Damage, Survival, and Overkill
A Union Raid attempt should be judged by expected union progress, not only personal screenshot damage. Survival affects damage because a dead team loses remaining time. Mechanic handling affects damage because failed circles can stun or wipe the team. Overkill affects damage because excess beyond a boss's remaining health does not advance the next target.
Before attacking, compare the boss's remaining health with the team's normal range. If the team greatly exceeds it, use a smaller formation or ask another member. If the boss has an unpredictable lethal phase, retain enough survival rather than chasing a perfect theoretical run.
Do not reset or abandon attempts based on assumptions without reading the current mode rules. Confirm how attempts are consumed and whether any retry behavior exists in this raid.
Union Roles
A simple role structure improves execution:
Coordinator: posts schedule, active target, and assignments.
Scout: tests newly reached bosses and reports mechanics.
Damage specialist: uses optimized teams on high-health targets.
Finisher: closes low-health bosses efficiently.
Support analyst: helps members repair incomplete Burst chains or survival.
One person can hold several roles, but information should not exist only in private messages. The union needs a visible record.
Purchase and Resource Boundaries
Union Raid rewards and ranking can create pressure, but no member should be required to spend. Upgrade decisions should fit the broader account plan, and premium currency should not be used to repair a team that has not been tested against the live boss.
Players with an existing Gem purchase plan can compare Topuplist and the dedicated NIKKE top-up page. Confirm the account, server, product, and delivered contents. A July 31 raid deadline is not a reason to exceed a personal budget.
Unions should publish participation expectations separately from spending. Attendance can be requested; purchases should remain optional.
Final 24-Hour Checklist
Before the raid opens, confirm five legal Burst chains, main cubes, primary equipment, skill configurations, and local start time. Save team screenshots but label them provisional.
After opening, inspect the live enemy list and rules. Update the boss worksheet, assign scouts, and hold rare upgrade resources until a real problem appears. Check that adjusted Nikkes use current skill descriptions.
Before each daily reset, use remaining attempts, claim any available rewards, and post the next target. Before the final event deadline, convert August 6 at 04:59 UTC+9 to local time and finish early.
Common Mistakes
Do not copy Solo Raid teams without checking Union Raid restrictions. Do not place the same cube in multiple planned teams. Do not use the strongest team on a nearly defeated boss. Do not assume a returning boss behaves exactly like an older version. Do not reroll equipment impulsively.
Other errors include broken Burst chains, supports buffing the wrong target, missed red circles, and unclear reset times. Most are preventable through a five-minute review.
Final Recommendation
Prepare depth, not one perfect screenshot team. Turn the official enemy graphic into a live worksheet, distribute limited supports and cubes, and let the first attempts confirm mechanics. Use stronger accounts where they create the most union progress and let developing members handle suitable finishes or early levels.
The July 31 raid remains future content as of July 28. Plans should be ready, but final teams must remain flexible until the live client provides boss behavior, levels, and rules.
FAQ
When does the next NIKKE Union Raid start?
It is scheduled to start on July 31, 2026 at 12:00 UTC+9 and end on August 6 at 04:59 UTC+9.
How many teams should I prepare?
Prepare up to five functional Burst-chain teams, while recognizing that actual daily use depends on raid restrictions, boss progress, and union assignments.
Should every team maximize damage?
No. A sustain or mechanic-focused team can produce more real damage when a theoretical glass-cannon team dies early or fails red circles.
Can I reuse the same Harmony Cube in every planned team?
No. Build an actual cube allocation map. A written guide or screenshot may assume equipment that cannot be shared simultaneously.
Where can I prepare NIKKE currency before the raid?
Players with an existing purchase plan can compare Topuplist and the NIKKE recharge page. Confirm delivery details and keep spending separate from union participation requirements.
Should I finalize teams before July 31?
Prepare provisional teams, but verify the live enemy list, mechanics, levels, and restrictions before committing scarce resources or all daily attempts.
