Very confused about what happened when I swapped badges. Visual bug or something else?
8N8
Member Posts: 164
Hello all,
I am hoping someone can help me out with an explanation for this, I'm a little confused about something that happened when I was swapping badges. Although I do not have the original screenshot, Daryl's attack was at 4970 with the following badge setup:
I then swapped out the bottom right rare damage increase an epic damage reduction badge, and darlys damage dropped down into the 4400s. After having put the original badge back on that was there in the first place, his damage only returned to what it is currently, 4773.
Why didn't his damage return back to 4970? What am I missing, that replacing a badge back to the original badge didn't bring attack damage to 4970?
As I am writing this now, I now see that replacing survivors refreshes everything back to normal I guess? Can someone let me know what's going on?
TLDR;
Here's a video of the whole thing. Keep an eye on Daryl's damage output. He starts at 4970. What I did was en-equip and then re-equip the same exact badge. His damage output falls below the point it should be (4773). [If I had continued on with the mission, would his damage had stayed the same?] Instead I replace Anthony with Glenn, and the damage output stays the same (even though Daryl has a badge that increases his attack with a hunter teammate. It should have dropped. But since it was already down, maybe it stayed the same to adjust). When I put Anthony back in, it jumps back up to 4970. What is going on?
I am hoping someone can help me out with an explanation for this, I'm a little confused about something that happened when I was swapping badges. Although I do not have the original screenshot, Daryl's attack was at 4970 with the following badge setup:
I then swapped out the bottom right rare damage increase an epic damage reduction badge, and darlys damage dropped down into the 4400s. After having put the original badge back on that was there in the first place, his damage only returned to what it is currently, 4773.
Why didn't his damage return back to 4970? What am I missing, that replacing a badge back to the original badge didn't bring attack damage to 4970?
As I am writing this now, I now see that replacing survivors refreshes everything back to normal I guess? Can someone let me know what's going on?
TLDR;
Here's a video of the whole thing. Keep an eye on Daryl's damage output. He starts at 4970. What I did was en-equip and then re-equip the same exact badge. His damage output falls below the point it should be (4773). [If I had continued on with the mission, would his damage had stayed the same?] Instead I replace Anthony with Glenn, and the damage output stays the same (even though Daryl has a badge that increases his attack with a hunter teammate. It should have dropped. But since it was already down, maybe it stayed the same to adjust). When I put Anthony back in, it jumps back up to 4970. What is going on?
0
Comments
(survivor_damage*(1+hero+marksman)+Weapon_damage*(1+lethal)+Flatbadge)*(1+badge%)
Just by looking at the video, it's most likely due to Abe's leadership trait and layering.
The easiest way is to add/remove badges without anyone in the lead. I'm not going to run the numbers but this is just based on what I see.
Please note that unless the survivors are in the mission screen the stats will not update or show the correct value.
Feeling Lost, Click Here!
I'm not able to give 100% certainty for this issue, but in the vast majority of cases where players ask about stat changes, it ends up being a combination of leader traits and in/out of team conditions that cause the visual inconsistencies. My guess that this is the case here, as well. I'm confident that if you do your badge swaps outside of team selection, or with characters that are not part of your last-used team, you will see consistency with the numbers.
In any case, our apologies for the confusion.
Please note: Development is a fluid process, and suggestions and implementation take time and iteration. Any discussion of future features, deadlines, updates, balance changes, and such should be considered prospective and subject to change.