I am getting really close to solving the loops issues introduced with 341. I have a paladin borg playing at depth 98 right now. He is doing well.
- The borg was looping at searching a chest. I added a modulus check.
- A high level paladin borg was in a loop buying a +0 set of boots then enchanting them to +12. He’d then sell them and buy another set of boots and repeat the process. It wasn’t a bad plan for making money, but he had plenty at that time. The bug was related to the reward for carrying the ability to enchant.
- The borg was thinking that a mimic chest needed to be searched before he could attack it. The word ‘chest’ was throwing him off.
- I forgot to add the MAX_STACK_SIZE to CCW storage in the home. He was using three home inventory slots to store 90 !CCW.
- Another fix to the sync issues. I think the issue was with the cyan color of the “-more-“. There are still a couple more issues that I can’t seem to find. I suspect there is a key_flush() or something introduced.
- The borg encountered another sync-issue and this one led to the rogue_like_commands being set to ‘true’. I added a check in the code to make sure the right command set was selected.
- Another sync issue. This one was related the borg experiencing a normal failures while casting spells. I added an “escape” keypress before each prayer attempt.
- The enchanting needed another tweak on using the ‘/’ and skipping the inventory.
- Testing ‘Tunneling’ a door instead of Bashing one for a few months. Bashing can leave the borg paralyzed.
Something is strange for me with the borg tunneling. Tunneling through rubble can take several hundreds of turns, whereas stopping the borg and “shift+t” only takes around 10 turns (18/20 strength, priest, so usually a blunt weapon if that makes any difference). I often also find it “stuck” trying to tunnel through quartz veins and never getting anywhere, regardless of how many 100x cycles it does. I haven’t seen it at a stuck door yet but I assume it might react the same there…
Hi again,
I had a look in a .map file after my last borg’s death. I’m not sure what I am looking at but something seems strange to me. The map depict “@” in a room, a “&” next to him and two “p”s in a corridor, ~5 steps away, no other monsters except a skele orc in another part of the map. Yet the last messages states that: # Flowing toward item at cost 1 / & Key (0x36) / You hit Sangahyando of Umbar. / Sangahyando of Umbar hits you. / You die.
So it seems to me that @ was next to Sangahyando, bumped into him when trying to get to an item (bolt), and ultimately got killed by him. Is the map the final death screen? Then I guess the borg had lost track of the monsters and could not update his references. Would you be helped by the .map file? Or something else?
Ya. I found this one too a few days ago. I think I corrected it with the update for 8/8/13.