1.4.8: Autoexplore and sustain dispersal bug

[Mankeli]

So, trying to figure out for what exactly happened here (check the screenshot). This I do know: I got instagibbed from autoexplore by an archmage rare outside of my light radius but the messages I got don't make 100% sense to me.

If you get hit by damage, status effect or spot a monster while autoexploring the game log shows you the reason autoexplore stopped for each of these. However, in this instance the game log claims that autoexplore was stopped because I took damage. The REAL reason autoexplore should have stopped is clearly because I was hit with Disperse Magic, not because I took damage. If the damage would have happened first then it would have just taken a charge out of bone shield, no biggie.

So the way I see it's either

1) autoexplore did not stop after my character was stripped of sustains
or
2) the game produces the "takes damage" message for disabling sustains eventhough disperse magic does not inflict damage.

Regarding number 2), notice that with essence of speed it is possible that the archmage indeed had a double action.

Anyone know what's up?

(Also re-assemble is still bugged just like it was 2-3 years ago)

[jenx]

No idea, but it's important that this sort of bug gets fixed imo ....

[Mankeli]

So, with a help of a skilled code reading individual it seems that my suspicion was correct: Autoexplore did NOT stop when why sustains got dispersed. The reason for this is that if you get hit with sustain removals without taking damage and from outside of your light radius so you can't see the attacker (maybe from stealth too), autoexplore does not stop exploring.

This seems really dumb, taking like 10 damage which autoexplore would stop for is far less threatening than getting ALL your sustains removed.

[jenx]

So, with a help of a skilled code reading individual it seems that my suspicion was correct: Autoexplore did NOT stop when why sustains got dispersed. The reason for this is that if you get hit with sustain removals without taking damage and from outside of your light radius so you can't see the attacker (maybe from stealth too), autoexplore does not stop exploring.

This seems really dumb, taking like 10 damage which autoexplore would stop for is far less threatening than getting ALL your sustains removed.

Hey Mankeli - could you appy your skilled code reading to solve this long-standing problem? http://forums.te4.org/viewtopic.php?f=42&t=47046

No one has been able to solve this - we should offer a reward

I think even DG said he hasn't been able to track down the problem...

[Mankeli]

Unfortunately I didn't mean myself but Mordy.

But jenx I have another example of chronomancy taking up huge amount of resources if this helps: My PM was dreamscaped and as you know you get dream projections to fight the invader. My dream projections got high paradox and started spawning teluvortas ----->game becomes almost fully unresponsive. I try to save the game and go afk for 10 minutes but the saving process never finishes and not even stunt can fix the save.

Don't know if this story helps at all but at least you know you are not alone with leaks!

[jenx]

Unfortunately I didn't mean myself but Mordy.

But jenx I have another example of chronomancy taking up huge amount of resources if this helps: My PM was dreamscaped and as you know you get dream projections to fight the invader. My dream projections got high paradox and started spawning teluvortas ----->game becomes almost fully unresponsive. I try to save the game and go afk for 10 minutes but the saving process never finishes and not even stunt can fix the save.

Don't know if this story helps at all but at least you know you are not alone with leaks!

yikes! i never want to encounter that scenario...

i love Warden's Call on adventurer builds, and TWs, but I've just had to stop using the tree, it grinds the game to a halt, and I have a brand new desktop with dedicated graphics card and memory.