PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Effective Max DoT Taken Similar to Max Hit Taken

Abierto
#6,741 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?

It would be good to have some measure of how tanky a build is to DoTs of various damage types. This of course depends on damage mitigation, life pool, life recovery, and potentially flasks, or maybe even dot duration.

Describe the solution you'd like

I'm not sure about the exact best way to do this. There are various factors at play here.

The simplest way would be to just use the damage mitigation and life recovery to calculate it. However, dots like bleeds, poisons, and corrupting blood have durations. So we are (in those cases) more interested in whether the character can outlast the duration rather than whether the character's regen is enough to completely mitigate the damage. Then there are also other kinds of DoTs:

  • Ground Effects, which have infinite duration but can be avoided by not standing on them. Here we would care about how quickly they kill you. If it takes long enough then you have time to react.
  • Ailment DoTs. Here we would want to factor in that you can get immunity in various forms (either outright or with flasks), but these also have a duration so you just need to survive long enough.
  • I'm not sure how the other in game dots would split into categories. Perhaps easiest is just a general dot of each damage type (assuming some equivalent exists in game which is not covered in the previous categories). An example is that builds with Doryani's Prototype should show as highly vulnerable to lightning DoTs.

Here are some options:

  1. Calculate the highest dot dps for which the character would survive for X seconds, where X is either hardcoded based on in game DoT durations, or it can be set in PoB settings.
  2. Calculate how long the character can survive an X dps DoT of a certain damage type, where X is either hardcoded based on in game DoT values, or it can be set in PoB settings.
  3. Have a long list of common DoTs with their common damage ranges and/or durations and essentially calculate if the character can survive them for each one.

There may be better solutions I haven't considered.

I think this would be a good way to give people more info about how tanky a build feels, and to have people prioritise recovery a bit more. I understand this is a huge feature, but I haven't seen anyone else put the suggestion on GitHub yet and I have heard people talking about the idea so I wanted to suggest it here.

Describe alternatives you've considered

See above.

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

No se nombran archivos, pruebas ni puntos de entrada. Empieza por localizar el cálculo existente de Max Hit Taken y, después, revisa cómo se representan la mitigación del daño, la recuperación, las duraciones de DoT, las dolencias y los efectos de suelo; para darlo por terminado sería necesario acordar un diseño de supervivencia frente a DoT y realizar la validación correspondiente.

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

Evaluación

Stack tecnológico
lua
Área
game-dev
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.