Update 1.5.5 bug, Unable to kill Mannimarco, Me and NPC underneath the ground

GamerzElite

I created a new Tank Character and start playing game. At 42 level I went for quest Shadow of Sancre Tor, I reached Mannimarco and on 1st attempt he throw me under the earth. All attempt to come back on ground failed then I used /stuck command and respwan near him. 2nd attempt again he throw me under the earth that time I was unable to use stuck command, cause system say I need to wait 1 hour for other stuck command. Restart game using Alt+F4

3rd time I went there try to fight him with ranged weapon and I manage to kill him, but system says I still need to kill him. Server cant register his kill. All 3 NPC are under earth and I talked them they tell me "I have to kill Mannimarco".
What going on with this game. I tried 3 times and still cant go ahead.
And this happened after patch 1.5.5

Video is included:

https://www.youtube.com/watch?v=pkEjfYec2m8

Me and NPC underneath the ground pic below:

sorry for my bad english

Nestor

It's probably related to this

http://forums.elderscrollsonline.com/discussion/140482/falling-through-dolmen-floors-after-1-5-5

GamerzElite

Nestor wrote: »

It's probably related to this

http://forums.elderscrollsonline.com/discussion/140482/falling-through-dolmen-floors-after-1-5-5

But what abt the boss? Killed by me but game reject my kill?

Nebthet78

Not sure why the game is rejecting your kill.... Mine was bugged last night too but I was still able to kill him and proceed.

cristi73eb17_ESO

I have the same problem. After falling through the floor a few times I managed to kill him and nothing happens anymore. Quest still says I have to defeat Mannimarco, but he's no longer there.

rsciw

Guess I was lucky then, did this quest on one of my characters last night, he did fall through the floor to the end but was still able to be killed and it counted.

Thought the floor-drop was a one-time glitch, but it seems it isn't... O_o

stefan.gustavsonb16_ESO

Amazing to see what strange bugs they manage to introduce. I almost wanted to see this one for myself. Almost, but not quite.

tangorn

Just my 2c: it is not only him throwing me underground, but me using teleport strike also does the same thing, moves me next to him but 3 ft deep. Seems like teleporting spells no longer respect collisions there, while seem to work fine outside of daedric realm.

Razzak

tangorn wrote: »

Just my 2c: it is not only him throwing me underground, but me using teleport strike also does the same thing, moves me next to him but 3 ft deep. Seems like teleporting spells no longer respect collisions there, while seem to work fine outside of daedric realm.

That's true. Also his push back or my jump always made me or him go under ground.
I had to alt+F4 twice and then I had to repeat entire quest before I managed it.

MDHORDE

I have attempted and failed this quest 4 times each time logging out to reset the quest. I have killed Mannimarco all 4 times and looted his corpse only for the NPCs assisting me to be stuck underground. Each time after killing and looting his corpse the quest marker is still saying I need to kill Mannimarco. I stay above ground by staying on the outside of the Ring the fight takes place in.

HeX7

I had a similar problem except it was Mannimarco who was underground with just his head sticking out for me to beat on. I killed him, but he was hard to target. It was like whack-a-mole.

Lylith

that's just what this particular battle needed, more difficulties.

Loneshard

This happened to me as well 2 days ago!

okraus

I have the same problem!
I got stuck twice under the floow, alle companions are under the earth, mannimarco teleports around sometimes being swallowed by the ground up to his waist.
Third time i killed him from safe distance. Was hard work with light/heavy staff attacks but the kill does not Count.
Quest ist stuck!!

Please ZOS is it possible that you react only this one time faster then usual? This is a showstopper and cannot wait several weeks until you decide to fix it...

Nebthet78

Patch notes indicate this is suppose to be fixed as of today's update.