PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Additional sorting functionality

Open
#10,103 1 comment 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 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?

Linux - Wine

Is your feature request related to a problem?

No

Describe the solution you'd like

I would like more sort option. There are many things you can't sort by such as:

  1. area of effect
  2. skill effect duration
  3. damage converted to
  4. extra damage gained as
  5. reduced critical strike damage taken
  6. curse effect on you
  7. curse effect
  8. aura effect
  9. ailment duration
  10. ailment total damage
  11. ailment effect
  12. cooldown recovery
  13. penetration
  14. stun duration
  15. stun threshold
  16. enemy stun threshold
  17. elusive effect
  18. recoup
  19. maximum resistances
  20. cost efficieny (or cost of skill)
  21. impale chance
  22. impale effect
  23. maximum rage
  24. flask effect
  25. flask recovery amount
  26. flask effect duration
  27. flask charges gained
  28. flask charges used
  29. flask recovery rate
  30. focus recovery rate
Describe alternatives you've considered

Having 30+ poe wiki pages open.

Additional context

This would be much appreciated, thanks!

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 existing sorting controls and the data used by them. Map each requested attribute to an available sortable value, then define the scope and ordering behavior for the list. Done means the agreed sorting options work consistently and are covered by appropriate checks.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.