Angband 4.0beta status

[Nick]

Update e77b3ef is takkaria'a patch to allow wildcards in .prf files.

[Jungle_Boy]

I picked up a two-handed great flail and it pseudoed as {excellent}. I wielded it and felt stronger healthier and more dexterous, now it has a {splendid} tag. I swung it at a nearby uruk and it glowed and identified as "of Westernesse" but it still had the {splendid} because only one of the slays had been identified. This may be working as intended but it is a change to have the ego identified but not fully known.

[Jungle_Boy]

I read an unidentified scroll, turned out to be enchant weapon to-dam, I hit escape instead of choosing a weapon and it still consumed the scroll, is this intended?

[Nick]

I read an unidentified scroll, turned out to be enchant weapon to-dam, I hit escape instead of choosing a weapon and it still consumed the scroll, is this intended?

I guess not. This applies to enchant, ID, recharging I guess - any others?

[Ingwe Ingweron]

I guess not. This applies to enchant, ID, recharging I guess - any others?

The can't back out bug. If I recall the earlier posts, this is also draining mana points when casting certain spells, but then backing out, e.g., Identify, Enchant Weapon, Enchant Armor, etc. Haven't tested this lately.

[Nick]

The can't back out bug. If I recall the earlier posts, this is also draining mana points when casting certain spells, but then backing out, e.g., Identify, Enchant Weapon, Enchant Armor, etc. Haven't tested this lately.

Still happens, shouldn't after next update

[Nick]

Update 97c6d0d fixes:

• Mushrooms having a failure rate
• Pack re-arrangement message spam
• Backing out of ID, enchantment etc now possible
• Brands and slays learned on learning an ego

(Up soon)

[Nomad]

Update 97c6d0d fixes:

• Pack re-arrangement message spam

This is almost working perfectly now! Just one case I've found where you still get an unnecessary message: if you use the wield command to swap an item in for one that's already equipped. Wielding to an empty slot is fine (and hence if you use t to take off the existing item and then wield the new one you don't get any messages) but I assume swapping is satisfying the "nothing added or removed" condition and accidentally triggering the message.

[Nick]

This is almost working perfectly now! Just one case I've found where you still get an unnecessary message: if you use the wield command to swap an item in for one that's already equipped. Wielding to an empty slot is fine (and hence if you use t to take off the existing item and then wield the new one you don't get any messages) but I assume swapping is satisfying the "nothing added or removed" condition and accidentally triggering the message.

My first attempt at this gives a message if the taken off item goes to a different slot, so other stuff moves too, but not if it's a straight swap. This is different to 3.5.1, but might this actually be an improvement?

[pen]

Movement bug - latest build, roguelike command set. When using 'Run' (Shift-Direction) one stops next to an item, presumably so you don't actually pick it up by accident if you have auto-pickup configured. I do not use auto-pickup.

So, typically I would shift-run again and stop directly on top of the item, and press my key to pick it up if I've decided I would like to. However, in the latest builds doing so leads the character to run OVER the item stopping on the opposite side of it, necessitating a backtrack to pick it up.

It's really hard to play this way. Can that be fixed perhaps? Thank you for your work Nick!

[Thraalbee]

I have seen traps hide a downstair a few times. Not sure if that is a bug or not but don't recall seeing that in v3.

[Nick]

I have seen traps hide a downstair a few times. Not sure if that is a bug or not but don't recall seeing that in v3.

Yeah, that's a known bug - I just haven't been able to work out what's causing it yet.

[Nick]

Movement bug - latest build, roguelike command set. When using 'Run' (Shift-Direction) one stops next to an item, presumably so you don't actually pick it up by accident if you have auto-pickup configured. I do not use auto-pickup.

So, typically I would shift-run again and stop directly on top of the item, and press my key to pick it up if I've decided I would like to. However, in the latest builds doing so leads the character to run OVER the item stopping on the opposite side of it, necessitating a backtrack to pick it up.

Excellent! Running past items is a known bug - I had been unable to repeat it reliably until now, but this explains when it's happening.

[Nomad]

My first attempt at this gives a message if the taken off item goes to a different slot, so other stuff moves too, but not if it's a straight swap. This is different to 3.5.1, but might this actually be an improvement?

I don't think the message is necessary - I feel like it should only occur for 'unexpected' movement within the pack, i.e. not directly initiated by the player. If I'm actively shuffling my own equipment around, I anticipate that things will rearrange according; if I'm only identifying an item, I don't necessarily expect that it's going to hop into a new slot by itself after the name change, so that's when you need the message to alert you that it's happened.

[pen]

Excellent! Running past items is a known bug - I had been unable to repeat it reliably until now, but this explains when it's happening.

I'm not sure, but I noticed that trap disarming doesn't appear to be auto as well, you actually have to hit the disarm key combo and pick a direction. It feels like may be related. I have no idea why.