Maintenance for the week of September 23:
• PC/Mac: No maintenance – September 23
• Xbox One: NA and EU megaservers for patch maintenance – September 25, 6:00AM EDT (10:00 UTC) - 10:00AM EDT (14:00 UTC)
• PlayStation®4: NA and EU megaservers for patch maintenance – September 25, 6:00AM EDT (10:00 UTC) - 10:00AM EDT (14:00 UTC)
• ESO Website for maintenance – September 26, 7:00AM EDT (11:00 UTC) - 11:00AM EDT (15:00 UTC)
Update 24 and the Dragonhold DLC Game Pack are both now available for testing on the PTS! Experience the amazing conclusion to the Season of the Dragon saga. You can read the full patch notes here: 

Problems with the "Maarselok on his Perch" fight: Shagrath's Shield and inconsistent grounding times

The 4th boss encounter of Lair of Maarselok is "Maarselok on his Perch"; it's the one where you have to prevent hoarvors from reaching Selene and protect the Shagrath's Hosts (green spiders) from the strangler spawns.

How does the spider mechanic actually work?

Every 3 seconds, Selene will summon a new Shagrath's Host (green spider).

Each time a spider climbs all the way up to Maarselok, it gives Maarselok a stack of a debuff named "Spider at Top". This debuff lasts for 10 seconds and is refreshed each time the boss gains a stack. When the boss has gained 5 stacks of the debuff, he is grounded and can be damaged.

If 10s go by without any spiders reaching the boss, the debuff expires and the stacks are reset to zero.

So how do you end up with a 10s gap in the chain of spiders? Well, if you let a hoarvor get to her, it will stun her with an effect aptly named "Boom" that lasts for 7 seconds and no new spiders will spawn during that time. And of course, stranglers can kill spiders.

The stranglers' spit will immediately kill any spider that it targets because it's a 1-shot against the spiders.

What is wrong with this mechanic? Part 1: Shagrath's Shield

I had never bothered to look at this mechanic in detail until we tried to get the Shagrath's Shield achievement, the last achievement from this dungeon that we're missing. At the moment, I feel that this achievement is impossible unless we get incredibly lucky.

Why? Because the stranglers' targeting appears to be random. Sometimes it'll target a player. Sometimes it'll target a spider. And if it targets a spider, that achievement is gone.

No, doing the damage to the stranglers do not make them target you instead of the spider. Here is a clip showing all three DDs hitting the strangler, and the strangler ignoring us, spitting, and killing a spider.

Yes, we tried having DDs slot taunt and taunting the stranglers. No, their spit is still random and does not respect taunt.

Yes, the stranglers can be CC'ed. But with the incredibly high rate of strangler spawns, all it takes is for one strangler to spawn and spit at at a spider before the CC could be placed to lose the achievement. And CC durations are too short--typically on the order of 2s or so--and that's not enough time to burst through 172K health.

With the help of an addon custom-made just for tracking this achievement, I can see exactly how many and when a spider dies. And, ultimately, it comes down to luck. We've had a few lucky phases where no spiders died because the stranglers targeted us. But we've never had three lucky phases in a row.

Again, all it takes is for one strangler to spawn, randomly pick a spider as a target, shoot a single spit, and the achievement is RIP. And all this could happen before players could reasonably react.

What is wrong with this mechanic? Part 2: Inconsistent Groundings

This is something that I've heard from a lot of groups. That the times to ground Maarselok can be inconsistent. Most of the time, he grounds fairly quickly. But sometimes, it seems to drag on forever. We saw this for ourselves during our first clear of this boss on Live. Our first and third phases/groundings were very quick. And the second phase/grounding took 6 times as long.

Now that I understand the mechanic better and know what to look for in the logs, the problem becomes pretty clear. We had incredibly bad luck on that second grounding, where it seemed as if the stranglers had a much greater affinity for the spiders than players. There were three times when we built up 4 stacks on the boss only to lose it due to the unusually high number of spider deaths. We also had one hoarvor stun which exacerbated matters, but that had happened after we had already lost a 4-stack due to spider deaths.

