PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Tincture value issue

Open
#10,322 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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 open and closed issues by using the search function of the issue tracker
What platform are you running Path of Building on?

Windows

How is Path of Building expected to behave?
Image Image
How does Path of Building behave?
Image
How to reproduce the issue
Item Class: Tinctures
Rarity: Magic
Potent Prismatic Tincture of Overpowering
--------
Quality: +24% (augmented)
Inflicts Mana Burn every 0.39 (augmented) Seconds
8 Second Cooldown when Deactivated
Intangibility: 5%
--------
Requirements:
Level: 68
--------
Item Level: 85
--------
{ Implicit Modifier — Damage, Elemental, Attack  — 67% Increased }
100(70-100)% increased Elemental Damage with Melee Weapons
--------
{ Prefix Modifier "Potent" (Tier: 3)  — 67% Increased }
35% increased effect — Unscalable Value
47(47-51)% increased Mana Burn rate
{ Suffix Modifier "of Overpowering" (Tier: 1) — Damage, Elemental, Attack  — 67% Increased }
Melee Weapon Damage Penetrates 19(17-19)% Elemental Resistances
--------
Right click to activate. Only one Tincture in your belt can be active at a time. Mana Burn causes you to lose 1% of your maximum Mana per stack per second. Can be deactivated manually, or will automatically deactivate when you reach 0 Mana.
PoB for PoE1 build code

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

The payload names no source file, test, or entry point. Start by reproducing the provided magic Tincture case on Windows and compare the expected and actual screenshots, then locate the Tincture value calculation and verify that the displayed values match the item text; done means the reported value discrepancy is corrected and covered by an appropriate regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
desktop, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.