I just DC’d at the end of an Arah solo. Lost the instance as usual. No change from before.
Did the stability change lead to any mobs having their skills modified? I haven’t noticed any.
What about just dumping it all on the TP during time gates?
There is a workaround: use a ranged, targeted weapon such as guardian scepter or ele staff (fire). It looks to me like the hitbox has been made smaller and moved to the top of the dragon’s head so that melee can’t hit it. Plus, his head moves around like crazy so you need a skill that is targeted.
Not a great solution, but it works. You can still kill it in two cycles if you use the timewarp that kasmeer(?) drops for you.
Got a trading post express from daily today. It doesn’t stack with my older ones.
I just checked it. Ranged single-target projectile skills work. But the really interesting thing is that you can see they put the hitbox at the dragon’s head (your projectiles fly in that direction).
So :
- Skills at ground level don’t hit (for example melee skills and longer range skills hug the ground like ele fire dagger 1).
- The dragon’s head (and thus hitbox moves around wildly so if you’re using an untargeted skill, it’s practically impossible to get a hit.
It’s a pretty big fail because this means you’re severely restricted in what weapons you may use in this encounter.
scepter works great for that fight , seems a shame to have to buy one just for one fight tho. you’d think all weapons would do it.
Hitboxes for structure bosses were messed up in the tuesday patch. But a single target range weapon will automatically aim its projectiles towards the correct spot. This may be why it works?
Still unfixed after 3/20 patch.
It’s been bugged since the March 16 update. Before that there were zero problems hitting the dragon.
The same issue has affected other structure bosses as well, I believe.
Just take a break until it’s fixed.
To put it simply: You’re not wrong but what you’re talking about has no relevance.
There was never a problem for smaller groups to take on larger groups. This is because with Stability in it’s old form, stacking duration, it gave smaller groups mobility. Mobility meant they could avoid spike damage (Wells) and soft CCs (chills, cripples) and setup their own spike damage. They didn’t need to remove stability from an equal sized or larger group to do this as stripping stability with boons, being that it’s the last boon to be removed, is near impossible without some massive strip like Corrupt Boon (single target) so most people didn’t try.
So your argument that it allows smaller groups to remove stability from larger groups is irrelevant since it was never needed or desired.
NOW…on the reverse side blobs, or massive groups, have an extreme advantage with the changes because where it was impossible for them to really strip stability off before (again, boons being stacked up and Stability last to go) their larger number of players leads to a larger amount of CC which will easily strip Stability off. Simply % wise a larger blob will always have more CC than a smaller group. This CC, when coordinated, can be dropped on player’s heads so there’s simply no avoiding them thus stripping Stability incredibly fast. So now now only does the smaller group have to content with the large amount of soft CC, but they also have vastly higher hard CCs that will eventually catch and separate them leaving them vulnerable to spike damage and they die very fast.
This is why blobs are encouraged by this change. More numbers = more CCs and the more CCs you got the less reliable enemy Stability will be. The less reliable enemy Stability is the more likely hood they will get caught in a CC and killed with spike damage.
This. It’s significantly easier for a blob to stunlock smaller guild groups now. Losing blobs vs guild groups play will be a loss of a big part of WvW and will lead to lots of skilled groups quitting.
…party DCs gave a 1 minute grace period to log back in before your instance is destroyed?
Too much to ask, I suppose.
- Mobs that are not optional have a barrier to prevent you from progressing if you go further. No barrier means they are optional.
- Don’t join a speed run group and complain about it if you don’t want to do a speed run.
WoR sploit works fine.
it’s better to have WoR exploit than the fix, which is certainly going to be unblockable, unreflectable attacks.
For instance, more people watched the last League of Legends world finals online than watched the American Superbowl.
If you read the articles, they say more people streamed the LoL finals than streamed the superbowl. Which is a very misleading comparison considering the superbowl is on free TV.
From his past post history and pretty clear lack of WvW exposure, his absence is not surprising.
Thanks Lord Kuru
I wonder what the developers could have been planning when they tampered with Belka.
Just checked: Belka’s burning is now 588 per tick; 1/2 of the 1176 that it used to be (from gw2dungeons).
Actually on the site it lists the total damage, not damage per tick.
Yes, of course. My bad. Then maybe it’s the condition damage issue? (But I scrolled as far as I could in my combat log and the burnings were all for 588 per tick.. maybe it’s missing ticks?).
“When it’s ready” are just words to cover slow or non-existent development.
Thanks Lord Kuru
I wonder what the developers could have been planning when they tampered with Belka.
Just checked: Belka’s burning is now 588 per tick; 1/2 of the 1176 that it used to be (from gw2dungeons).
…in particular the dragon’s shadow in the last LS chapter (99% of attacks don’t register in combat log and don’t hit). I believe the same issue occurs in the ice fractal.
Sinister trinkets such as Wynne’s Locket are not available to players who don’t have Season 2 of the Living Story unlocked. This means they must buy Season 2 (with gems) for the gear. Now players can certainly buy gems with gold, but one wonders:
Will this also be a feature of HoT?
Has anyone noticed anything odd about Belka? It feels like her damage has been significantly reduced.
Having fought her solo several times each week since October, I have a pretty decent idea when I’d need to run away from her – and after the patch I barely had to. There’s no change in my clumsy skills and rotations. The difference is quite noticeable.
On a side note, it feels like Brie’s death ray has been reverted, or maybe I just did better at sidestepping… although on the patch day I got hit by her every time she charged it up.
Funny, I’ve had the same experience at Belka. As for Brie, I don’t believe it’s been reverted.
I’d say chances are, the reversion of downscaling is unintended. They seem to have a lot of trouble with version control: we often see old fixed bugs return in later patches.
But then we would have issues with enemy mob stat scaling instead of ours
Change them all to 80 (or 82 or whatever) once and never have to bother with it again.
Perhaps dungeons should be all level 80 where sub-80 players are upscaled.
This would cater to what’s probably the vast majority of dungeon runners and would solve the problem of the terrible downscaling algorithms foisted upon us from time to time.
In theory, you should be banned. In reality, you’re 99.99% safe from any form of punishment.
Hmm that comment about the end of CoF sounds interesting. Not in that I care about CoF
, it’s more that maybe they changed something about objects, especially ones like that, which resulted in strange hit boxes…so maybe that happened to the Elemental in Snowblind and it is just a bug! I can hope right?
Same issue with the last dragon fight in the last chapter of the LS. It’s a structure also, and people are also having a hard time getting hits on it (as in 99% of attacks do not record a hit).
Not a true solution, but certainly better than nothing (Anet’s solution):
Have a PPT score as we do now… but also have a secondary PPT score just for EB. This way, a server that’s in a horribly unbalanced matchup can rally together with an attainable goal (be competitive in the EB mini-matchup), helping server morale and reducing player attrition.
this patch is only going to promote guilds and blobs to run pirateship meta besides that guilds that run 20ish numbers or below wont be able to take on the 30-60 zergs anymore
If the ability to do this is lost (guild group vs pugs) simply because of the ability for the bigger group to CC spam, then a lot of guilds are going to quit the game.
Perhaps the nausea is from bigger field of view causing the lower FPS everyone’s having. That means when you rotate, things are more jumpy.
In appearance, this looks very much like the tower upgrade bug WvW has been having for a while now (maybe a year?) where the upgrade shows a full bar but nothing is actually being upgraded.
Anyone know a workaround for the mystery cave dragon issue? (dragon doesn’t take damage 99% of the time during damage phase)
Yeah i did think Brie’s ray changed. It looked like it tracked me today when i sidestepped. Although im not entirely sure. Been kind of distracted with the new camera and have a habit of zooming so far out that i cant see tells properly.
Yeah.. it could be that it tracks you differently from before instead of being wider, but the animation is exactly the same as yesterday… so maybe it’s now like Belka’s bugged ball of death.
I’m pretty sure Brie’s death ray (Arah p2) is significantly wider than it was yesterday.
In the mystery cave, damage phase.
Why stop at three almost identical faces? They should have done 100 new almost identical faces and heavily advertised “100 new faces!!”
I need to do the achievement myself this week, so I’ll test it then. I know the boss bugs out occasionally and has done so since it first got released – sounds like you’re experiencing an existing (and annoying) bug.
Oh.. didn’t know about the bug…. I’ve restarted the instance but am still getting it. Not cool.
I think this was the case beforehand. I know my ele had huge issues wih aoe targeting damage on him. In the end I gave up and did single target stuff
I was doing the exact same instance yesterday (going for achievement) and had zero problems with icebow. The difference is enormous, from massive damage yesterday to almost none today.
Could be that it’s not icebow, but I can’t really check at the moment because quitting the instsance means going through all those horrid unskippable cutscenes when I do want to try again.
Was doing the “Kill the shadow of the dragon” in the final LS chapter…
icebow #4 on the shadow of the dragon in the damage phase does little to no damage. I tried it multiple times. Anyone checked icebow on other “structure” bosses?
Edit: looks like dragon is bugged sometimes (was working perfectly yesterday for me).
(edited by Lord Kuru.3685)
Couldn’t Anet make it so you can only drop rams in a “X” radius of gates in the first place? other siege would be harder but at least other siege wouldn’t be completely useless
As has been said countless times before, flame rams have other uses than just smacking gates. If you want to limit how players use siege, then just do like siegerazer, smack a tower, ring pops up, you wait to ‘cap’ the ring and then siege appears, build it, ram a gate. Yet some people are going to think this would be a good idea too >.<
Kindly tell us what other use a flame ram has, please?
Lords room on the lord for the iron hide buff.
You said it yourself, you’ve reported people and nothing has come of it. The “hated one” is still around after griefing people for three(!) years. I think it’s pretty safe to say that Anet isn’t going to act.
It’s happening because with the new BL, map completion will be impossible since you can’t get to the old BL.
The EoTM map that was introduced was, in my opinion, a disaster turned Ktrain that no self respecting WvW player enjoyed. Even now, it remains a Ktain map that guilds only go to when regular WvW is quiet to farm linen from players.
It makes me sad that this is the direction WvW is going in. I know that many of the current WvW players of the game feel as i do and WvW testers would not allow this mode to go through alpha without major changes or objections so my question remains, Where were the WvW testers when this mode was in development?
You do realize that EotM was publicly beta tested, right? Maybe you should do some more fact-checking before you make assertions or complaints.
You do realize he never claimed EotM wasn’t publicly beta tested, right? Maybe you should read more carefully before you make assertions or complaints.
They clearly are just developing whatever they want with no regard for player input, hence the string of fails from skyhammer to bloodlusts ruins to EotM. So there’s no need for testers.
For example if you get kicked at end you would still get 80%-90% of the rewards. This could also be extended to solos so that you would get 500% rewards if you solo.
Good idea in theory, but I don’t see any chance they would actually increase rewards for doing dungeons with fewer than 5 people.
If you give a way to remove siege, the trolls will remove your legit siege. Whether siege is legit or not is easy for a human to determine but hard to automate. The only way to stop this behavior is banning people.
Now if supply-drain griefing were ever acted upon, that’d be something.
You can get offenders temp-banned but you do so at the price of your forum posting rights.
I’m proof of that :/
how do you know they got temp-banned?
As I understand it, it’s getting in fashion to have alternate accounts for retaliation purposes (they order guards during an attack and you drop 6 of their omegas off a cliff, for example). Definitely not a good thing as this can easily get out of hand… but players feel like there is no other recourse (which is pretty much true).
Yeah. This is going to be really bad, particularly for catching foes when chasing or fleeing from foes in WvW. It’s a huge nerf for some professions — ones that don’t have much mobility. But Anet doesn’t develop for WvW in mind so, not so surprising.
I’m pretty sure someone’s going to be punished: the OP. You might want to take down the video.
I wonder what the developers could have been planning when they tampered with Belka.
, it’s more that maybe they changed something about objects, especially ones like that, which resulted in strange hit boxes…so maybe that happened to the Elemental in Snowblind and it is just a bug! I can hope right?