Champion Magus/Paragon
80 Elementalist of [APeX]
So i was looking at the updated patch notes (https://forum-en.gw2archive.eu/forum/professions/balance/Feature-Build-Balance-Preview/page/16#post3667926) and i saw the proposed addition of a red circle to meteor shower. I main Elementalist, the skill ceiling for this class is very hgh right now, but for real… A red circle on meteor shower… you must be trying to kill Ele… I’d like this forum post to be a “petition” against the proposed change, throw your backing behind it if you care about your local staff Elementalist.
Thanks!
It needed a circle IMO. I don’t think it’s absurd nor out of line with every other aoe skill in the game.
It’s a bit of a shame in that it makes it a lot easier for enemies to figure out where to stand to avoid it, but I don’t think losing a few kills on confused zerglings is that big a deal.
As much as I’d like to say “no”, I have to agree with the red circle change.
It should follow the rules that the other aoe skills follow.
Random exceptions like meteor shower are detrimental.
Id be down for a change to circles for individual meteors, but the whole thing? Come on…
That’s silly. That doesn’t follow in line with any other skill.
I know you’re upset but it’s just logical.
It is probably the nail in the coffin for glass staff in pvp, though. But it did need a circle. Glass staff just needs something else.
I agree, it’s really needed. Whether you play elementalist or not, it doesn’t give the player time to react until they realize they’re being hit by 5k~15k Metoeor Shower crits in pvp/wvw.
In a way it may be better with the circle showing if its the big version its becomes a fear trick for ele. It only shows where they could be coming down and it may not hit you at all but would you risk running though it. You can play mind games with it. For the most part meteor shower not going to hit ppl that often unless they need to stay in it or simply do not see it coming. If you where going to miss your still going to miss even if there was no circle.
I agree, it’s really needed. Whether you play elementalist or not, it doesn’t give the player time to react until they realize they’re being hit by 5k~15k Metoeor Shower crits in pvp/wvw.
1) Don’t zerg (in WvW).
2) 3,5s of casting animation, interruptable and punish-able (in pvp).
Anything else you’d like to know?
I agree, it’s really needed. Whether you play elementalist or not, it doesn’t give the player time to react until they realize they’re being hit by 5k~15k Metoeor Shower crits in pvp/wvw.
1) Don’t zerg (in WvW).
2) 3,5s of casting animation, interruptable and punish-able (in pvp).Anything else you’d like to know?
How does it feel being that edgy? Does it hurt?
I agree, it’s really needed. Whether you play elementalist or not, it doesn’t give the player time to react until they realize they’re being hit by 5k~15k Metoeor Shower crits in pvp/wvw.
1) Don’t zerg (in WvW).
2) 3,5s of casting animation, interruptable and punish-able (in pvp).Anything else you’d like to know?
Am I supposed to laugh or what?
Oh please, I’d like to go to your PVP world where Staff Eles would free cast in the middle of a cap point where everybody can see them instead of positioning himself someplace where he won’t be interrupted during that 3.5 secs. Or do you play that way? Go inside a cap point and start casting Meteor Shower where your enemies can stop you with 1 CC or even get instagibbed by thieves?
P.S. I don’t even join zergs anymore. I just go to WvW to solo/2~5 man roam with friends.
I’m more upset with the fact one person cried about this and got an instant dev response than the actualy change. It feels so degrading to always be ignored when you present ele issues, whereas a single complaint from the recieving end gets adressed straight away…
The red circle is required. As others have stated meteor shower currently does not follow the rule of every other AoE spell in the game and there is no reason for it. There are indeed a lot of spells on staff that need some work but making another spell like meteor shower cheesy as some sort of compensation is not the solution.
If you think everyone will then run out of it has not really realized how BIG that circle is and how many AoE circles are there during a fight. In fact I’d be happy if they would all run out of it because that would be like a 360 radius fear bomb.
I agree, it’s really needed. Whether you play elementalist or not, it doesn’t give the player time to react until they realize they’re being hit by 5k~15k Metoeor Shower crits in pvp/wvw.
1) Don’t zerg (in WvW).
2) 3,5s of casting animation, interruptable and punish-able (in pvp).Anything else you’d like to know?
Am I supposed to laugh or what?
Oh please, I’d like to go to your PVP world where Staff Eles would free cast in the middle of a cap point where everybody can see them instead of positioning himself someplace where he won’t be interrupted during that 3.5 secs. Or do you play that way? Go inside a cap point and start casting Meteor Shower where your enemies can stop you with 1 CC or even get instagibbed by thieves?
P.S. I don’t even join zergs anymore. I just go to WvW to solo/2~5 man roam with friends.
I thought it was quite funny… and a great response to your rather obnoxious tone.
The red circles are needed, especially to differentiate friendly MS from the unfriendly version.
Lastly I’ll add use stability if you can’t rip off your MS without getting interrupted. I suspect you know that but since you were playing that card as some sort of defense, I’ll bring it up.
Just for clarification, Meteor Shower is NOT the only AOE spell out there that doesn’t follow this red circle rule, in particular multiple of the mesmer spells don’t like Feedback and Null Field, would be nice to know if feedback is friendly or hostile before i hit myself in the face…
In all fairness yes, it should have a circle, but i bet if we go and complain about any of the other spells missing the red circle, not a kitten will be done about it. That is what most people are frustrated about.
Another thing i find weird is how Anet wants to take time and “balance” every small change they make, but as soon as they found out that this spell was missing a circle, they decided to hit it asap without actually testing it in action which doesn’t seem like the kind of balancing they seem be so fond of.
I think it should have a red circle, I also think that anyone too stupid to move out of the thing even as it is now deserves the swift death it provides.
That is all.
Actually, Null Field does have a red circle. And I don’t know why you think MS shouldn’t function the same as every other AoE skill in the game lol.
Add red circles to all AoEs that lack them. Giving some circles and letting others get by without is broken.
As far as worrying about the nerf as a result of fixing the bug – I would much rather the ele stand on its own than have to rely on a series of bugs to prop it up. Besides, with the size of the ring and the AoE cap, most zergs will likely ignore it anyways.
So i was looking at the updated patch notes (https://forum-en.gw2archive.eu/forum/professions/balance/Feature-Build-Balance-Preview/page/16#post3667926) and i saw the proposed addition of a red circle to meteor shower. I main Elementalist, the skill ceiling for this class is very hgh right now, but for real… A red circle on meteor shower… you must be trying to kill Ele… I’d like this forum post to be a “petition” against the proposed change, throw your backing behind it if you care about your local staff Elementalist.
Thanks!
The devs have done nothing but buff warrior and theif since launch, while nefed ele every single patch.
It depends how long the circle is displayed for. If it’s on the ground for there entire channeling time then Meteor will truely become a PvE only skill.
Well first of all, its going to be a huge kittening circle. Like the size of ACs’. Granted, these circles may be more obvious in PvP, but in WvW in 90% of the situations where Meteor Shower is cast? No one is going to notice a giant circle when they are looking for wells and marks. Maybe over time, people will start looking for the giant red circle, but those people already notice when Meteor Shower starts going anyways.
if it gets small circle for individual meteors, then i can understand. But probably, it will have a big cirlce for possible hits saying that; “Hey player there will be a random damage around this circle for next 8 sec so plan accordingly”. This is far more than a “red circle”.
If it is one GIANT Red Circle where they have no idea where individual meteors will hit, I am OK with that… But if EACH meteor gets a circle…
Meteor Shower doesn’t create one AoE. It creates multiple AoEs within an area. Each one can hit up to 5 enemies.
Each single meteor should get a blast and a circle, just like Comet has. It’s a not a rain of fire. It’s a shower of individual physical meteors.
It’s weird enough they do not have a knockdown like GW1’s Meteor Shower or like Meteor. They should get knockdowns, even if that meant getting a much longer recharge. But if that cant be, at least they should get blasts.
That also applies to the Meteor elementalists get when using a boulder. It should also get a blast and a AoE circle like Comet.
(edited by MithranArkanere.8957)
Every balance patch has some negative impact on the ele. The last one in particular destroyed the build I had been running for months by moving up to the Master tier 2 of the Adept traits I was using.
Meteor Shower is obviously our best staff skill, it was also pretty easy to avoid. Now with a red circles enemies will dodge out before the first meteor even strike. It is a huge buff for people who are fighting a staff ele, as it makes our best spell even easier to avoid.
In 1 vs 1 we were already almost an hopeless case, now its just getting worse.
Anet is better to have a noticeable buff to damage or functionality (instant drop of first meteor as the red circle appears?) to compensate for this, because between the lack of new content, lack of GvG and a broken class (RTL over 50% nerf, Mist-Form healing removed, and now this?), I’m just gonna move to the next big MMO.
I’m more upset with the fact one person cried about this and got an instant dev response than the actualy change. It feels so degrading to always be ignored when you present ele issues, whereas a single complaint from the recieving end gets adressed straight away…
I totally share that feeling.
(edited by Xillllix.3485)
I’m more upset with the fact one person cried about this and got an instant dev response than the actualy change. It feels so degrading to always be ignored when you present ele issues, whereas a single complaint from the recieving end gets adressed straight away…
This is probably the strangest fact about the announced change. The bug forum is bursting full with far more important issues and THIS gets fixed? If they did (miraculously) solve all the other issues as well I would not say anything, but how likely is that?
I’m more upset with the fact one person cried about this and got an instant dev response than the actualy change. It feels so degrading to always be ignored when you present ele issues, whereas a single complaint from the recieving end gets adressed straight away…
This is probably the strangest fact about the announced change. The bug forum is bursting full with far more important issues and THIS gets fixed? If they did (miraculously) solve all the other issues as well I would not say anything, but how likely is that?
Bugs have different priority levels and ease of repair. I’ve fixed low priority bugs that were simple fixes because they were exactly that — simple. I’ve also postponed high priority bugs that were incredibly difficult to fix.
From the original forum post, it seems that this was a simple scripting error which didn’t require any changes to the code base. That would make it something trivial to repair.
I wouldn’t look much deeper than that regarding why this is getting fixed so soon over other bugs. In fairness they have fixed issues nearly every patch. They are getting thru it, although slowly.
I’m more upset with the fact one person cried about this and got an instant dev response than the actualy change. It feels so degrading to always be ignored when you present ele issues, whereas a single complaint from the recieving end gets adressed straight away…
This is probably the strangest fact about the announced change. The bug forum is bursting full with far more important issues and THIS gets fixed? If they did (miraculously) solve all the other issues as well I would not say anything, but how likely is that?
Bugs have different priority levels and ease of repair. I’ve fixed low priority bugs that were simple fixes because they were exactly that — simple. I’ve also postponed high priority bugs that were incredibly difficult to fix.
From the original forum post, it seems that this was a simple scripting error which didn’t require any changes to the code base. That would make it something trivial to repair.
I wouldn’t look much deeper than that regarding why this is getting fixed so soon over other bugs. In fairness they have fixed issues nearly every patch. They are getting thru it, although slowly.
True, i’v myself have done that a lot, but that doesn’t explain why the other spells don’t get fixed that has the same problem.
I’m more upset with the fact one person cried about this and got an instant dev response than the actualy change. It feels so degrading to always be ignored when you present ele issues, whereas a single complaint from the recieving end gets adressed straight away…
This is probably the strangest fact about the announced change. The bug forum is bursting full with far more important issues and THIS gets fixed? If they did (miraculously) solve all the other issues as well I would not say anything, but how likely is that?
Bugs have different priority levels and ease of repair. I’ve fixed low priority bugs that were simple fixes because they were exactly that — simple. I’ve also postponed high priority bugs that were incredibly difficult to fix.
From the original forum post, it seems that this was a simple scripting error which didn’t require any changes to the code base. That would make it something trivial to repair.
I wouldn’t look much deeper than that regarding why this is getting fixed so soon over other bugs. In fairness they have fixed issues nearly every patch. They are getting thru it, although slowly.
True, i’v myself have done that a lot, but that doesn’t explain why the other spells don’t get fixed that has the same problem.
I had my hopes up for those fixes when I saw the “fake” balance patch notes (congratulation to whoever did those, everything the ele needed). Now all hope is gone, we will probably get some other unnoticeable buffs, hidden trait nerfs sold as buffs and this huge nerf to our best skill (as everyone will just dodge out of the huge circle now).
True, i’v myself have done that a lot, but that doesn’t explain why the other spells don’t get fixed that has the same problem.
That depends on what the problem is. It is quite possible that the fix for Meteor Shower ends up adding proper circles to every AoE in the game.
I’m more upset with the fact one person cried about this and got an instant dev response than the actualy change. It feels so degrading to always be ignored when you present ele issues, whereas a single complaint from the recieving end gets adressed straight away…
Welcome to the world of thiefs.
Not affiliated with ArenaNet or NCSOFT. No support is provided.
All assets, page layout, visual style belong to ArenaNet and are used solely to replicate the original design and preserve the original look and feel.
Contact /u/e-scrape-artist on reddit if you encounter a bug.