Hey there, thanks for the feedback. I'm not sure what could have caused this, can you send me your save file so I can double check? Maybe send an older one as well, if you still have it.
duelist 9:51 seed:115859796105. new record out of nowhere, early ring of learning but first melee weapon (broad sword) at second last floor before yendor, got my fastest yendor ever, 9 speed points with 2 power and 4 energy potions to strafe attack bosses in few seconds
addition to previous comment: seems like it doesnt always work, if goblin guard moves upright then it fails, if that pattern keeps repeating then try to change it by killing few enemies or something and then try again, when it works it usually works multiple times in a row.
seed: 96571951723. duelist only: ignore enemies and dont use sp, go 7 step down then 4 step down right then 5 step up and use scroll melee (mace+1) use another scroll ring (ring of slayer+1), this step count works only for duelist, other characters have different step counts.
found weird but pretty useless glitch, i dominated enemy that had heal on hit and when i died and started new game i had 60 something health but max health was normal so not real benefit.
Dandooka: first try your seed and got my second best time ever 12:49 (duelist) there is a pit to drop to vault of yendor and skip both dungeons. then i got lucky with first scroll and got mace+1 second gave me 3x potion of energy that was almost useless, but 1 of the chest triplets had wand of cold that made the run possible, i even forgot to put 2 talents on precision to get 40%more crit damage cause i usually get 14dex to get dash attack that i never got. str13 dex12 my lowest attributes and talents ever to finish a run also. i also had +2 goblin swift bow that gave half my sp:)
11:29 duelist, broad axe, +2goblin swift bow, +1 gauntlets of strength, ring of learning, weapon mastery and 4 power potions, str15,dex14. insanely lucky run despite not so good weapon and no
flash freeze or wand of cold.
Thanks for pointing this out. I'll make sure to fix this in the next update :)