PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding-PoE2

Cadiro's Gambit: Perandus Arrows are not supported

Open
#2,415 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
1.9k
Forks
451
Avg merge
21h 16m
Merged PRs (30d)
68

Description

Check for duplicates

I've searched open and closed issues for "Cadiro" and "Perandus" and found nothing.

What platform are you running Path of Building on?

Windows

Is your feature request related to a problem?

Cadiro's Gambit (Primed Quiver) has the line "Each Arrow fired is a Crescendo, Splinter, Reversing, Diamond, Covetous, or Blunt Arrow", which is unsupported. The quiver currently calculates as if it only granted increased Attack Speed.

The Diamond Arrow is the one that matters for the DPS number: all its Hits are Critical Hits, with 60% increased Critical Damage Bonus. On a bow character with 29% Critical Hit Chance and a 4.28x Critical Damage Bonus, that Arrow alone is worth 903k Full DPS against 393k, so the item reads as far weaker than it is.

Describe the solution you'd like

The six Perandus Arrows are:

  • Crescendo: Chain 6 additional times, 60% increased Damage for each time they have Chained
  • Splinter: Split towards 6 targets
  • Reversing: Pierce all targets and Return to you
  • Diamond: all Hits are Critical Hits with 60% increased Critical Damage Bonus
  • Covetous: enemies killed drop items with 600% increased Rarity
  • Blunt: 600% increased Stun Buildup

Each Arrow is rolled independently, so averaging behaviours as different as Chaining and guaranteed Critical Hits into a single number is not meaningful. A config dropdown that picks which Arrow to calculate, in the shape of the existing "Random element mode" for modifiers that choose an element, keeps every number honest and leaves the default behaviour unchanged.

Describe alternatives you've considered

Applying all six at once, which would report a character that Chains, Splits, Pierces and always Crits simultaneously. That number does not exist in game.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the codebase for Cadiro's Gambit, Perandus Arrows, and the existing "Random element mode" handling. Trace how item modifiers and configuration choices reach the damage calculation, then determine how a selected arrow should affect its behavior while preserving the default; done means each arrow can be selected independently without combining incompatible effects.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.