PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Allow node power calculation to consequtively calculate more than one statistic

Abierto
#6,709 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

enhancement
Lenguaje dominante
Lua
Estrellas
5.4k
Forks
2.4k
Merge medio
1 d 12 h
PR fusionados (30 d)
26

Descripción

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

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

El issue menciona el node power system, su statistic dropdown y los node calculations, pero no indica archivos ni tests. Empieza localizando los puntos de entrada de la node power UI y de los cálculos, y luego define cómo las métricas priorizadas reducen los candidatos y cómo debe verificarse la finalización.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
lua
Área
desktop
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
28/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.