Monolith boss fail at level 80 moved my char to level 55 area

After failing Lagon on level 80 after 0.7.9d, I got a load of odd “modifier removed messages” (which need looking at, btw - very confusing/unfinished) and when I went to click on the monolith to restart, I had been moved to the level 55 location.

The level 80 looks ok, with modifiers removed but not set to zero.

Are you referring to the Monolith in Echo of a World? If so, that’s a known bug, sorry about that.

Could you elaborate on what about the “modifiers removed” popup was confusing? When you die in the Monolith, you lose a number of Echoes Conquered and some of the modifiers you had on your run are also removed.

I went and died for the cause!

The messages I get when the modifiers are removed say …

“A long modifier that has been lost exists here”
“this is another mod that has been lost that goes here and is slightly long”
“This is a slightly shorter mod that has been lost”
“This is a fourth mod that has been lost and is particularly long”
“this is a fifth that won’t happen most times!enemies have 169% to shred armour on hit”

Letter for letter what I get (excluding quotes).

They are a little uninformative!

Regarding the reset to 55, my char was taken to the level 55 area, not the Echo of a World.

On this 2nd death in area 80, I am now in Echo of a World.

It sounds like that’s placeholder text, which definitely isn’t happening for most people. How many modifiers did you have before dying?

Please try to repair the game if you’re playing through Steam. If the issue persists, attach your log file. Thanks!

I had 39 Echoes Conquered on 1st death, lost 9.

Had 30 on 2nd death, lost 7. Now at 23.

Will check Steam and relaunch game.

I reset monolith to zero.

Exited game and validated files with steam.

Started mono 80 again from 1, and did around 7 or so (not got 1st quest yet).

I then died and am still getting the same sort of messages.

Log file attached.Player.log (437.9 KB)

Seems to be the same bug Kissingaiur has reported.

We’ve found the cause of this issue and will fix it in 0.7.9e. Thanks for the report!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.