PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Node Blocking
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Lua
- Sterne
- 5.4k
- Forks
- 2.4k
- Ø Merge
- 1 T. 12 Std.
- Gemergte PRs (30 T.)
- 26
Beschreibung
Is your feature request related to a problem? Please describe.
It is not related to any problem, just something that I think would be helpful when creating builds.
Describe the solution you'd like
The solution in question would be a simple interaction with any node on the tree, possibly through a right click, that "disables" the node, making it appear with a certain visual queue showing it is disabled (possibly crossed out with an x.)
This would then help when creating a build and looking through Node Power and Power Report as it would exclude blocked nodes from those reports, making it easier to exclude nodes that are calculating as high power nodes, when they actually provide stats that are not related to the build you are utilizing.
Describe alternatives you've considered
Another option would be to create some kind of filtering in the Power Report or Node Power to exclude keywords or something similar, but I think blocking nodes would be a simpler solution.
Additional context
Here would be a situation where this could be useful.
I'm making a simple elemental ice shot bow build, and when using the Node Power Report it is suggesting Command of the Elements as a powerful node, while it does add elemental damage with attack skills and resistance penetration, I know I don't want to use it as I won't be utilizing a shield.
It would be great to be able to quickly right click and choose block or ctrl + right click or some other shortcut to make it so it no longer shows up as circled in red and is excluded in the actual Power Report.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne damit, die Interaktion mit dem Node-Baum und die Einstiegspunkte für Node Power und Power Report zu lokalisieren. Implementiere den beschriebenen deaktivierten visuellen Zustand und stelle sicher, dass blockierte Nodes aus beiden Reports ausgeschlossen werden; fertig ist es, wenn ein Node durch eine Interaktion blockiert und wieder entsperrt werden kann, sichtbar markiert bleibt und nicht mehr in den Reports erscheint.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- lua
- Bereich
- desktop
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100