Snowcloak first boss

[Sove92]

People used to think Twister @ T5 is random too...
it works for me every single time I play it.

I made my post before the 2.41 patch, where the bug in Snow drift was fixed.

[IzumiYuki]

It's not about moving when he is casting. You have to be moving when the snow drift animation actually starts and the damage hits. The actual spell comes about 2-3 seconds after the cast ends. I have been moving during the spell animation itself and not the cast and have successfully avoided getting stacks. I have also been in groups that actually know to move during the animation and not the cast and everyone managed not to get stacks at all.

[Sho86]

It's still random. I've had entire groups moving right after cast goes off and continue to keep moving until the damage hits and we all still get a stack/frozen. Then I have times where I move while cast finishes and do nothing during the animation/damage and not get a stack, and of course other times where I do get a stack.

[dejavutwo]

I just ran a snowcloak to test if moving prevented the debuff by running along the outside of the available arena as soon as the cast bar started until after the debuff appeared, completely disengaging the boss and being fairly far from team mates. I still got hit by every single debuff, so either movement is not a factor or it is bugged even worse than before the patch.

[Fynlar]

Yeah, it still doesn't consistently work for me either.

[Vespar]

Yep, moving didnt work for me either the last few runs Ive tried.

[Ravengeringura]

what i do is when i see snowdrift finish casting, i wait 3 seconds then hit A and S rapidly till it goes off, works 100% of the time for me

[Craiger]

I have tested moving around the whole fight, but still got hit by most of them... And then tried standing still through it another time, and got hit the same amount of times (so not all)

Some runs it works by moving like you have said, and some times it doesn't... To me it seems like it's random from run to run

[Velox]

Ran some tests with this mechanic over the course of 3 separate runs (trying different scenarios) and here are the results I got.
This is all post-fix (supposedly)

On first instance
Stood still from cast until damage taken (as a control)-> stack of debuff
Started running during cast until damage taken -> stack of debuff
Started running after cast until damage taken -> no debuff
Started running before cast until damage taken -> no debuff

On second instance
Stood still from cast until damage taken (as a control)-> stack of debuff
Started running during cast until damage taken -> no debuff
Started running after cast until damage taken -> no debuff
Started running before cast until damage taken -> stack of debuff

On third instance
Stood still from cast until damage taken (as a control)-> stack of debuff
Started running during cast until damage taken -> stack of debuff
Started running after cast until damage taken -> stack of debuff
Started running before cast until damage taken -> stack of debuff

---Analysis---
I know 3 runs is hardly a proper sample, but from what I can tell the only certainty with this mechanic is the control. If you don't move, you will get a stack. As far as anything else goes, it just seems like pure RNG to me. Some fights I go with only 1 or 2 stacks so I think I have it figured out. I try reproducing the result the next run and end up frozen over and over. I honestly have no idea at this point if there is a definitive way to dodge this mechanic.