Borg bugs and feature requests

[eschiss1]

Re #131, 134. Uploading a truncated log file that shows some of what happened, where the dungeon map probably contains the most information- will see if I can capture this at a point that shows what's happening more informatively rather than when the "infinite loop" is already well underway at 5 a.m. Not sure if I remember anything flowing towards me, but I may be misremembering.

[agoodman]

Re #131, 134. Uploading a truncated log file that shows some of what happened, where the dungeon map probably contains the most information- will see if I can capture this at a point that shows what's happening more informatively rather than when the "infinite loop" is already well underway at 5 a.m. Not sure if I remember anything flowing towards me, but I may be misremembering.

He is waiting for the "B" (crow) to approach. So, why isn't it approaching? I wonder if it is afraid or something. I can check for status afraid or stunned or confused. It is only supposed to do this when the monster is within a step so I will also add a "don't do this twice in a row" check. I am also going to change the message to
"waiting for monster {name} to approach"
just so we can be sure we know what we are waiting for and we already know what square we are on so that seemed like useless information.

[eschiss1]

it was either asleep, or in a holding pattern with its holding pattern, or... hrm. Good point. It's happened once (with wildcats) since but I'll see if I can find out next time...

[backwardsEric]

An awake monster whose level is less than the player's level - 35 will always try to flee (and a fraction of the monsters whose levels are less than the player's level - 28 also flee). There's a more involved calculation, taking into account the player's and monster's hitpoints, that can cause a monster whose level is less than the player's level - 20 to flee. In all those cases, the monster does not necessarily have the afraid timed effect.

That may explain the behavior of the wild cat (level 2) and crow (also level 2) facing a level 50 rogue.

[agoodman]

An awake monster whose level is less than the player's level - 35 will always try to flee (and a fraction of the monsters whose levels are less than the player's level - 28 also flee). There's a more involved calculation, taking into account the player's and monster's hitpoints, that can cause a monster whose level is less than the player's level - 20 to flee. In all those cases, the monster does not necessarily have the afraid timed effect.

That may explain the behavior of the wild cat (level 2) and crow (also level 2) facing a level 50 rogue.

from what I can tell in the code such monsters aren't marked as "afraid" so they won't trigger that check but if I make sure the borg doesn't do it twice in a row he will, hopefully, wait once then approach. If the monster steps away we may see a stutter-y approach until the monster is pinned down. I could add a check for mon level + 25 vs plevel. Not sure it is worth it. Chances of this being a problem is pretty low. I am even having trouble duplicating it using this "attack" at all.

added https://github.com/angband/angband/pull/6516 which should help.

[eschiss1]

Thanks. It's happened a few times in, however, a weird game.

[eschiss1]

By the way, the list of borg commands in borg.rst.txt and on an official website I think too, gives an out of date list of internal borg commands (e.g. ^z 2 rather than the now ^z P for the depth the borg believes it's ready for.)

[agoodman]

By the way, the list of borg commands in borg.rst.txt and on an official website I think too, gives an out of date list of internal borg commands (e.g. ^z 2 rather than the now ^z P for the depth the borg believes it's ready for.)

I rewrote a bunch of the commands. I just checked in https://github.com/angband/angband/pull/6526 to update the docs.
btw, play around with the commands and see if they work the way you like.