Morgoth doing more than 600 damage in a single round

[Timo Pietilä]

My experience differs from yours -- for me it's not four or five turns. Turn 1 I cast the rune, Morgy doesn't break it. Turn 2 I attack; Morgy doesn't break it (maybe). Turn 3 I attack, Morgy breaks it and I get hurt. Runes are still useful, but only because I can set them up ahead of time; they aren't worth casting in the heat of battle.

I haven't played an arcane caster in awhile, but warriors don't find enough ?Rune to make them worth saving against Morgoth, and priests/paladins in my experience get better mileage from leveraging their cheap heals. Just phase away before healing and Morgy won't get any free attacks on you.

If you use phase, you can use rune as well. You probably have more than one turn time to wait for M to get you, and it only takes one turn to heal and one to cast the rune. One thing I collect when playing priest is restore mana. In 3.2.0 they are plentiful way beyond need, so I usually have very large supply of those before last fight.

[Timo Pietilä]

I was not advocating removing the earthquake effect, I was suggesting that the crush damage be reduced to 200 from 300 so that the maximum damage that a player can take in a single turn would be reduced to 600 or so, which is I think what most of us have been assuming it to be up until now.

I have a benefit of being old-timer with knowledge that Morgoth can do 800 or so damage in melee. It was actually much more common in old days, because pushing player to other grid didn't stop Morgoth attacks there. It always got all four in even if you changed place twice during the combat.

And clearly you do not need to be in a GV or something for this to happen, since I was not when it happened to me. Reading the code, it can happen whenever there are no empty spaces among the 8 surrounding ones. "Not empty" includes spaces with monsters on them. If there is nowhere safe to be "pushed" to, you get the "crush" effect, and you stay in the same place. If you are unfortunate enough that the subsequent earthquake *still* leaves you with nowhere to go, it can happen again. It appears to me that standing on an artifact (or stairs) is irrelevant since the code does not check the space you are *on*, only the 8 surrounding ones.

AFAIK crushing happens only if the game tries to form a rock where you stand, and that doesn't happen when you are standing on a artifact. Checking escapes happens only after it has already passed the check of generating the rock there.

You got unlucky with escapes.

[Thraalbee]

In my experience, Morgoth never needed more than two or three turns to break a glyph at most, making the cost of casting them more than the cost of healing for priest-types.

I'd say for a Priest, glyph is definitely worthwile but wouldn't collect ?'s for the final fight as a fighter.

My last winner in 3.2 was a Priest. I fought M in a dead end in a vault and kept casting glyphs all through the fight. It was a long fight and I'd say the average time per glyph was rather 3-5 turns than 2-3, I had high speed if it matters.
I only chugged a single !Restore Mana and that wasn't really neccessary, Staff of Magi worked fine in combination with the glyphs. My immediate comments after the fight was that the glyphs were too powerful, but after thinking about it more I'd say it's ok as it is. Priests are easy in the late part of the game, I see no problem with that.

/Mathias

[bron]

AFAIK crushing happens only if the game tries to form a rock where you stand, and that doesn't happen when you are standing on a artifact.

That's not the way I read the code: in "earthquake()" in spells2.c, the game can *try* to form a rock on a location regardless of what is there, *then* the player on that location gets hurt, *then* the code checks cave_valid_bold and decides not to place a rock there after all if there is an artifact on the floor. But it looks to me like the player still takes the crush damage.

As I said in the original post, I admit that the odds of this happening are low: there is only a 15% chance that the game will try to put a rock onto the space you are in, and you have to fail that check twice, and be surrounded both times. OTOH, people worry about getting to speed +30 to face Morgoth even though the odds of him doing a double mana-storm during the precise turn that he also gets a double move are quite low. It is, however, something to be aware of.

[Timo Pietilä]

That's not the way I read the code: in "earthquake()" in spells2.c, the game can *try* to form a rock on a location regardless of what is there, *then* the player on that location gets hurt, *then* the code checks cave_valid_bold and decides not to place a rock there after all if there is an artifact on the floor. But it looks to me like the player still takes the crush damage.

That's how I read that too. Odd. I was sure that standing on a artifact prevented you from being crushed by rock. Checked older code and I'm seeing exactly same there too. Maybe it has been just in my mind. I haven't actually done that many times, I prefer runes, so it might be that it just not had happened when I have been standing on a artifact. Using runes Morgoth doesn't get many hits through during endgame.

[Pete Mack]

That one already happens. Runes get destroyed in case wall appears in its place. I don't think there is any kind of save for them.

It's the opposite: M can't hit you until he breaks the rune. So the broken rune leads to the earthquake, not the other way around.

[Timo Pietilä]

It's the opposite: M can't hit you until he breaks the rune. So the broken rune leads to the earthquake, not the other way around.

I mean that other runes, not the one you are standing on, can be destroyed by earthquake. Obviously M needs to break the rune to hit you in order to make earthquake, so that part earthquake can't destroy the rune because it simply doesn't happen.

Hmmm....Maybe we should make earthquake as monster spell?