Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Add detailed source breakdowns for Effective DPS and damage conversion/extra damage

Aberta
  • Algo errado?
#10,326 4 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
42/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
lua
Domínio
desktop

Direção de pesquisa

Comece localizando as decomposições de fontes existentes de “Total Increased” e “Total More” referenciadas na issue e rastreie como suas entradas são montadas e exibidas. Compare esse caminho com os cálculos de Effective DPS, damage conversion e extra damage; considera-se concluído quando cada stat solicitado expõe suas fontes contribuintes individuais e o total resultante, com cobertura para os casos de exemplo descritos.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement
Check for duplicates
  • I've checked for duplicate open and closed issues by using the search function of the issue tracker
What platform are you running Path of Building on?

Windows

Is your feature request related to a problem?

I would like to see more detailed but there is only final value.

Describe the solution you'd like

I would like to see more detailed breakdowns for the following stats:

  • Effective DPS modifiers
  • “X Damage Converted to Y Damage”
  • “Gain X as Extra Y Damage”

For these stats, it would be very helpful if PoB could show every individual source contributing to the final value, similar to how “Total Increased” and “Total More” currently display their individual sources.

For example, when looking at a build, it can sometimes be very difficult to figure out where a particular Effective DPS value or damage conversion/extra damage value is coming from. Having a detailed breakdown of each source would make it much easier to understand and troubleshoot a build.

Ideally, each of these stats would show something like:

  • Source A: +X%
  • Source B: +Y%
  • Source C: +Z%

and then the resulting total.

This would make it much easier to identify how PoB arrives at the final numbers, especially for complex builds.

Describe alternatives you've considered

No response

Additional context

Example:

Enemy resistance 50%
Effective resistance:
13% (non-inverted hit after penetration) ... <- source ?
-87% （inverted hit after penetration)
= -2%

Effective DPS modifier:
x 1.02 (resistance) <- source ?
x1.16 (increased/reduced damage taken) <-source ?
=1.183

Enemy modifiers
Value Stat Skill types Notes Source
10% increased Damage Taken Spell Condition:Unnerved Base <- source ?

If the source could be listed directly, it would save a lot of time. Otherwise, it can take quite a while to track down where it comes from.

Linguagem predominante
Lua
Estrelas
5.5k
Forks
2.4k
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de PathOfBuildingCommunity/PathOfBuilding

Todas as issues de PathOfBuildingCommunity/PathOfBuilding

Issues semelhantes

Mais issues de Lua

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.