Allow node power calculation to consequtively calculate more than one statistic

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

L’issue mentionne le node power system, son statistic dropdown et les node calculations, mais aucun fichier ni test. Commencez par localiser les points d’entrée de la node power UI et des calculs, puis définissez comment les métriques prioritaires réduisent le nombre de candidats et comment vérifier que le travail est terminé.