Angband 3.2.0 Borg

[thapper]

There still seem to be something not quite right with this. My current Borg is wearing Firestar (with immFire) and from time to time (but not always) he seem to miss that his rCold is expiring (after casting "resist Cold and Heat"). I've only seen it since he found Firestar so I suspect it has something to do with that.

EDIT: No, it still appeared after he had ditched Firestar. Perhaps it has something to do with if the resist Cold/Heat expires in town? (Wild guess)

I think I might have found it. When the borg visits his home and he has some equipment with an immunity stored there, he picks up a temporary resistance for that element. Since this is not true there will never be a message cancelling it.

I think this happens because he evaluates all equipment at home and when he hits something with immunity that tells him that he has both resistance and temp_resistance to that element so that he won't get any bonus to power from additional sources of this.

The same seems to happen it the borg has wielded a piece of equipment with an immunity but taken it off. He then keeps on believing that he has a temporary resistance for that element.

[Magnate]

Ha!

I made my first ever attempt to find something in the code (well, second, but never mind) and I found it!

The problem with the borg_hero flag never going off (in BORG9.C) is off course that the message for running out of heroism has changed from "The heroism wears off." to "You no longer feel heroic."

The same for Berserk: "You feel less Berserk." is now "You no longer feel berserk."

The next step for me would be to start compiling myself to test that it works...

The borg shouldn't be trying to parse messages, but should instead be testing either p_ptr->timed[] or p_ptr->state.flags[] for this kind of thing (for temp and perm stuff respectively). There is a function called check_state() which will check whether the borg has a particular flag (e.g. RES_COLD) from either a timed or permanent source. You can pass it the known state rather than the actual state, so that it doesn't cheat.

[thapper]

Ha!

I made my first ever attempt to find something in the code (well, second, but never mind) and I found it!

The problem with the borg_hero flag never going off (in BORG9.C) is off course that the message for running out of heroism has changed from "The heroism wears off." to "You no longer feel heroic."

The same for Berserk: "You feel less Berserk." is now "You no longer feel berserk."

The next step for me would be to start compiling myself to test that it works...

[APWhite]

*edit* Got stuck again a couple levels later, I watched it for 2500 turns then decided to upload the savefile for you. Just as a question, am I expected to edit the Borg.txt file or does it work fairly well with the options that are already in there?

You can edit the top part of the borg.txt file with no bad repercussions. Editing the bottom half (after the warning) is not a good idea unless you really know what you are doing. But by default, the bottom stuff is turned off. You you would have to chance the borg_uses_dynamic_calcs to true in order for the borg to use the bottom half of the borg.txt.


the bounce is fixed. I recognized it right away. I saw this in the zborg about 2 weeks ago and thought I made the correction for vborg as well. Basically, it wanted to flow to the stairs that were stuck behind a wall.

[thapper]

Echo thought his RFire was engaged when it was expired. He missed the expiration message (since they are now different from what they were in 309).

There still seem to be something not quite right with this. My current Borg is wearing Firestar (with immFire) and from time to time (but not always) he seem to miss that his rCold is expiring (after casting "resist Cold and Heat"). I've only seen it since he found Firestar so I suspect it has something to do with that.

EDIT: No, it still appeared after he had ditched Firestar. Perhaps it has something to do with if the resist Cold/Heat expires in town? (Wild guess)

[Jungle_Boy]

the borg will keep count of his steps. He will break loops if he gets to about 350 steps. Did you let it run at least 350 steps? If it is still freaking out, send me the savefile.

Also, I trust it was a typo when you say the borg.txt file is in the \usr directory, it should be the existing \user directory.

Andrew

I had a guy get stuck in a two-step north-south loop for over 5000 turns so this doesn't seem to always work. I finally broke him out myself when it was obvious he wasn't going to.

Also I noticed he refuels his torches at 2500 turns, is there a reason for this choice since radius does not decrease until 1500 turns.

*edit* Got stuck again a couple levels later, I watched it for 2500 turns then decided to upload the savefile for you. Just as a question, am I expected to edit the Borg.txt file or does it work fairly well with the options that are already in there?

[APWhite]

Rule number one: Don't get yourself surrounded.

If Borg is fighting multiple high level U:s in middle of the large room it is dead fire resistance or not. If that group contains even two Gelugons or any combination of Gelugons+Pit Fiends resistances do not help. Almost all major demons are summoners, you should never fight summoner in large open area.

If you can teach that to borg it should survive deep much longer.

