I want an answer directly from a dev as to why this bug was more important than ANY of the others listed here? Bug after bug and patch after patch all we seem to get are seemingly useless updates. There’s no point in having working tool tips when the skills hardly work in the first place right?(yes I know tool tips are most likely handles by a different department but it’s a wasted effort on broken skills) Please tell me as to why this bug was more important to fix then let’s say the iWarden bug that is literally game breaking(I haven’t used focus since that bug appeared since it is unreliable). I’m really wanting to try and understand your bug fixing logic and you saying “The iWarden bug is not that simple to fix” is not a valid reason, it is a game breaking bug where as iLeap was not a game breaking bug.
I’m really wanting to try and understand your bug fixing logic and you saying "The iWarden bug is not that simple to fix" is not a valid reason, it is a game breaking bug where as iLeap was not a game breaking bug.
That’s it, non-game breaking bugs are easier to fix than real game breaking bugs... :S *stares back at a Illusionary Warden staring at him* :P
I’m really wanting to try and understand your bug fixing logic and you saying “The iWarden bug is not that simple to fix” is not a valid reason, it is a game breaking bug where as iLeap was not a game breaking bug.
That’s it, non-game breaking bugs are easier to fix than real game breaking bugs… :S stares back at a Illusionary Warden staring at him :P
Hmm so this non-game breaking bug took them since the launch of gw2 to fix? I don’t buy it being easy to fix if it takes them that long to fix it.
lol. agree fully.
done with this thread and class….and not looking back.
whether it’s being short-staffed, incompetent, or having bizarre QA priorities, it is a real shame you’ve failed this class and its players so woefully.
Chaos Organ (Ele), Pistol Opera (Thief), Modular Man (Eng)
MARA (EU) Gunnar’s Hold
Illusionary Leap: Fixed a bug that allowed players to swap places with their clone after it was destroyed.
Wait this was a bug? really? Now not only does it not work half the time now I can’t even swap to it just after it dies… great thanks anet.
Is this for real?
Can you make our Warden not reflect/destroy projectiles anymore while you’re at it? It would be way more consistent than what we currently have.
Also give Blink a 10s self-immobilize upon cast, as it would at least give us a visual cue of our inability to move after blinking.
I mean, sorry about the harsh critique, but you guys have failed to make this profession feel reliable so many times already that many of us have already lost faith.
While we’re not really expecting bugfixes anymore, having a feature removed (and flagged as a bugfix) only adds insult to injury.
Hmm so this non-game breaking bug took them since the launch of gw2 to fix? I don’t buy it being easy to fix if it takes them that long to fix it.
I was just making a joke there by the way :P
Yea I know I just felt like pointing out the obvious since people miss it.
Hehe, I got it. But yeah, too many bugs that really need to be fixed but it looks like the only ones they come up with are small ones or not-needed fixes. :S
There’s a range where the red bar is gone, but the skill fails. Last but not least, I believe that swapping mechanics have been altered, as it often fails to swap and resets the clones position from the target closer to you.
Extra prediction: as we know from Arcane Thievery, the “underwater Mimic bug” should appear for the third time in the next patch notes.
Mimic: Fixed a bug that caused the underwater channel for this skill to be shorter than the land channel.
The least they could’ve done before fixing this “bug” is to make sure the skill actually worked correctly in the first place…
Which it hasn’t. For a long time.
And apparently it’s even more buggy now. Does it count as a new bug to add to the (increasingly long) list if the skill was already bugged beforehand? Or does their fixing of a supposed bug in exchange for creating a new bug somehow cancel both out? ._.
Every patch I excitedly scroll down to the Mesmer bug fixes. Every patch I’m disappointed. Seriously…this is getting more and more ridiculous. Necromancers got a long list of changes while the most bugged class has the smallest list? Why?
Wow at all these people still here hoping for fixes. It’s 2 years since release and nothing changed, they never ever given a crap about fixing the game and never will. At this point I don’t know if you’re really unflinching or just plain stupid. Stop supporting them and quit this kittening game.
Anet…please…fire this hambow warrior, who keeps nerfing mesmers… I know,…there is not much left…but find a mesmer to lead mesmer balance team….its just to ridiculous.
It seems that he (dev) still lose to some mesmers. Even with his huge passive heal and Usain Bolt speed. Maybe it’s time to help a little warriors and put one stealth skill on his bow.
Until then fix more skills on mesmer. I still burst warr for 10k so look at “arcane thievery”, sometimes take stability first.
Nerf izerk too, sometimes die after mesmer.
Don’t forget about torch, that OP PU, it seems that has no delay to use.
On a serious note (for WvW only):
- too many passive skills;
- too easy to reset a fight after heavy damage dealt (only for roaming);
- “hard revive” and rally mechanic needs some changes.
No trinity made heavy classes with healing and running abilities a must in zerg.
You tried to balance other classes but with little luck (huge life for necro).
I don’t miss holy trinity but your wvw become boring.
nope they all play war thief,engi. i ve seen only 1 anet tag with a mes in pve and when i whispered him he confirmed that mes was in a bad state with all the bugs. how about toolfixes and further nerfs actually fixing the bugs in this very thread? who cares about mimic?do we even use it on regular bases?noooo we dont! we use iwarden though and blick and aaaaaal the things mentioned here
Lv 80 glamour Mesmer Triforce Mesmerpower PU mes,Lv 80 power necro
[AVTR]
Isle of Kickaspenwood
One good thing about all these Mesmer bugs is I’ve begun to spend a lot more time outside and not on the computer playing Guild Wars 2 or buying anything from the gem store, ever, because I have no intention of sending money to a publisher in the process of milking their cash cow until it “kitten” bleeds.
There’s a range where the red bar is gone, but the skill fails. Last but not least, I believe that swapping mechanics have been altered, as it often fails to swap and resets the clones position from the target closer to you.
Three patches later, still happens. Range indicator is misleading and can lead to no Leap clone when displayed as in range, Swap fails to swap with clone. Pathing is as bad as before.
Dont worry, the next tooltip refinement patch will add “this skill has a random chance to do nothing at all” to most of our skills. Everything will match its tooltip and so is “bugfixed”.
Dont worry, the next tooltip refinement patch will add “this skill has a random chance to do nothing at all” to most of our skills. Everything will match its tooltip and so is “bugfixed”.
If they’re fixing tooltips then I’m surprised we haven’t got a change to Focus 4 – ‘Applies a boon which looks like Swiftness but isn’t, because Swiftness stacks duration’.
I keep getting that shared cool down bug, usually when using portal. Anyone have any tips for avoiding this? Has kittened me over in some frustrating ways.
Meh. This game really needs one “balance” dev per class. By “per class,” I mean actually plays; if not mains each class. Then, we might finally see some of this bug-cyclopedia bleeding dealt with.
Malegryne (Sylvari Mesmer), Lannka (Asura Thief) – Ferguson’s Crossing: [PRD/BRB/OMFG]
Other 80s: Any but Warrior
If you do not, it remains an eye sore and scares off new people who see classes with lots of broken mechanics, the community which is frustrated if not infuriated, and the total lack of communication from developers (and ubiquitous miscommunication when they do communicate).
There is just one thing which would actually solve the situation: fix these bugs and keep the community informed. Unfortunately, this option is not really an option as it requires work which has never had place in the plan.
Meh. This game really needs one “balance” dev per class. By “per class,” I mean actually plays; if not mains each class. Then, we might finally see some of this bug-cyclopedia bleeding dealt with.
This game is called “Guild Wars”, not “Guild Mess”. Go figure
Not giving up on this class. Anet shouldn’t either but signs point to a sad place.
Please don’t force folks to go GWEN.
too late. i really really really loved my mesmer. before all the massive nerfs and bugs i couldnt wit to log onto my mesmer. it was fun in wvw, pve and spvp. i felt viable in every game mode. now with all these bugs and sooo many nerf i feel useless in wvw which is my favorite gme mode. no aoe nothing work the way its supposed to and instead of fixing just 1 single bug just 1…they nerf ileap…..speechless……
so yeah i have given up on this class and only play necro now, at least i get lootbags and kills and not just veilveilveilbot boredom. i think anet only sees the 1v1 mes and balances according to that, thats why they done even notice all the bug that mainly wvw players experience.
i miss my mes though but with these bugs its simply unplayable and i barely log in nowadays…just dailies…and log out.
Lv 80 glamour Mesmer Triforce Mesmerpower PU mes,Lv 80 power necro
[AVTR]
Isle of Kickaspenwood
Played mes since headstart, and played both PvE and PvP since then (with breaks). It’s kind of at the point, PvP-wise, where I’m not 100% confident the skills I press will do the things I need them to do.
Though I suppose a good portion of mesmer traits have a randomness factor, anyway..
(Staff 2 still occasionally gets you stuck in random walls, esp. in Legacy of the Foefire. You then have to either relog or pray that your blink/Phase Retreat will port you back outside. Previously iLeap was a pretty good bandaid-fix for that – you could target something outside the wall, throw out a clone, and port out of the wall.)
I’m not sure if this has been posted in the bug list but from where i have looked i haven’t seen it.
IWarden with Illusionist Celerity trait will not give cooldown reduction.
Not the case – iWarden with Illusionist’s Celerity properly shows the reduced recharge reduction to 20s in the tooltip and reflects it when cast (default is 25s).
However, if both Warden’s Feedback and Illusionist’s Celerity are taken, the tooltip incorrectly states a 20s recharge, but exhibits the correct double reduced recharge upon cast.
I’m concerned the devs won’t even bother looking at this thread and use this as an excuse:
3. Do not post more than one bug per thread: lists of bugs are not very helpful to us because we’re frequently sending thread links to specific people who may not be able to address the other bugs you’re reporting. Please make a separate thread for each bug you’re seeing. [edit] This is with the exception of a staff request for bugs to be consolidated.
This is under the sticky on how to report bugs. If I’m mistaken let me know and I’ll delete this reply. But at the moment there is so much other stuff in here besides just a plan bug report.
I’m concerned the devs won’t even bother looking at this thread and use this as an excuse:
3. Do not post more than one bug per thread: lists of bugs are not very helpful to us because we’re frequently sending thread links to specific people who may not be able to address the other bugs you’re reporting. Please make a separate thread for each bug you’re seeing. [edit] This is with the exception of a staff request for bugs to be consolidated.
This is under the sticky on how to report bugs. If I’m mistaken let me know and I’ll delete this reply. But at the moment there is so much other stuff in here besides just a plan bug report.
You may be right, perhaps this is why the devs ignore us. What shall we do now? Make 40+ new threads here?
I’m concerned the devs won’t even bother looking at this thread and use this as an excuse:
3. Do not post more than one bug per thread: lists of bugs are not very helpful to us because we’re frequently sending thread links to specific people who may not be able to address the other bugs you’re reporting. Please make a separate thread for each bug you’re seeing. [edit] This is with the exception of a staff request for bugs to be consolidated.
This is under the sticky on how to report bugs. If I’m mistaken let me know and I’ll delete this reply. But at the moment there is so much other stuff in here besides just a plan bug report.
You may be right, perhaps this is why the devs ignore us. What shall we do now? Make 40+ new threads here?
The devs stopped noticing the thread for two reasons:
It has too much offtopic grumpiness. Yes, there’s a reason for it, which is: no appropriate dev attention to these problems. That’s a vicious circle. When we got that attention, we appreciated it, remained pretty constructive and waited patiently for our fixes; when the one person who seemed to care left, we were left with even more miscommunication, unfixed bugs, new bugs and ninja-nerfs – so no wonder we’re a bit upset here, right?
They have their own view on our class and on our bugs, while they also have a large queue of bugs, little time dedicated to actually fixing things, and a skewed priority system (iLeap “fix” vs unbugged iWarden). This is made worse by the fact that they can’t (or are strongly not willing to as it is not cost-efficient in their view) fix the underlying mechanics of the engine which cause bugs like pathing issues, broken blinks and getting permanently stuck in place.
Having an extensive properly formatted list of fully documented bugs with examples and suggestions from the community is useful for any developer, provided that a) it has all the necessary information regarding the bug and/or b) has links to specific posts, videos, threads; “naked” lists which purely say that bugs exist are not really helpful indeed. Proper lists may also let the person dealing with a specific bug notice something in an adjacent bug what was actually the key to solving the problem. This also serves as a good argument in assigning more time to a specific class if a coder wants to get it from his uppers. New bugs, though, should still get separate threads regardless for ANet’s forum combers to easily register.
However, since I’ve personally lost faith in this idea after a certain incident with a piece of my feedback, I’m not eager to run this list anymore. Again, if anyone feels like s/he can update the list to its current ~30-40 form with proper formatting, grammar, forum/youtube links etc. and make it into a new thread, I would be happy to “move” there.
I absolutely agree. This thread has gotten way off topic with people just complaining about lack of changes in every release notes.
If we are to get anything done, I think we need to just start again with a clean slate that clearly identifies all the known bugs and perhaps runs a poll (straw-poll will do) to establish a community driven priority list. This would go a long way to helping the devs identify which bugs are the most game breaking to us.
