[2021] Encounters III - Stone of the Currents (Wharf) Voltage Surge buff bugged

" delasteve wrote: tl;dr Culling the boss with the purple aegis up (Voltage Surge) and 15+ flood orbs spawned results in a failed challenge.

Details:

At 75, 50, and 25% health, the boss will spawn between 4-8 Flood Orbs. Once all 15+ orbs have spawned, I will kite them away to a corner and trap them so they won't die when I cull the boss. The boss will get down to 1hp using Southbound and an Elemental Focus gem. I will run away from the boss to have it's shield go away. I will then run back in to the boss and wait for it to cast the shield again. Once it's cast, I will cast Bane to finish the boss off. This results in a challenge failed.

Extra info:

Having spoken with others who have done the challenge themselves, they've also reported to me that it's RNG based and they didn't change anything in their technique, but after several attempts, it completed.

If necessary, I can post a video or screenshots of my attempts.

Thanks for your report, we're looking into this.

" oestergreen wrote:

" Jatin_GGG wrote:

" delasteve wrote: tl;dr Culling the boss with the purple aegis up (Voltage Surge) and 15+ flood orbs spawned results in a failed challenge.

Details:

At 75, 50, and 25% health, the boss will spawn between 4-8 Flood Orbs. Once all 15+ orbs have spawned, I will kite them away to a corner and trap them so they won't die when I cull the boss. The boss will get down to 1hp using Southbound and an Elemental Focus gem. I will run away from the boss to have it's shield go away. I will then run back in to the boss and wait for it to cast the shield again. Once it's cast, I will cast Bane to finish the boss off. This results in a challenge failed.

Extra info:

Having spoken with others who have done the challenge themselves, they've also reported to me that it's RNG based and they didn't change anything in their technique, but after several attempts, it completed.

If necessary, I can post a video or screenshots of my attempts.

Thanks for your report, we're looking into this.

You responded a month ago and u haven't gotten back? ...

This should have been fixed in patch 3.15.2. If anyone is still having this problem please post a video of it occurring.