Gragu heavy route

The profile uses Gragu, Veteran's Battle Axe, and Triarch Repeater to describe an acquisition path around the authored heavy setup. “Heavy” is a route label, not a measured damage tier or promise that the loadout wins every matchup. Confirm the three pieces independently and test the current moves before spending upgrades. The source establishes the recommendation boundary; the player's release build establishes whether the route is usable now.

Begin with Gragu and equipment already available so the Shell can be evaluated without confusing the result with two new weapons. Next obtain and test the battle axe's reach, recovery, and input sequence in a safe encounter. Add the repeater only after the primary weapon decision is understood. This sequence makes it possible to identify which piece changes the experience.

The acquisition list says when to seek a piece, not when to commit every upgrade material. Keep resources unspent until the moveset has been tried and the route source matches the game build. If a location or requirement differs, leave the target open, follow the attributed page, and record the discrepancy instead of assuming the profile is complete because all names appear in the database.

Use the map for a specific acquisition question and close nearby completion work only when the roadmap calls for it. An efficient route can share travel with other objectives, but a map marker does not prove the item was obtained. Confirm inventory in the game, then update the one shared local target.

Test whether the setup's pace, recovery commitments, and sidearm role fit the player's goal. Compare those observations with another profile using the same encounter and question. Do not turn personal comfort into an objective DPS figure, and do not treat a successful boss attempt as proof that the profile is globally best.

A completed profile means the named loadout was assembled and intentionally selected for the local run. The limitations remain part of that completion receipt. If a later patch changes behavior, keep the earlier result tied to its version and reopen only the affected evidence rather than deleting all confirmed acquisition progress.

For the Gragu profile, preserve the reason the heavy route was accepted or rejected: the Shell choice, battle axe commitment, repeater role, and encounter used for the trial. Record which component created an unacceptable recovery or acquisition cost without assigning an invented damage value. If only the sidearm is unsuitable, keep Gragu and the battle axe confirmed while comparing another sourced sidearm route. If a version change moves a piece, reopen that acquisition question and retain the earlier inventory evidence. The receipt should explain the decision while keeping subjective feel separate from verified ownership. Retest only the changed component when the cited release build no longer matches.