Sign Up

I want to get information about activities, sales and personal offers

or continue with social networks

twitch google steam reddit discord
Already have an account?

Log In

Remember me Forgot your password?

or continue with social networks

twitch google steam reddit discord
Not a member? Sign up now

Elder Scrolls Online: The Mechanics Of Each Necrom World Boss

Posted: Oct 08, 2023

After years of some players asking for harder Overland content, Necrom released with some tougher world bosses to scratch that itch. There are usually one or two in each zone that stand above the rest when you’re looking for a challenge, but the majority of them in Necrom are pretty tough.

If you’re struggling to find a group, the mechanics can be an additional issue to face. Of course, if you have enough ESO Gold, you’d better equip your character with some good equipment first.

So, let’s take a look at what’s involved for each of them in order of difficulty.

Elder Scrolls Online The Mechanics Of Each Necrom World Boss

Corlys The Chainmaker, Clamorclap Bowl 

The first one is Corlys the Chainmaker.

This world boss starts with two waves of smaller enemies that must be defeated before the boss will even show up. And when he does show up, he spawns with an Argonian Behemoth that attacks with heavy hits and fiery breath. Corlys himself, who hits pretty hard, has chains that can pull you into him and creates a path like AOE where he will roll into you.

In this fight, you should focus on the Behemoth first, while avoiding attacks from Corlys. With the Behemoth gone, you can easily defeat him. I find this to be the easiest and most soloable of the Necrom world bosses.

Valkynaz Dek, Chthon Plaza

Valkynaz Dek is a Dremora who summons enemies to aid him in battle, the most damaging of them being the bow wielders.

When he calls in his ads, there is a momentary delay before he becomes invulnerable to attacks. When this happens, you should focus on the ads until they are gone. Then, he will unshield and you can rinse and repeat. He also occasionally summons lightning cloud AOEs. Avoid them when you can.

This boss is similar to the last one in terms of difficulty. But the rest of the world bosses in Necrom kick up the difficulty quite a bit.

The Prime Cataloger, Libram Cathedral 

Next up is The Prime Cataloger fight, which can be a little chaotic with tons of ads being summoned to a him in battle and damaging whirlwinds of books that circle the room.

You should try to keep his ads to a minimum and avoid the AOEs when you can. At about 75% and 35% Health, he will split into four shaded versions of himself. During these unskippable phases, you want to attack the unshielded copies. You have limited time to do damage before the shield comes back and then another of his copies will drop its shield. When all of his copies are dead, the boss returns and you can focus your damage back on him.

This fight takes much more time to complete because of these phases. And since they can’t be skipped, it guarantees to be a marathon, not a sprint type of fight.

Also Read: Major Changes Coming To Diablo 4 Season 2 - In Depth Community Discussion

Vro-Kuul-Sha, Deepreave Quag

This next one is also very chaotic, leaving little room for error.

Vro-Kuul-Sha is a large Lurker who spits poison, summons Tendrils that deal some fast acting AOE damage, and summons smaller Lurkers to help him in battle.

The best advice here is to keep moving to avoid as many of the AOE as you can and keep the number of ads in the fight to a minimum. There can be a lot going on at one time, but the most important thing is awareness of where not to stand.

Runemaster Xiomara, Runemasters Acropolis

Runemaster Xiomara uses Arcanist abilities, launching runes and teleporting around the room. This boss also creates poison AOEs and has a couple of white worthy mechanics.

Keep in mind that the outside edges of the room will do damage if you venture off the platform. So, when you’re avoiding AOEs, do not leave the ring.

The Runemaster also summons Abyssal Tendrils at your feet and a Shard of Chaos. The Shard of Chaos will shoot projectiles at everyone until it is destroyed. And it deals some hard-hitting damage that seemingly increases the longer the shard is up.

The boss is also completely invulnerable to attack while the shard is up. So, you should focus all of your attention on the two smaller shards to unshield the big one and then focus that center shard to destroy it before you return your attention back to the Runemaster.

If he starts channeling, interrupt him with a shield bash. This can happen even when he is shielded. You’ll see the red lines coming off of him and a green book over his head. 

The phases in this fight can be skippable when there are a ton of people, but I have seen so many groups wipe here from these two mechanics. If you’re watching for both, this fight shouldn’t be too terrible.

The Walking Nightmare, The Nightmare Den

And that leaves us with the most difficult world boss in Necrom.

The Walking Nightmare takes the top spot. This boss is very unforgiving if you’re not paying attention. He summons enemies to aid him in battle and has a tongue attack that pulls you to him. Also, he periodically runs across the room, leaving shock and poison AOEs in his path that you should definitely avoid. 

During battle, some of the ads will channel a shield around the boss that can't be interrupted. As soon as you spot the channeling enemies, turn your attention on them. 

Throughout this fight, you should take out the ads to keep the room chaos down. Keep moving to avoid the AOEs and watch for blocks and interrupts if you're being targeted.


As time goes on and more content comes out, it can get even harder to find a group to complete the bosses. So, I hope that knowing the mechanics helps you to feel better equipped to fight them, especially when you don't have a big group.


Next: Elden Ring 1.10: The 5 Most Powerful Weapons! - Weapon Tier List
Previous: EA FC 24: How To Play The 4321 Meta Formation? - A Complete Guide
Surplus stock:
Connecting to online customer service, please wait.