Storm Cloud strikes
Let the cloud generate the resource while you keep moving.
Residual Lightning builds
Watch the stack count and your available MP.
Cloud Slash spends
Use a safe opening and pay 5 MP to consume the stacks.
Interaction documented in TEAM HORAY’s 1.0.31 notes. This diagram illustrates the sequence; it is not a game screenshot or a damage simulation.
01Assemble the core before adding support
Start with the Blade branch unlocked and identify Cerulean Cloud Sword Arges in the upgrade route. The 1.0.31 notes specify that Arges shifts weapon attacks toward Lightning Damage, applies a 20% weapon-attack damage reduction and replaces Sheath with Cloud Slash. This makes the build a change in how you generate and spend damage, not simply a reason to equip every item with a Lightning tag.
Get the Storm Cloud effect working before committing the rest of the board. The named stack source is the cloud striking on its own. If the cloud is absent, Arges cannot produce this loop merely because your Lightning stat is high. Keep useful general damage and defense while assembling the pair; when the cloud is available, you can start judging upgrades by whether they help the loop you now have.
| Piece | Job | Priority |
|---|---|---|
| Blade + Cerulean Cloud Sword Arges | Turns the branch into the Lightning / Cloud Slash route | Core weapon upgrade |
| Storm Cloud effect | Its independent strikes generate Residual Lightning | Core interaction |
| Lightning Damage | Supports the attack’s named damage scaling | Damage direction |
| MP available for Cloud Slash | Each activation costs 5 MP | Keep the spending action usable |
02Read Residual Lightning as a resource, not a timer
The documented cap is 20 stacks. Cloud Slash consumes the accumulated stacks, with base-power steps at five-stack intervals and an additional per-stack increase. Watch the stack count alongside the next safe attack opportunity. A ready boss opening is a reason to spend; a dangerous animation is a reason to keep moving while the cloud continues doing its job. Waiting for the cap is an option, not a universal instruction.
Keep the movement input and the spending input separate in your plan. If you have enough MP but the next enemy pattern forces you to dodge, do that first and use the slash when you can finish it. If you repeatedly have stacks but cannot afford the action, repair the resource problem before adding more peak-damage pieces. This helps distinguish three different failure cases: no stack generation, no MP to spend, and spending during an unsafe opening.
03Choose optional support by the problem it solves
Fretted Clay Tablet is an Artifact despite its name. Its 1.0.31 change raises the recorded chance of Storm Cloud avoiding consumption to 20/30/40/55/70%. Consider it when cloud retention is useful to the setup you actually have. It is support for the cloud’s consumption behavior, not proof that every lightning hit creates an extra Arges stack.
Rusty Tsuba is a different decision: its evolution needs blocks made with Sheath or Unsheath, while Arges replaces Sheath. Before trying to progress it in this route, check whether the remaining weapon action can perform the required block. If not, evolve it while using a compatible action before switching, or choose another defensive piece for this run. An item’s Blade association does not make its trigger compatible with every Blade upgrade.
A third possible support is Dull Resonance Stone when the current Move Speed reaches its 140% evolution threshold. Its benefit is Highest Elemental Damage, so compare the resulting stat with the Lightning direction of your run. Do not spend several slots reaching a threshold if it breaks the core interaction or the defense you need for the next room.
TEAM HORAY · 1.0.31 UpdateTEAM HORAY · 1.0.33 Update
04Keep the run playable when a core drop is missing
Without Arges, continue with the useful Blade upgrade you have rather than treating a Lightning item as a completed Cloud Slash build. Without Storm Cloud, keep a working attack route and leave space to adapt when a cloud option appears. Without a preferred support Artifact, maintain the core pair and choose survival or resource support you can use immediately. This separates the pieces the interaction needs from a screenshot-perfect inventory.
Before entering a boss fight, check that the cloud is active, independent strikes are adding stacks, Cloud Slash can be paid for, and the attack can be used in a safe opening. Use Comprehensive Training Grounds to inspect the unlocked pieces and their action changes before starting a new run. For the inventory, group your must-keep pieces in a saved Planner sketch, then fill the remaining cells with the support the run actually offers.