Weapon upgrade

Cerulean Cloud Sword 'Arges'

Arges turns Blade toward Lightning Damage and replaces Sheath with Cloud Slash. Build Residual Lightning from Storm Cloud’s independent strikes, then spend 5 MP to consume the stacks in a wide slash.

Source-backedbladelightningstorm cloud

Source version: 1.0.31
Source reviewed: 2026-10-19
Current version: Pending review
Last verified: Pending review
Introduced: 1.0.31
Index status: Published

Use it in your run · Editorial guidance

When to choose Cerulean Cloud Sword 'Arges'

Choose Arges when Storm Cloud is producing independent lightning strikes and you are building Lightning Damage. Each of those strikes supplies one Residual Lightning stack for Cloud Slash. The upgrade also reduces Weapon Attack damage by 20% and replaces Sheath, so compare its offensive loop with the defensive action you give up.

1.Get Storm Cloud striking independently before evaluating stack generation; the recorded trigger is the cloud’s own lightning, not every source of Lightning Damage.
2.Reserve 5 MP for Cloud Slash and watch Residual Lightning build toward its 20-stack cap.
3.Consider a safe opening near a five-stack breakpoint: the recorded base-power sequence is 200/220/250/300% of Lightning Damage, with an additional 5% damage per stack.
4.Aim the wide slash in front of you and spend the stacks when the opening is safe. Cloud Slash consumes all stacks, and waiting at 20 cannot store more.

Assemble the Arges and Cloud Slash route

Recorded effect evidence

Weapon Attack damage is reduced by 20% and instead scales with Lightning Damage. Sheath becomes Special Attack: Cloud Slash. Each independent lightning strike from Storm Cloud grants 1 Residual Lightning stack, capped at 20. Cloud Slash costs 5 MP and consumes all stacks for a wide slash in front of you. The announcement lists base power increasing every 5 stacks at 200/220/250/300% of Lightning Damage, plus an additional 5% damage per stack.

This is a historical record from version 1.0.31. The source has been reviewed; current tooltip values and live-game behavior still require in-game testing.