Vale Guardian Break Bar
yes
they changed it that it auto drop fast. hence, the no CC technique is no longer works for us.
Death is Energy [DIE] – Gandara EU
Australia
Yes the cast time of Magic Storm was reduced to prevent unintended gameplay. I’ll follow up on our patch note procedure to make sure we don’t miss stuff like this (it should have been there).
Also looks like the note about the checkpoint for players exiting the instance after completing the Bandit pre-event got missed as well and that has also been fixed for what it’s worth.
Thank you for fixing the check point at Sabetha, that was annoying
Thank you for fixing the check point at Sabetha, that was annoying
No more walk of shame or the lines ‘u spawned there cuz too low dps!’
I used to be a power ranger, now not sure anymore
Yes the cast time of Magic Storm was reduced to prevent unintended gameplay.
“Play how we want you to play” isn’kitten ?
Are you also gonna change Gorseval because you can kill him without taking an updraft?
https://www.reddit.com/r/Guildwars2/comments/3vajhn/gorseval_no_glider_challenge/
Fort Aspenwood
What was the unintended gameplay about his breakbar?
What was the unintended gameplay about his breakbar?
If you didn’t interrupt him, you could ignore every other mechanic other than the floor change and the orb attacks he casts while in the break bar.
You can still ignore it, but just for a few seconds now as it will break by itself
How long does it last now? OP said 4-5 seconds, but is that true or just an estimate? I’m trying to decide if it’s better to ignore now or break.
How long does it last now? OP said 4-5 seconds, but is that true or just an estimate? I’m trying to decide if it’s better to ignore now or break.
It should be around 10s.
Yes the cast time of Magic Storm was reduced to prevent unintended gameplay.
“Play how we want you to play” isn’kitten ?
Are you also gonna change Gorseval because you can kill him without taking an updraft?
https://www.reddit.com/r/Guildwars2/comments/3vajhn/gorseval_no_glider_challenge/
It doesn’t have anything to do with allowing you to play the way you want and so I’d like to share some insight into why we made the change.
We’re actually perfectly okay with players not interrupting a break bar. However what we’re not okay with is having all the deadly mechanics of the encounter removed during this period. Honestly that’s really just an oversight on my part in how I built the encounter. This was the most simple change we could make that was relatively low impact.
It doesn’t have anything to do with allowing you to play the way you want and so I’d like to share some insight into why we made the change.
We’re actually perfectly okay with players not interrupting a break bar. However what we’re not okay with is having all the deadly mechanics of the encounter removed during this period. Honestly that’s really just an oversight on my part in how I built the encounter. This was the most simple change we could make that was relatively low impact.
Thank you for being transparent about this. I’m glad you are setting a precedent for fixing unintended gameplay as we know what happens to mechanics when players are allowed to cheese them for extended periods of time (Looks at dungeons).
It doesn’t have anything to do with allowing you to play the way you want and so I’d like to share some insight into why we made the change.
We’re actually perfectly okay with players not interrupting a break bar. However what we’re not okay with is having all the deadly mechanics of the encounter removed during this period. Honestly that’s really just an oversight on my part in how I built the encounter. This was the most simple change we could make that was relatively low impact.
Thank you for being transparent about this. I’m glad you are setting a precedent for fixing unintended gameplay as we know what happens to mechanics when players are allowed to cheese them for extended periods of time (Looks at dungeons).
Agreed. Thank you for this!
Yes the cast time of Magic Storm was reduced to prevent unintended gameplay.
“Play how we want you to play” isn’kitten ?
Are you also gonna change Gorseval because you can kill him without taking an updraft?
https://www.reddit.com/r/Guildwars2/comments/3vajhn/gorseval_no_glider_challenge/
It doesn’t have anything to do with allowing you to play the way you want and so I’d like to share some insight into why we made the change.
We’re actually perfectly okay with players not interrupting a break bar. However what we’re not okay with is having all the deadly mechanics of the encounter removed during this period. Honestly that’s really just an oversight on my part in how I built the encounter. This was the most simple change we could make that was relatively low impact.
If you don’t want people to use his channel as free makeshift DPS phase, why not change it so he still does at LEAST the teleports during the channel, and keep the auto-break at or around 30 seconds? for a good dps phase during that, you have to kite the seekers away (cant use ANY hard CC, except for single target fear (necro DS/RS 3 and knockbacks ranger LB4. you also have to be mindful of mesmer TWs, as slow will do a good amount of damage to his bar), keep up the rotations from each segment of the arena all the while dodging/mitigating the AoE’s damage. Now, with all of that going on, you would also have to worry about teleports AND the potential of having vale in a bad section when he auto-breaks, causing a circle to spawn in a lit up segment of the arena.
Or perhaps give him a stacking buff that grants some form of stronger retal that lasts ONLY during the channel, so you can still get some fair amount of damage off, but you have to be really mindful of you and your teams health.
(edited by Xehanort.7034)
Yes the cast time of Magic Storm was reduced to prevent unintended gameplay.
“Play how we want you to play” isn’kitten ?
Are you also gonna change Gorseval because you can kill him without taking an updraft?
https://www.reddit.com/r/Guildwars2/comments/3vajhn/gorseval_no_glider_challenge/
It doesn’t have anything to do with allowing you to play the way you want and so I’d like to share some insight into why we made the change.
We’re actually perfectly okay with players not interrupting a break bar. However what we’re not okay with is having all the deadly mechanics of the encounter removed during this period. Honestly that’s really just an oversight on my part in how I built the encounter. This was the most simple change we could make that was relatively low impact.
If you don’t want people to use his channel as free makeshift DPS phase, why not change it so he still does at LEAST the teleports during the channel, and keep the auto-break at or around 30 seconds? for a good dps phase during that, you have to kite the seekers away (cant use ANY hard CC, except for single target fear (necro DS/RS 3 and knockbacks ranger LB4. you also have to be mindful of mesmer TWs, as slow will do a good amount of damage to his bar), keep up the rotations from each segment of the arena all the while dodging/mitigating the AoE’s damage. Now, with all of that going on, you would also have to worry about teleports AND the potential of having vale in a bad section when he auto-breaks, causing a circle to spawn in a lit up segment of the arena.
Or perhaps give him a stacking buff that grants some form of stronger retal that lasts ONLY during the channel, so you can still get some fair amount of damage off, but you have to be really mindful of you and your teams health.
Or, you know, they could just deal with the unintended issue instead of makeing the FIRST boss of raids even harder and messier for newcommers.
Seriously, what’s the big deal. It was clear from the start that killing VG while he goes into chill spamm mode was going to get fixed.