Still ICD on F1-F4 after 11 months?
icd is for preventing players to make multiple shaters at 1 set of clones so its not bug and dont in any way make our game harder….
icd is for preventing players to make multiple shaters at 1 set of clones so its not bug and dont in any way make our game harder….
i know why its here and the reason why it was introduced was to wait for F3-F1 shatter fix bug and then they were supposed to remove icd. Devs themselves said this will be gone when bug is fixed. Now it seems everyone including devs forgot/don’t care.
https://forum-en.gw2archive.eu/forum/pvp/pvp/25-Cooldown-on-Shatters/first#post1142800
here’s a link. this was supposed to be a “temporary bandaid until they can figure out the problem”, half a year later~~~~~~~~~~~~~
Do you remember berserker’s bug? well.
Do you remember berserker’s bug? well.
i sure do lol and if it wasn’t everyone on this forum asking for a fix for MONTHS i don’t think lazynet would’ve done anything. this bug is completely ignored by the community, i don’t think i saw a single thread about it in 4+ months. I bet most are like the first guy who posted on this thread, think its there for balance issues lol
How long is the ICD?
How long is the ICD?
it doesn’t matter how long it is, its there until fix arrives. been months, no fix was ever mentioned so leave it broken and move on?
Do you remember berserker’s bug? well.
i sure do lol and if it wasn’t everyone on this forum asking for a fix for MONTHS i don’t think lazynet would’ve done anything. this bug is completely ignored by the community, i don’t think i saw a single thread about it in 4+ months. I bet most are like the first guy who posted on this thread, think its there for balance issues lol
Well, the thread you linked is in the pvp section. I guess a lot of people dont read it.
Im not sure if its the only reply from devs but they usually dont like to post here, and this is another poor decision.
I can tell you that i never saw that thread before but im glad you linked it. Many mesmers will do the same until we know whats going on.
here’s the original thread which lead to the spvp one i previously posted.
https://forum-en.gw2archive.eu/forum/professions/mesmer/Thoughts-about-the-new-update/first
I love these two comments which were posted SIX MONTHS AGO.
ensoriki says “possibly a temporary fix until they can eliminate the source bug, but that might take awhile”
Lightofshados responds “By “a while” you mean 2015 obviously because fixing old content and bugs is definately not a priority”
This is exactly what’s happening right now and people are happy with monthly jumping puzzle additions
Yes, page 3. I must missed this one.
Maybe a lot of us did not saw that replies or just think its fine the way it is? Even if its not an hour it hurts to read that they wanted to fix it.
Yes, page 3. I must missed this one.
Maybe a lot of us did not saw that replies or just think its fine the way it is? Even if its not an hour it hurts to read that they wanted to fix it.
the reason i made this thread. i knew people would come with their sarcastic bs “How long is the ICD” but what they don’t understand is that it doesn’t matter. This was supposed to be fixed and fixed long time ago. Nothing been done and they let it broken like dozens of other skills/traits in this game.
Yes, page 3. I must missed this one.
Maybe a lot of us did not saw that replies or just think its fine the way it is? Even if its not an hour it hurts to read that they wanted to fix it.the reason i made this thread. i knew people would come with their sarcastic bs “How long is the ICD” but what they don’t understand is that it doesn’t matter. This was supposed to be fixed and fixed long time ago. Nothing been done and they let it broken like dozens of other skills/traits in this game.
I was sincerely asking. No sarcasm.
But really thank u for bringing up the topic. I was not aware of this.
If you got no experience programming, “temporary” means “permanent” in regards to workarounds and bugfixes. Source: work.
If you got no experience programming, “temporary” means “permanent” in regards to workarounds and bugfixes. Source: work.
temporary like izerker.
Don’t mind Nuka, he/she isn’t the most polite individual.
The ICD is 0.25 and really doesn’t bother me. I agree with the principle, that if you say you’ll fix something then you should. But I can also see why it’s not a priority.
Yes, page 3. I must missed this one.
Maybe a lot of us did not saw that replies or just think its fine the way it is? Even if its not an hour it hurts to read that they wanted to fix it.the reason i made this thread. i knew people would come with their sarcastic bs “How long is the ICD” but what they don’t understand is that it doesn’t matter. This was supposed to be fixed and fixed long time ago. Nothing been done and they let it broken like dozens of other skills/traits in this game.
How long it has been in place is irrelevant. How badly is it affecting players, and is it worse than other things that need a developer’s time?
If the answers are “not affecting many player’s ability to play mesmers” and “not as bad as other issues”, then it will not be prioritized, regardless of how long it has been in place.
Yes, page 3. I must missed this one.
Maybe a lot of us did not saw that replies or just think its fine the way it is? Even if its not an hour it hurts to read that they wanted to fix it.the reason i made this thread. i knew people would come with their sarcastic bs “How long is the ICD” but what they don’t understand is that it doesn’t matter. This was supposed to be fixed and fixed long time ago. Nothing been done and they let it broken like dozens of other skills/traits in this game.
How long it has been in place is irrelevant. How badly is it affecting players, and is it worse than other things that need a developer’s time?
If the answers are “not affecting many player’s ability to play mesmers” and “not as bad as other issues”, then it will not be prioritized, regardless of how long it has been in place.
Not prioritized/ That’s cool n all but its been half a year? Things not on their priority list supposed to be fixed in weeks, months or years? Will this be fixed by 2015!? All i hear lately is “its not in our priority list” then what is? Shallow new content instead of hundreds of bugs in this game? Makes sense.
(edited by Nuka Cola.8520)
You have to pick your fights — why are you picking this one over other unfixed problems?
imho, this doesn’t impact anyone as you can’t make more clones to shatter faster than 0.25s — unless you are concerned that the self-shatter trait is kitten with a 0.25s delay on jamming your F-keys. Even if that’s the case, it’s hardly impacting anyone. I’m being generous here as “hardly” is an overstatement at best.
If the answers are “not affecting many player’s ability to play mesmers” and “not as bad as other issues”, then it will not be prioritized, regardless of how long it has been in place.
Not prioritized/ That’s cool n all but its been half a year? Things not on their priority list supposed to be fixed in weeks, months or years? Will this be fixed by 2015!? All i hear lately is “its in our priority list” then what is? Shallow new content instead of hundreds of bugs in this game? Makes sense.
[/quote]
While indeed annoying, so long as other more pressing issues keep coming up and being added (higher!) to the remaining list of things to do, it won’t ever come far enough down to fix this issue.
Which is just how software development works. FIFO doesn’t really work out at all, so you have to do something like this.
It’s somewhat annoying but not nearly as much as the GS auto attack bug when it keeps getting obstructed at a way smaller height difference than it should.
You have to pick your fights — why are you picking this one over other unfixed problems?
imho, this doesn’t impact anyone as you can’t make more clones to shatter faster than 0.25s — unless you are concerned that the self-shatter trait is kitten with a 0.25s delay on jamming your F-keys. Even if that’s the case, it’s hardly impacting anyone. I’m being generous here as “hardly” is an overstatement at best.
im not picking fights, just stating one of the dozen bugs we currently have and certainly one of those most people forgot about. hell, some even thought its supposed to be like that…
(edited by Nuka Cola.8520)
Whats so bad about a 0.25 second cooldown?
Neer have i ever attempted a shatter which dient activate because of that vooldown. What reason do you possibly have to use shatters so quickly in a row?
Warning: link may contain traces of awesome.
Lyssa’s Grimoire – a guide every Mesmer should read.
Whats so bad about a 0.25 second cooldown?
Neer have i ever attempted a shatter which dient activate because of that vooldown. What reason do you possibly have to use shatters so quickly in a row?
To finish off a target quicker? But that’s not really the point. If devs came out and officially stated that .25sec will stay permanent to improve balance then that’s fine and time to move on, what annoys me is that they haven’t addressed the issue in six months.
How exactly does a 0.25 second cooldown “improve balance”?
How much does it really bother you that it takes 0.25 seconds longer to finish off a target quicker?
The exploit was that people had multiple shatter effects on a single illusion. They added a 0.25 second cooldown to prevent that.
The issue seems fixed to me.
Warning: link may contain traces of awesome.
Lyssa’s Grimoire – a guide every Mesmer should read.
How exactly does a 0.25 second cooldown “improve balance”?
How much does it really bother you that it takes 0.25 seconds longer to finish off a target quicker?The exploit was that people had multiple shatter effects on a single illusion. They added a 0.25 second cooldown to prevent that.
The issue seems fixed to me.
did you read the tread i posted? devs themselves said its a bandaid until they find out the bug. What if i want to F1-F3-F2 on someone? That’s clearly more than 0.25 of a delay but close to a second. How it prevents balance? i have no idea, its first people on this thread who’ve said so and i believe that’s what many think.
Actually that’s a 0,5s delay if you go through three shatters.
Doesn’t shatter affect all active clones? Why is this cooldown an issue then?
It creates an issue when using IP. The trick (the other one besides the exploit) was to string shatters together in order to daze the target so your MW+CoF could hit without them using skills to evade and add extra damage and confusion to the attack from IP.
What’s better? A spike that does 12K and allows the opponent to evade/interrupt your other skills/counterattack, or a spike that does 12K plus adds 2 stacks of confusion and dazes/interrupts the target?
Dissentient [DIS] ~Tarnished Coast