The Anti-Summoning Corridor is finished. I am testing it now. So far it is really nice. EchoB, a level 50 Ranger is knocking down summoner uniques left and right. In just a few minutes, he took out Ungoliant, Kronos, Mouth of Sauron, and the Cat Lord. It was no problem for him. He dug the tunnel, sat there and waited for the summoner to show up. I will continue to test it for a day before I upload the code. On the front end, I am not seeing any bad behavior, or buggy moves.

[Jungle_Boy]

I just downloaded this the other day and started playing with it. I'm not sure if I have a setting wrong or what. My last three characters have died of starvation, two on level one and one in town. I have connected stairs on so finding a way up should not be a problem. This thing is fun to play with but sometimes it seems to get stuck in a loop quite often, it does eventually get out I think. One time in town the door for home was on a corner and it got stuck looping on the opposite corner like it couldn't decide which way to get there.

[thapper]

Couldn't wait so I'm running a new borg now. Three things, first, it's running much faster, is it just some delay that got changed or is it a huge improvement in efficiency?

Good thing that the temporary resistances got fixed but could you check if the same problems exist for "heroism" and "berserk" as temporary buffs? These indicators never go off in the borg status window after the borg has buffed once. "Shielded" seems to work, "prot. from evil" I don't know.
EDIT: "prot. evil" and "blessed" also works, only "heroism" and "berserk" never goes away.

Last, and this one is divided in two issues, my new borg seems to get a lot deeper than he "should". Currently he's clvl 29 and on dlvl 36. If I do ctrl+Z->2 it tells me that I'm ready for dlvl 22 (dlvl+7 >= clvl). The borg status window tell the reason for not diving is clvl < dlvl. So, the message for not diving is different in the borg status window and when I check "Borg power". And, he's not caring about those at all, usually he has rather been hanging out at dlvl 20 at this point. I'm not complaining, it speeds up the borg quite a bit, but I guess it might not be intentional.
EDIT: I guess the different messages were due to that he got so deep (below clvl=dlvl). The problem is that he seems unable to reset his recall point and he is too scared to stay that deep for long. At some point he gave up and started go down from dlvl 1 instead.

[Timo Pietilä]

This was not EchoB's fault; it was mine. I fixed the problem that lead to his death. Echo thought his RFire was engaged when it was expired. He missed the expiration message (since they are now different from what they were in 309).

Rule number one: Don't get yourself surrounded.

If Borg is fighting multiple high level U:s in middle of the large room it is dead fire resistance or not. If that group contains even two Gelugons or any combination of Gelugons+Pit Fiends resistances do not help. Almost all major demons are summoners, you should never fight summoner in large open area.

If you can teach that to borg it should survive deep much longer.

[APWhite]

No endgame for EchoB, next time I looked into what the borg was doing it was dead, killed by a greater balrog after fighting Us (Gothmog etc) in the middle of a large room...

This was not EchoB's fault; it was mine. I fixed the problem that lead to his death. Echo thought his RFire was engaged when it was expired. He missed the expiration message (since they are now different from what they were in 309).

The fix is already uploaded to the webpage. But can you wait to run EchoB until I add a new routine. I will have the borg dig a better antisummon corridor. He is trying to fight the deep unique summoners in rooms instead of in the hallways and worse, he is not digging the corridors that we all dig. It will take a day or two for me to finish. In the end the borg will dig something like this:

/*
 * Dig an anti-summon corridor. Type I
 *
 *            ############## We want the borg to dig a tunnel which
 *            #............# limits the LOS of summoned monsters.
 *          ###............# It works better in hallways.
 *         ##@#............# 
 *         #p##............# 
 * ########## #######+###### 
 * #                  #
 * # ################ #
 *   #              # #
 * ###              # #
 *
 */

[APWhite]

That's interesting. The ID assumes the equipment is the default group. The borg will need to hit '/' before selecting the 's'. I'll fix this in the morning and let you know.

That was repaired and the fix was uploaded to the webpage.

[APWhite]

I'm eager to get the September 14 end game fixes (the windows.exe was still from September 11 when I checked just now) since I think my borg could make it to the end game...

But for now EchoB get stuck after activating "Eriril" for ID. I've seen it twice, both times there have been an un-IDd ring in the inventory.

That's interesting. The ID assumes the equipment is the default group. The borg will need to hit '/' before selecting the 's'. I'll fix this in the morning and let you know.

[APWhite]

I'm eager to get the September 14 end game fixes (the windows.exe was still from September 11 when I checked just now) since I think my borg could make it to the end game...

But for now EchoB get stuck after activating "Eriril" for ID. I've seen it twice, both times there have been an un-IDd ring in the inventory.

I will run EchoB with debug mode on and catch his death to see why he dies.

[thapper]

No endgame for EchoB, next time I looked into what the borg was doing it was dead, killed by a greater balrog after fighting Us (Gothmog etc) in the middle of a large room...