PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Stun Duration is not affecting Boneshatter's pulse area of effect

Open
#4,219 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Lua
Stars
5.4k
Forks
2.4k
Avg merge
1d 12h
Merged PRs (30d)
26

Description

Check version
  • I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
  • I've checked for duplicate issues by using the search function of the issue tracker
What is the expected behaviour/value?

When I increase my Stun Duration via passive skills or support gems, I expect Boneshatter's pulse area of effect to reflect that.

Boneshatter gem states the following:

"Pulse has 15% increased Area of Effect per 0.1s of Stun Duration, up to 400%"

What is the actual behaviour/value?

image image

However, increasing stun duration does not have an effect on the area of effect (see above).

How to reproduce the issue

No response

Build code
https://pastebin.com/xTpt1jpW
Screenshots

No response

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

No source file or test is named. Start by loading the linked build code in Path of Building and comparing Boneshatter's displayed pulse area of effect with different Stun Duration values. Trace the Boneshatter calculation entry point and verify that the displayed area follows the gem's stated scaling.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.