PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Feature Suggestion: Allow to filter/combine lines

Open
#40 2 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

Hi
I really appreciate your work and am happy that impale is implemented, but it punctuates a long lasting problem with path of building. I'm talking about double and triplling of similar information where one statement would be much more clear. I have following example: https://pastebin.com/7tNQEbUe
If you allocate the small damage note next to the scion there are 5 lines displayed which all show similar information. I would like to have the option (probably in the config) to show one line that combines dps, poison dps, impale dps and ignite dps (Probably the most important information that currently isn't provided at all) and another line that maybe shows only hit dps (for trashclear). The other lines wouldn't be shown in my comparison screen. They can still be shown on the left (even though I know people that don't want them there as well), but most importantly the comparison pob provides is shown in a better manner.

This is also an issue with other stats, f.e. i have a coral ring in above pastebin. Many builds wear an item that gives them life for tankyness and int for requirements. These 2 stats result in 12 lines on the comparison screen. I have played builds for which any single displyed line gives vital information, but most builds care about a maximum of 3 of these lines. Just giving us the option to filter would be a big upgrade.

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

Start by reviewing the linked Pastebin example and the comparison screen described in the issue. Trace how damage and item-stat lines are presented, then determine how configuration should control filtering and combining. Done means users can select a concise comparison view while retaining the existing detailed lines where desired.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.