What can be done?

Option 1: Make the stranglers more manageable

Personally, I think the random nature of the strangler spit is one of the biggest problems. If a strangler is being damaged by a player, it should target that player and not target a spider.

The other problem is that a strangler, upon spawning, could choose to immediately target a spider for spit. There isn't a reasonable amount of time for players to react. Adding an initial cooldown to when they could spit at a spider would help.

Option 2: Make spider deaths more forgiving

Relaxing the requirements on the achievement (i.e., changing it from "0 dead spiders" to "no more than X dead spiders"; X=8, maybe?) is probably the most direct fix for the achievement problem. Increasing the 10s reset time would help with the inconsistency problem.

Edited by code65536 on August 23, 2019 1:25PM
PC/NA ― Officer of Nightfighters ― Officer and former GM of The Merchant's Reserve
PC/EU ― Member of WipeKings
@code65536 (NA)
DC – Breton Nightblade – DD/Tank – Snow Oryx   ☙
DC – Dunmer Dragonknight – DD/Tank – Cinder Oryx   ☙
EP – Altmer Sorcerer – DD – Elim Crake
DC – Breton Templar – Healer – Zebulon the Spirit Bear
AD – Bosmer Nightblade – Tank – Higgs Bosmer
DC – Argonian Dragonknight – Tank – Makeş-It-So
DC – Redguard Sorceress – DD – Rallina Oryx
DC – Altmer Nightblade – DD – Joyèd

@code4096 (NA)
DC – Dunmer Nightblade – DD – Raven Oryx   ☙
DC – Argonian Dragonknight – Tank – Takes-All-Blame
DC – Altmer Sorceress – DD – Codegasm

@code65536 (EU)
DC – Breton Nightblade – DD/Tank – Snow Øryx
DC – Imperial Dragonknight – Tank – Codetank
DC – Altmer Sorceress – DD – Stormy Øryx

The Flawless Conqueror  •  Dro-m'Athra Destroyer  •  Tick-Tock Tormentor  •  Voice of Reason  •  Bringer of Light  •  Blackrose Executioner  •  Extinguisher of Flames

Add-Ons: Itemization BrowserLoot LogDeconstruction Junk MarkerRaidificatorPurge TrackervHoF Status PanelAsylum Status PanelDungeon TimerCombat AlertsSmart Looter

Guides: Sunspire MechanicsScalebreaker Dungeon Hard Modes
  • UntilValhalla13
    When I was tanking it yesterday, (I DESPISE this fight, by the way) I just started chaining the hoarvers to me and just running into them to explode them so they don't reach her. We did our best to kill all of the stranglers so that he would land. He usually landed the second the last strangler died, which was not easy.
  • cheifsoap
    Here's what we did to beat it

    Tank - Tank everything that moves (besides stranglers - duh), run in to hoarvers as they spawn, never let their AOE explosion touch selene.
    Healer - You have 2 AOE heals now, place one on the stranglers, and one on selene so the tank can get some of that heal love, besides that; do your thing
    DPS - I think the difference maker was using comet. It hits a lot of stranglers and refills almost instantly. Our DPS the second time was 2 range DPS where before it was 1 melee, 1 range. I think either set up will work but the difference maker was using comet.

    Everyone just needs to do their job and if a hoarver knocks out selene, you basically start over. When the dragon lands, cleave the adds, and if there is 1 big guy up; dps it down once the dragon goes back up on his perch. The tank should never be tanking >1 big guy. Oh and battalion defender helps a lot in that fight may have excessive but the tank is tanking a lot of adds so it'll proc a lot.

    I didn't find the fight particularly difficult once we figured out what we need to change/do differently than our first couple of attempts. I hope the above helps someone
  • Czekoludek
    thank you for this post, now I understand why this achi is so much pain
Sign In or Register to comment.