Bug reports (Spoilers ahoy!)

[Dreamdancer]

Did Namtar's Lair today and had no problem with JJ's Chaos Avatar (had previously 2 crashes with it) and the slow effect from Earthmothers Entanglement.

[Dreamdancer]

Had one dungeon runs with no problems from slow-effect from the teleport glyph.

But got now a crash from slow effect from the entangelment boon.
Damage a wraith. Took the boon. Killed it while it was slowed. Then i could even explore some new hexes. Crash occured as i tried used the BURNDAYS glyph, could activate it (see cursor) but not target an enemy.

[Lujo]

Crash in cursed oasis after mousing over the dragon boss.

[dislekcia]

I'm not entirely sure what's going on here, but I was worshiping Taurog and had Warrior Pact (the +1 HP, -3 piety) active, and each kill was increasing my HP but not changing my piety at all. (Taurog should grant +4 or +8 for magical creatures, meaning a net +1 or +5 piety and +1 HP for each kill, but I had +0 piety and +1 HP.) A while later in the dungeon my piety gain returned to normal. Maybe it was the effect of being near 100 piety?

That actually makes sense: If you're given piety by Taurog and that caps at 100, then you lose 3 piety for your pact, you're going to be at 97.

What happens if you sign up for the pact before you start worshipping Taurog?

[q 3]

That actually makes sense: If you're given piety by Taurog and that caps at 100, then you lose 3 piety for your pact, you're going to be at 97.

What happens if you sign up for the pact before you start worshipping Taurog?

So it's a result of order of operations and the piety cap kicking in immediately? Hmm. It didn't occur to me that the order in which you take a pact will affect the order in which you gain or lose piety. I'd test it the other way around but that would require scumming for both altars and then getting to 100 piety, and if I'm going to scum for things I'd rather scum for fun things.

[paplaukes]

Human berserker silver challenge.
He was level 7, at 50 hitpoints, wielding a bear mace (to avoid blinks, sort of) and a fine sword. Lacked 7 xp for next level.
1 square lower - level 6 dragonspawn at full health
2 squares lower - corroding plant
I drank courage juice to get the xp bump/first strike/might, combat prediction showed -2 health on mob and death for me. I went for it anyway. Leveled up! \o/ and died. If I understand it right, the extra damage from bear mace wasn't counted as 'first strike', so my guy got retaliated against and died before the knockback kicked in. I think the knockback should be counted along with the first strike, and if it isn't (bummer), I shouldn't be able to level up after dying.

[Dreamdancer]

@paplaukes:
If you drink the reflex potion (first strike + double attack) the knockback is applied to both attacks, if i remember correctly.
I think what happened is the following. First you hit the monster. Then the monster retilated and killed you. But the second attack from the reflex potion applied and killed the monster. But still strange that you got the second attack after the death.

[paplaukes]

Just to clear things up

So it's just 1 attack + knockback and the retaliation had to happen inbetween.

[Dreamdancer]

@paplaukes: err... my fault
mixed the 'courage juice' up with the 'strength pot' and then thought you had also drank a 'reflex pot' due to first strike.
shouldn't post to the forum, if i'm still half asleep

[dislekcia]

I really hope they fix this stuff pretty soon. And I have a small request going forward... can you guys maybe think twice before doing a huge update right before taking a few weeks off? I don't begrudge the time off at all, everyone deserves a break, but maybe wait to do the major bits of tinkering until you get back?

Sorry. Today's update fixes the hell out of this bug...

It wasn't actually caused by any large changes - the real problem was a small tweak to the way effects were ordered when applied to players and enemies. That would snowball into a situation that would crash the game when an effect that thought it should be in a position before something else turned out to not actually be there anymore - like when you slow an enemy with first strike. But only the first time that monster got moused over, which is why Weytwut didn't cause problems