Borg bugs and feature requests

[eschiss1]

Tried the new/old borg log feature but now not sure how to turn the log off - replacing the map file name with blank, as a conjectural way of saying "ok that's enough", just crashes the program... Oh, because it's a snapshot log file, not an ongoing one as in earlier borg versions once upon a time, and there's nothing to turn off. Maybe shouldn't crash the program, but shouldn't be trying to create an empty file, either.

[eschiss1]

btw will it still work with my old borg save file, borg.txt, etc., or do I need to start a whole new installation? never mind- solved that problem, I think.

[eschiss1]

There, found out how to get past Mac Gatekeeper...

[eschiss1]

I'll try the prereleases page. Thanks

[backwardsEric]

Further edit: Mac just won't open Angband opened from Rephial.org at all. Back to Macports version with September 26 2024 borg, then, for now!

The method described at https://support.apple.com/guide/mac-...er-mh40616/mac does not work? The ways to open an unsigned application were restricted further in macOS 15; before that you could also do this:

1. Control click (i.e. click while holding the control button down) on the application in the Finder.
2. Select "Open" in the menu that comes up.
3. That will bring up a confirmation dialog about allowing the application to open on the system.
4. If your account does not have administrator privileges, there'll be an additional dialog asking you to authenticate as an administrator to apply the exception to the security settings.

I don't know who handles Angband in Macports, but they likely only update for the major releases. So I wouldn't expect the version available in Macports to change until after 4.2.6 is released.

[Nick]

Ooh, was looking for the "keep playing" borg.txt cheat death WIll try that. Thanks-- ah, the version I have (via MacPorts) is still using the Sep. 26 2024 borg compile. Not sure whether the Nov. 2024 compile is available for the Mac yet. (maybe if I'd downloaded it more normally, rather than by MacPorts. Worth checking.)

Further edit: Mac just won't open Angband opened from Rephial.org at all. Back to Macports version with September 26 2024 borg, then, for now!

You can get the very latest version from the releases page - have you tried that?

[agoodman]

Necromancer bug: seems to cast crush at anything that looks like it's in its line of sight, which can become a real problem if it has telepathy. Repeatedly. Often runs very low on hp this way and this may be the indirect cause behind some unnecessary deaths.

okay, I will take a look at his use of crush. I have run into issues with it before. It is new code and was a SWAG on how to use it.

Ooh, was looking for the "keep playing" borg.txt cheat death WIll try that. Thanks-- ah, the version I have (via MacPorts) is still using the Sep. 26 2024 borg compile. Not sure whether the Nov. 2024 compile is available for the Mac yet. (maybe if I'd downloaded it more normally, rather than by MacPorts. Worth checking.)

Further edit: Mac just won't open Angband opened from Rephial.org at all. Back to Macports version with September 26 2024 borg, then, for now!

Hmm. Nick or backwardsEric might have some clue on the Macport. I don't have a Mac handy so I can't test.

[eschiss1]

Necromancer bug: seems to cast crush at anything that looks like it's in its line of sight, which can become a real problem if it has telepathy. Repeatedly. Often runs very low on hp this way and this may be the indirect cause behind some unnecessary deaths.

(used to have another account but locked myself out of it, grumble. Hrm, never mind, I seem to be posting as my old name anyway despite having had to log in under a new one. Weird, but ok!)

Ooh, was looking for the "keep playing" borg.txt cheat death WIll try that. Thanks-- ah, the version I have (via MacPorts) is still using the Sep. 26 2024 borg compile. Not sure whether the Nov. 2024 compile is available for the Mac yet. (maybe if I'd downloaded it more normally, rather than by MacPorts. Worth checking.)

Further edit: Mac just won't open Angband opened from Rephial.org at all. Back to Macports version with September 26 2024 borg, then, for now!

[agoodman]

a quick list of changes to the borg since the last time I mentioned changes to the borg:
1) cheat death in borg.txt. a setting to allow the borg to keep playing and just cheat death rather than being reincarnated
2) fixes to vault excavation logic
3) fixes to light beam attack
4) fixes to sell things before they are ID'd if the borg has more than one
5) fixes to using unblessed items to match new paradigm for that
6) better collection of teleport staffs
7) fixes to prioritize high cal food more
8) fixes to attacking when afraid since it now doesn't cost an action
9) fixes to identifying monsters on the map
10) make sure the code stops when things go wrong rather than letting bad keypresses accumulate
11) fixes to the use of tremor and earthquake spell
12) fixes to which spells can be cast just for experience
13) check for "web" on the ground. used for teleporting
14) changes to how the "uniques alive" count is done and used
15) fixes to how cursed items are handled
16) fixes to home optimization which was very slow before and should be faster now
17) flow changes to avoid being stuck and help some exploration
18) fixes to potion collection during the endgame

and other things. Full list can be seen https://github.com/angband/angband/p...r%3Aagoodman00

Just wanted to make sure people know that just because things have been quiet on the forum doesn't mean things aren't being done.

[agoodman]

I thought the ^Z-l command began saving the borg messages to a file, hence "log" (this was, if I recall, true of earlier versions, years ago.)

https://github.com/angband/angband/pull/6048 now crates a .map file that includes logged messages

[agoodman]

I thought the ^Z-l command began saving the borg messages to a file, hence "log" (this was, if I recall, true of earlier versions, years ago.) I didn't think it was doing anything because it wasn't doing that, but I may be mistaken; !

Mistaken or not, not a bad idea. I will add a note to my todo list. Might even be better to dump the full character, map, and recent log much like the .map file on command.

[eschiss1]

I thought the ^Z-l command began saving the borg messages to a file, hence "log" (this was, if I recall, true of earlier versions, years ago.) I didn't think it was doing anything because it wasn't doing that, but I may be mistaken; I had forgotten to check borg-log.txt. yes. Yep, borg-log.txt is there, registers two very good borgs in a row in fact (whose maximum death dungeon levels are a bit misleading as they were reset higher/less than they actually were, so one who died having reached level 92 at one point is described as "Killed on level: 74 (max. 74) by an osyluth", but, nothing for that . The one before that one couldn't quite figure out how to take on two drujn (drujs? Bruges? Drujes? ) at once, but I remember years ago getting taken out by merely one of them when playing at one in the morning by my lonesome, and can sympathize.)
Thanks!
Edit: most recent fairly long-lived borg instance died (this morning, only level 38/dlvl 28...) because, from the looks of the messages at death, did not recognize creeping adamantine coins as an enemy?... - ok, no, that's not the reason, the monster memory now says "Your ancestors have killed at least 20 of these creatures". Still, this borg was not even trying to fight back, which is - just weird. Can attach some form of the messages if that's helpful if it suggests there might be a bug...

[agoodman]

Also, while I'm on it, apologies, but is there a chance that the borg [l]og function will be re-enabled in the near future? That said, I know I gripe, but it's just fun to have a working borg (for MacOS) back!- one of the borg dunadan paladins, for the first time in years and years, got as far down as dungeon level 92 before dying just recently...

It isn't working? There should be a borg-log.txt with a list of the deaths and causes and a borg.dat with the same data in csv format (I think) and, depending on your borg.txt settings, a {name}.map. You only get the .map if you are above the config borg_dump_level.

[eschiss1]

Also, while I'm on it, apologies, but is there a chance that the borg [l]og function will be re-enabled in the near future? That said, I know I gripe, but it's just fun to have a working borg (for MacOS) back!- one of the borg dunadan paladins, for the first time in years and years, got as far down as dungeon level 92 before dying just recently...

[agoodman]

btw, I created
Borg todo list
which has a list of some of the things on the todo list... including the "deep descent isn't used",