Maintenance for the week of November 25:
• [COMPLETE] Xbox: NA and EU megaservers for maintenance – November 27, 6:00AM EST (11:00 UTC) - 9:00AM EST (14:00 UTC)
• [COMPLETE] PlayStation®: NA and EU megaservers for maintenance – November 27, 6:00AM EST (11:00 UTC) - 9:00AM EST (14:00 UTC)
• [COMPLETE] Xbox: NA and EU megaservers for maintenance – November 27, 6:00AM EST (11:00 UTC) - 9:00AM EST (14:00 UTC)
• [COMPLETE] PlayStation®: NA and EU megaservers for maintenance – November 27, 6:00AM EST (11:00 UTC) - 9:00AM EST (14:00 UTC)
Dreadsail Reef - Lylanar and Turlassil Hard Mode Fire/Frostbrand Bug
soulreaper1213
✭✭✭
There is an issue with a mechanic in Dreadsail Reef on the first boss: Lylanar and Turlassil after activating the challenge banner.
The mechanic in question is the firebrand and frostbrand mechanic. When both bosses are down, they will choose 2 people to have brands (1 frostbrand and 1 firebrand) which will explode after a short duration. To avoid deaths to this mechanic's explosion the players who are picked are supposed to stack on a player with the opposite brand color to mitigate the damage. On hard mode this mechanic changes to pick 4 people (2 frostbrands and 2 firebrands) and in addition to this, on brand explosion there is an additional straight line, aimable AOE that shoots out of each players' brand explosion. Crisp Flurry is the white straight-line AOE that shoots out of frostbrand (as pictured below) and Pyretic Wake is the straight-line AOE that shoots our of the firebrand, but in a red color.
Before Firesong patch, you stacked on someone with the opposite brand, aimed your Crisp Flurry/Pyretic Wake AOE to not shoot towards your team members, and blocked the explosion of the brand. Nobody died if done correctly. After Firesong patch, no matter how early and correctly people play out this mechanic, people are dying at random, no sense of logic or cadence to the deaths. Very rarely, all 4 players will live. Much more commonly at least 1-2 players will die and sometimes all 4 players die. Looking at death recaps of these players we realize that the Crisp Flurry and Pyretic Wake from the 2 players are killing either their stacking partner or even themself.
Either before the patch, the damage done by Crisp Flurry and Pyretic Wake to players marked with brand was negligible, or the AOEs just never hit people within the stack. We have tried stacking in a different manner, in which both players with brands intentionally not have their character model stacked directly on one another so their Crisp Flurry or Pyretic Wake wouldn't hit their stack partner, but just enough so the players don't die to the brand explosion not being stacked. In this case, players died to their own Crisp Flurry or Pyretic Wake, not from their stacking partner, nor from the other 2 players with brands.
This bug is making simple progression of the fight exponentially harder and progression of the trial's trifecta near impossible, as it is now to be expected that every brand someone dies. I wish I had more information to give, but since logging the fights are currently bugged I cannot provide anything more.
The mechanic in question is the firebrand and frostbrand mechanic. When both bosses are down, they will choose 2 people to have brands (1 frostbrand and 1 firebrand) which will explode after a short duration. To avoid deaths to this mechanic's explosion the players who are picked are supposed to stack on a player with the opposite brand color to mitigate the damage. On hard mode this mechanic changes to pick 4 people (2 frostbrands and 2 firebrands) and in addition to this, on brand explosion there is an additional straight line, aimable AOE that shoots out of each players' brand explosion. Crisp Flurry is the white straight-line AOE that shoots out of frostbrand (as pictured below) and Pyretic Wake is the straight-line AOE that shoots our of the firebrand, but in a red color.
Before Firesong patch, you stacked on someone with the opposite brand, aimed your Crisp Flurry/Pyretic Wake AOE to not shoot towards your team members, and blocked the explosion of the brand. Nobody died if done correctly. After Firesong patch, no matter how early and correctly people play out this mechanic, people are dying at random, no sense of logic or cadence to the deaths. Very rarely, all 4 players will live. Much more commonly at least 1-2 players will die and sometimes all 4 players die. Looking at death recaps of these players we realize that the Crisp Flurry and Pyretic Wake from the 2 players are killing either their stacking partner or even themself.
Either before the patch, the damage done by Crisp Flurry and Pyretic Wake to players marked with brand was negligible, or the AOEs just never hit people within the stack. We have tried stacking in a different manner, in which both players with brands intentionally not have their character model stacked directly on one another so their Crisp Flurry or Pyretic Wake wouldn't hit their stack partner, but just enough so the players don't die to the brand explosion not being stacked. In this case, players died to their own Crisp Flurry or Pyretic Wake, not from their stacking partner, nor from the other 2 players with brands.
This bug is making simple progression of the fight exponentially harder and progression of the trial's trifecta near impossible, as it is now to be expected that every brand someone dies. I wish I had more information to give, but since logging the fights are currently bugged I cannot provide anything more.
4
-
WrathOfInnos✭✭✭✭✭
✭✭✭✭✭Apparently you can just dodge roll before the brand goes off to avoid the extra damage. I wouldn't hold my breath for a quick fix, but it is still doable without deaths.0 -
minxina✭✭Happened to us too. Executed perfectly stacking mechanic still kills randomly.
Could we get this acknowledged and fixed please?0 -
ZOS_KevinCommunity ManagerHi all, thanks for letting us know about this. The team is aware of this bug and is working on a fix. When we have a fix ready, we'll update everyone regarding this.Community Manager for ZeniMax Online Studio and Elder Scrolls OnlineDev Tracker | Service Alerts | ESO Twitter1 -
ESO_Nightingale✭✭✭✭✭
✭✭✭✭Hi all, thanks for letting us know about this. The team is aware of this bug and is working on a fix. When we have a fix ready, we'll update everyone regarding this.
hey kevin, regarding Dreadsail Reef bugs, is the team aware of warden's shalks not registering on tideborn taleria unless the player dips their toes into the pool in the middle? this has been reported multiple times and i don't believe i've seen if the team has acknowledged it or not.PvE Frost Warden Main and teacher for ESO-U. Frost Warden PvE Build Article: https://eso-u.com/articles/nightingales_warden_dps_guide__frost_knight. Come Join the ESO Frost Discord to discuss everything frost!: https://discord.gg/5PT3rQX0 -
WrathOfInnos✭✭✭✭✭
✭✭✭✭✭
@Trenia don't worry too much about this bug. It's almost like a fun new mechanic where you have to stack, then dodge roll away. It shouldn't cause any real problems.
Now the other bugs will cause some issues. The new block bug has been killing a lot of tanks. Crashes have been terrible. I also think that shalks missing Taleria is more impactful than the brand bug, as it has basically removed 1/6 DPS classes from the newest trial for half a year.Edited by WrathOfInnos on November 8, 2022 7:14AM1 -
Matherios✭✭✭Hi all, thanks for letting us know about this. The team is aware of this bug and is working on a fix. When we have a fix ready, we'll update everyone regarding this.
Hey kevin you should also look into the invisible flare line. Some people sometimes don't get the line and they don't know where they have to turn so they avoid sniping people.
https://www.youtube.com/watch?v=rq3Crx7swTQ 0 -
What_In_Tarnation✭✭✭✭Hi all, thanks for letting us know about this. The team is aware of this bug and is working on a fix. When we have a fix ready, we'll update everyone regarding this.
Hello, Kevin. There're some avoidable attacks by roll dodge seems not working properly sometimes in trials as well. Things like heavy attack from Boss, crashing waves..e.t.c will still hit you even in roll dodge animation. And afaik this isn't only happened in DSR but also in some other scenario.Edited by What_In_Tarnation on November 10, 2022 1:20AM1 -
GreenDay✭✭please tell me when the problems with vDSR with the block and logs and so on will be fixed. why wasn't it fixed in the first week? why should players suffer from your own mistakes that you don't even want to fix.
why fix it: fixed an issue where petting a certain cow could give you meat, leather, or guts. It doesn’t work that way.
aren't there more serious problems in this game?3 -
Treeshka✭✭✭✭✭
✭I believe as a work around players who stack each other can roll dodge just before explosion and sometimes you survive. But this bug is very annoying and crippling groups. Because as a group we die nothing in this boss except this bugged mechanic and it is very frustrating to see that. I hope this gets fixed for next incremental patch.0 -
Skvysh✭✭✭I believe as a work around players who stack each other can roll dodge just before explosion and sometimes you survive. But this bug is very annoying and crippling groups. Because as a group we die nothing in this boss except this bugged mechanic and it is very frustrating to see that. I hope this gets fixed for next incremental patch.
I assume when we die while dodging, we die to brand + line from the other person (at least that's the only "logical" explanation).
Which means that not only do we need to position lines away from the group (with lines being invisible about 25% of the time and barely visible when they do show up), we also need to make sure that each person's line also won't hit the other person they're stacking with.
Or, you know, they could've fixed it in the first incremental patch, but instead we're stuck with this fun new change in mechanic for at least one more week, if we're lucky.1 -
WrathOfInnos✭✭✭✭✭
✭✭✭✭✭@FantasticFreddie No word on when it will be. Apparently the devs are struggling to reproduce the issue. Strange because it occurs 100% of the time to all players that have been in HM this patch. Maybe that's their way of saying "working as intended".Edited by WrathOfInnos on November 22, 2022 1:43AM1 -
Xairvaiss✭✭✭According to how many bugs they introduced since last patch, Im pretty sure it will be fixed in best case at January of 2023...1
-
guarstompemoji✭✭✭✭I heard that the devs were unable to replicate it? Seeking clarification. @ZOS_GinaBruno @ZOS_GinaBruno are the devs testing it on hm?
Wish to know, thank you.0 -
Matherios✭✭✭There is no way they can't reproduce it . [snip]
[edited for minor bashing]Edited by ZOS_Icy on December 5, 2022 7:01PM0 -
BahometZ✭✭✭✭✭
✭It's not possible to make it happen, it just randomly happens, So they would have to just spend some time in the trial.Pact Magplar - Max CP (NA XB)0 -
WrathOfInnos✭✭✭✭✭
✭✭✭✭✭It's not possible to make it happen, it just randomly happens, So they would have to just spend some time in the trial.
It "randomly" happens every single time the brand mechanic occurs in hard mode.
Before the bug would stack the brands and live. Now you stack the brands and always die. If you stack the brands and dodge at the last second you can live.
Not a huge deal, we did Swashbuckler over the weekend despite this issue, just annoying to see it ignored/denied.0 -
p00tx✭✭✭✭✭
✭✭It's not possible to make it happen, it just randomly happens, So they would have to just spend some time in the trial.
It happens reliably every single flare in hardmode, as long as you don't try to mitigate it with roll-dodge or Barrier.PC/Xbox NA Mindmender|Swashbuckler Supreme|Planes Breaker|Dawnbringer|Godslayer|Immortal Redeemer|Gryphon Heart|Tick-tock Tormentor|Dro-m'Athra Destroyer|Stormproof|Grand Overlord|Grand Mastercrafter|Master Grappler|Tamriel Hero0 -
guarstompemoji✭✭✭✭Even if they do not have a team who can do so (they should, for playtesting purposes), then they should be able to make the fight skip to that point for testing, and so on, via some command sequence.
Hoping to get an answer. I don't like rumors, so yeah, hoping.
This is/was their flagship, and latest and greatest when it comes to this content.0 -
FantasticFreddie✭✭✭✭✭
✭✭✭guarstompemoji wrote: »Even if they do not have a team who can do so (they should, for playtesting purposes), then they should be able to make the fight skip to that point for testing, and so on, via some command sequence.
Hoping to get an answer. I don't like rumors, so yeah, hoping.
This is/was their flagship, and latest and greatest when it comes to this content.
If they can't reliably recreate a bug that happens to everyone else 100% of the time, the only thing I can think of is they simply don't have a trial team that can get to that point.
Maybe the bug doesn't happen if you skip certain phases of the fight, or play it in the dev God mode, who knows.
Not us, because zos won't answer, le sigh.1 -
Anne13✭✭✭✭guarstompemoji wrote: »Hearing accounts that this may be fixed. Good luck, everyone!
From where? Just on PC?
0 -
code65536✭✭✭✭✭
✭✭✭✭✭It's fixed. My understanding is that an adjustment was made, but it was omitted from the patch notes because there was uncertainty about whether it would work. Based on my experiences yesterday, it was indeed fixed by the Monday morning PC patch.Edited by code65536 on December 6, 2022 10:11AMNightfighters ― PC/NA and PC/EU
Dungeons and Trials:Personal best scores:- Dragonstar Arena: 46817 (NA)
- Maelstrom Arena: 600526 (NA)
- Blackrose Prison: 99274 (EU) (Unchained)
- Maw of Lorkhaj: 165227 (EU)
- Halls of Fabrication: 220708 (NA) (Tick-Tock Tormentor #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12)
- Asylum Sanctorium: 114957 (NA) (Immortal Redeemer #1, #2, #3, #4, #5, #6, #7, #8, #9, #10)
- Cloudrest: 131256 (NA) (Gryphon Heart #1, #2, #3, #4, #5, #6, #7)
- Sunspire: 250866 (EU) (Godslayer #1, #2, #3, #4, #5, #6, #7)
- Kyne's Aegis: 235841 (EU) (Dawnbringer #1, #2, #3, #4, #5, #6, #7, #8)
Dungeon trifectas:- Mountain God and Leave No Bone Unbroken
- Apex Predator and Pure Lunacy
- Depths Defier and Relentless Raider
- Defanged the Devourer and Nature's Wrath
- In Defiance of Death and No Rest for the Wicked
- Bane of Thorns and True Genius
- Ardent Bibliophile and Subterranean Smasher
- Battlespire's Best and Bastion Breaker
- Zero Regrets and Land, Air, and Sea Supremacy
- Fist of Tava and Invader's Bane
- Curator's Champion (Valinna) and Temporal Tempest
- Unshakeable Fervor and Lighting the Embers
Extended Journal Add-Ons: Item Set Browser ― Loot Log ― Character Knowledge ― Collectibles Tracker ― RaidificatorOther Add-Ons: Combat Alerts ― Deconstruction Junk Marker ― Purge Tracker ― Asylum Status Panel ― Smart Looter ― Improved Companion Rapport Information0 -
Matherios✭✭✭It's fixed. My understanding is that an adjustment was made, but it was omitted from the patch notes because there was uncertainty about whether it would work. Based on my experiences yesterday, it was indeed fixed by the Monday morning PC patch.
Ty for reporting about it , hopefully next time they can say what they fix on patch notes and what not.0
