PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Allow node power calculation to consequtively calculate more than one statistic
まだ誰も着手していません。
- 主要言語
- Lua
- スター
- 5.4k
- フォーク
- 2.4k
- 平均マージ
- 1日 12時間
- マージ済み PR(30日)
- 26
説明
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
Is your feature request related to a problem?
Right now, having PoB calculate the node power only works for a single 'metric'. Meaning, if I choose any specific thing from the drop down, PoB calculates what nodes would increase that specific thing.
Sometimes, I don't only want to maximize for one thing. I'd want to have stat A, and out of all those stats see what other node I should pick for stat B.
Describe the solution you'd like
For example, say I pick bleed DPS from the dropdown and PoB calculates all the nodes and colors them appropriately. Then, I'd like to be able to pick a second thing, like say cold damage, I want 'the best' node for, and PoB calculates (out of of the list of bleed dps nodes) which one of them would give me the most cold damage.
This is just an example. It could be life, then armour and then evasion. Or even more than two or three things you want.
In other words, I'd like the power node system not only focus on one thing at a time but consecutively keep narrowing down to include all of the things I want to include in a node.
--
Some suggestions, this could be done manually, as in, let the system calculate the first metric first, then you pick a second one and it calculates again, and so on until you're satisfied.
Or, be able to give your whole priority stack ("Bleed, cold, attack speed" or "Armour, life, life leech") and PoB calculates everything at once. You could do this by 'tagging' what things you want in what order, instead of just picking one thing the node power system should maximize for.
This whole thing could happen by still retaining the drop down, but then when you click one stat, it gets transferred to a different table or list next to it. This list is all of the thing PoB should calculate for.
Describe alternatives you've considered
Right now, I have to use the node power system to see the total of all the nodes that would increase the stat I told the system to maximize for, and then have to pick between all the nodes which one would have most of other things I need manually.
This becomes prohibitively time-expensive if I have more than a single thing I want to maximize for.
Additional context
No response
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
この issue では node power system、その statistic dropdown、node calculations が挙げられていますが、ファイルやテストは示されていません。まず node power UI と計算処理のエントリーポイントを特定し、次に優先度付きメトリクスによって候補をどのように絞り込むか、また完了をどのように検証するかを定義してください。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- lua
- 領域
- desktop
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 28/100