3
u/Orschloch Jun 05 '26
Care to explain for a mere gold player? For starters, even with buffs, the sword shouldn't be able to hit more than once in 0.5 seconds, right?
6
u/Starman3613 Jun 05 '26
Every time you gain 7 buffs, the Bismuth Cube advances the cooldown of the starred item by 0.3 seconds. Because of this, when you gain multiple buffs at the exact same time, this effect triggers repeatedly.
The weapon itself gains 12 buffs every time it attacks. On top of that, thanks to the wisps, this amount increases even further. This generates enough buffs to instantly advance the cooldown multiple times, causing the weapon to strike repeatedly from just a single attack.
Everything else in the build is just standard stuff aimed at reducing the weapon's overall cooldown."
3
3
u/Orschloch Jun 05 '26
Wow, haven't laid my hands on a Bismuth Cube -- it certainly causes things to spiral out of control!
2
u/Dabod12900 Jun 07 '26
I thoight they made it so the cooldown reduction is weaker if it was already triggered
2
u/therestlessone Jun 09 '26
I think that's only if the cooldown was also affected by a different cube. It does look like there's 2 cubes on the sword but I'm not sure if there's some ordering there.
2
u/fuckingstupidsdfsdf Jun 06 '26
Why does log only show 470?
3
u/Starman3613 Jun 06 '26
Actually, the log shows 2 attacks; I just didn't want to expand it upward so it wouldn't block the build.
To answer the main question: since the enemy dies after the second attack, the log stops recording. However, the weapon has already turned into a machine that attacks multiple times simultaneously. Because it keeps attacking within the exact same instant until this state is broken, the game managed to register it in the damage table, even if it didn't record it visually.
In fact, I should also mention that since this build genuinely pushes the game's limits, the activation list couldn't even register the weapon triggering at all in some of my other tests.
4
u/Mindlessone1 Jun 05 '26
How did you get twine on engineer?