Angband 4.0beta status

[Nick]

Are the ones that have found their way in to the menu "never to be seen again" btw?

What was happening was anything generated on the current level was getting into the menu, rather than just when they were found and identified as artifacts. So it was making no difference to whether they appeared again.

[Nick]

In 3.5.1, the Macro works perfectly and in 4.0 it does not.

Both 3.5.1 and 4.0 map the [5] key as "," stand in place. Both 3.5.1 and 4.0 require "Direction ('5' for target, '*' or <click> to re-target, Escape to cancel)?" when targeting activatable attack items. The macro [Aa5] works perfectly in both 3.5.1 and 4.0 if the weapon is charged.

In 3.5.1, if the weapon is depleted, the macro works perfectly, returning "That item is still charging." message.

BUT, in 4.0, if the weapon is depleted, the "That item is still charging." message is immediately cleared by a "Type '?' for help." message.

In my opinion, either 3.5.1 was doing it wrong somehow, or it is a 4.0 bug. There's no difference in the mapping of the [5] key between the two versions, so what gives?

OK, I finally have a proper answer for this.

What has happened is that you now learn that the item can't be activated before trying to target - this is new to 4.0. So you need a different inscription - in fact, I have tested, and I believe that Aa now does exactly what you wanted Aa5 to do.

[Ingwe Ingweron]

OK, I finally have a proper answer for this.

What has happened is that you now learn that the item can't be activated before trying to target - this is new to 4.0. So you need a different inscription - in fact, I have tested, and I believe that Aa now does exactly what you wanted Aa5 to do.

Well, I now have to manually enter the '5' to fire at my old target, but it's close enough. Thanks, Nick.

[Nick]

Any reason for not trying to fix those six before release? Mostly, I'm just begging for seen vs. aware in object list.

Yessir.

Update 58b9bc6 (up soon) fixes

• Divide object list into seen and aware objects
• Attempt to fix the non-logged artifact problem - it's hard to check since it's rare, but I did plug a plausible hole
• PowerWyrm's latest fixes to LOS projections

There is now officially one thing to do (after defining away a few inconvenient possible bugs), and it's writing a help file on how to modify the game - I'm part way through it. So the plan is to release when that's done. PowerWyrm's continuing fine-tooth comb approach will no doubt turn up more bugs; those I have before release will be fixed, the remainder will be for 4.0.1. Do keep reporting bugs if you find them, and if they're bad enough I'll delay release.

[Derakon]

Well, I now have to manually enter the '5' to fire at my old target, but it's close enough. Thanks, Nick.

I take it you don't like the "automatically use previous target" option? If that were on, you could use the keymap "*tAa" to target nearest and then activate the item.

[Nick]

I have just pushed a new update, but it's basically getting some technical stuff right - there will likely be more updates of a similar nature before official release. I'll report back here if there's actually anything affecting players updated.

[Ingwe Ingweron]

This is all great, Nick! Being able to "see" immediately what's in a room (or LoS) is hugely helpful. It's one of those things that I think people will wonder how they ever did without.

One bug removed from the list still exists. #1881 Object sub-window delayed 1 turn. E.g., pick up a potion or scroll and it still appears in the object sub-window until the next move by either player or monster. Compare the monster sub-window which works correctly, kill a monster and it immediately is removed from the sub-window.

[PowerWyrm]

Playing with randarts, the Ring of Firmament of Arath activates for DRAGON_LAW (randomly breathing shards/sound). I activate it, enter a direction and... the game crashes.

[Nick]

Playing with randarts, the Ring of Firmament of Arath activates for DRAGON_LAW (randomly breathing shards/sound). I activate it, enter a direction and... the game crashes.

Do you have a savefile?

[PowerWyrm]

Do you have a savefile?

Savefile attached. Just activate the ring (need to try multiple times with 75% fail) and the game crashes. Probably related to activation message, since the base message takes a "name" parameter and the artifact is "of Foo" type.

[Nick]

Savefile attached. Just activate the ring (need to try multiple times with 75% fail) and the game crashes. Probably related to activation message, since the base message takes a "name" parameter and the artifact is "of Foo" type.

Thanks. Turns out it's an error in the parsing of activation.txt - the dice are all getting attached to the first effect, so it was rolling a d230 to decide whether to breathe sound or shards...

I'll have a fix for this (and the name issue) tomorrow.

[Ingwe Ingweron]

Has @ just been extremely unlucky, or has monsters' "teleport away" become more powerful? @ has 100% saving throw, but it seems like whenever a monster casts "teleport away" it works.

Ah, probably a dumb question... I just realized @ has a resistance hole for rNexus. My guess is the saving throw isn't helping at all without the rNexus.

[Derakon]

Has @ just been extremely unlucky, or has monsters' "teleport away" become more powerful? @ has 100% saving throw, but it seems like whenever a monster casts "teleport away" it works.

Ah, probably a dumb question... I just realized @ has a resistance hole for rNexus. My guess is the saving throw isn't helping at all without the rNexus.

IIRC you only get a saving throw against teleport-level, and teleport-away (within the level) always works regardless of the player's abilities/resists. Fair's fair, the player's Teleport Other always works too.

[fizzix]

Fair's fair, the player's Teleport Other always works too.

I have been looking forward to the day where we can change that for a long time.

[Ingwe Ingweron]

IIRC you only get a saving throw against teleport-level, and teleport-away (within the level) always works regardless of the player's abilities/resists. Fair's fair, the player's Teleport Other always works too.

Maybe. In 3.5.1 @ would get a message something like, "Ar-Pharazon the Golden commands the player to go away." But @ could often resist that command. Perhaps he was trying to teleport level the @ away rather than just teleport away?