|
Post by Kitsunenotsume on Jun 23, 2018 0:37:33 GMT -5
Kitara, James, Emmanuel, and Rhistel were in the ruins. We were handling the dwellers well enough, but suddenly one round we had a massive stack of incoming damage on both Kitara and James (who were in the front line) and got wiped when we encountered the following attack-spam in the span of a single combat flurry. (Note that Rhistel makes two attacks at the beginning but does not get to the next attack flurry in the entire length of the spam) We had no ability to react before both of us had gone from nearly full HP to dead, and the other two members of our party folded soon after as one was light armor melee facing 4 Dwellers solo, and the other had their client lock up due to lag from the spam. I honestly have no idea where it came from, but it seemed almost like the attacks from one of the dwellers had 'built up' due to a pathing problem or the like (as can happen with Parry riposte opportunities with a shorter ranged weapon) and just leveled them into us all at once. Attachments:
|
|
|
Post by Psionic-Entity on Jun 23, 2018 8:05:27 GMT -5
What kind of dweller made the attacks?
|
|
|
Post by Kitsunenotsume on Jun 23, 2018 10:42:51 GMT -5
Melee. I did not identify the particular weapon, but it was not the variety that spams the slam-attack.
|
|
|
Post by Psionic-Entity on Jun 23, 2018 11:24:05 GMT -5
They all spam some kind of attack with an animation. I think the acid VFX only appears on weapons during one of their activated abilities.
|
|
|
Post by Kitsunenotsume on Jul 20, 2018 23:23:43 GMT -5
It seems to be the Bruisers causing the problems. One is from Rhistel being hit by himself. The other two are from the *same* spam. It literally overflowed the combat log.
|
|
|
Post by Kitsunenotsume on Jul 20, 2018 23:25:25 GMT -5
And the Vanguard have their own situation of doing similarly: It is worth noting that Allison is using an SMG, in that all the hits occurred between one flurry and the next. Attachments:
|
|
|
Post by Psionic-Entity on Jul 21, 2018 10:54:54 GMT -5
Initially I thought this was some kind of engine bug with block or something but it kind of looks like it's from one of the scripted attacks instead. I'll add a couple things to address this next update, and I'll also bump something related to the dungeon once I've gone over the puzzles and clues again.
|
|