Angband 3.2 released!

[Nick]

Maybe as last selection before roller with just question "change birth options?" yes/no?

In O 1.1.0u there are only two birth options, so I just have a final question on the first birth page listing all four possibilities. I did the same in FA for a while, but when it got beyond 3 options I ran out of room.

I think going straight to a birth option page after roller choice and before point allocation (or whatever) is the best option.

[PowerDiver]

Maybe as last selection before roller with just question "change birth options?" yes/no?

How is that better than a page listing all of them, titled

"Change any birth options: ESC to start game"

or hopefully a better title.

[buzzkill]

Maybe birth options should be greyed out when you look at them via the '=' menu, so they're there but it's more intuitively obvious that they can't be changed in-game.

I was thinking this before I read it. Just having them absent is going to lead players to wonder where they went, or if they are unaware or them to begin with, they will remain unaware.

Also, why on 'link' to the option screen (=) from the Windows 'drop down' options menu.
Also, the 'drop down' help 'link' doesn't work either, windows vista.

[Nomad]

Maybe birth options should be greyed out when you look at them via the '=' menu, so they're there but it's more intuitively obvious that they can't be changed in-game.

Also, while we're talking about squelch options, would it be possible to implement some kind of global toggle for quality squelch? I would dearly love to have a single setting at the top of the menu that can be used to toggle everything from "no squelch" to "bad" simultaneously. Because I always want to squelch bad in every category right from the start, and having to go down the whole list again and again every time I die and start over drives me nuts.

[Timo Pietilä]

I think it's a good idea to allow people to see the birth options outside of birth, so people can tell what their options are... I will implement the second suggestion, though.

Maybe as last selection before roller with just question "change birth options?" yes/no?

[takkaria]

It turns out they are there, sort of. I tried to change the birth options, got a message can only change them at birth. You have to press '=' to see them during birth.

IMO you shouldn't be able to see the menu outside of birth, and during birth it should be a screen brought up automatically without any '=', but that's all UI. The rule to only allow changes to birth options at birth appears to be in force.

I think it's a good idea to allow people to see the birth options outside of birth, so people can tell what their options are... I will implement the second suggestion, though.

[Estie]

Agree, dsms need their own class. But throw robes in together with body armours. Its highly unlikely to not find some dsm of permanence which is always better than robe of same, and if anyone is really desperate for sustains he can inscribe robes with !k.

[Timo Pietilä]

You can work around that by setting an auto-inscribe of "!k" on all dragon armors using the knowledge menu. Then you can safely squelch body armors without squelching dragon armors.

Assuming you have seen all the DSM:s. You can't do it to those that you have not seen yet.

Better solution would really be separate DSM:s from rest of the bodyarmors for squelch. Anything needing a workaround indicates that there is something UI could do for you better.

Those new ego-DSM:s can be so much better than rest of the ego-bodyarmors that there really is a need for separating them from rest of the group. Like Balance DSM of Permanence {poison/confusion} or any DSM with speed-bonus, or even elvenkind of any non-single basic4 DSM.

[PowerDiver]

But you are right that takk's birth option changes are not there. They must be in an unmerged branch of his. Sorry for the noise.

It turns out they are there, sort of. I tried to change the birth options, got a message can only change them at birth. You have to press '=' to see them during birth.

IMO you shouldn't be able to see the menu outside of birth, and during birth it should be a screen brought up automatically without any '=', but that's all UI. The rule to only allow changes to birth options at birth appears to be in force.

[PowerDiver]

I've seen that assertion failure too, but only on occasional savefiles. It might be to do with the removal of bronze DSM.

That could explain it. The retired char had bronze DSM at home.

[Derakon]

You can work around that by setting an auto-inscribe of "!k" on all dragon armors using the knowledge menu. Then you can safely squelch body armors without squelching dragon armors.

[pampl]

Could dragon armor be in a separate squelch category than body armor, or always count as ego or something? There are long periods of game time where I'd want to squelch magical armor but be happy with a nice set of DSM

[Magnate]

Any idea when staging will migrate? I tried
git clone git://github.com/angband/angband.git
and still see the old style birth options.

I should note that a char I just retired, not sure but I think it was running the official release of 3.2 on rephial, crashed on startup with the git clone above due to an assert

angband: load.c:121: rd_item: Assertion `o_ptr->k_idx' failed.

The game started up just fine when I commented out the assert.

I've seen that assertion failure too, but only on occasional savefiles. It might be to do with the removal of bronze DSM.

If you're cloning the official repo, simply do

git checkout origin/staging

and then

git checkout -b newbranch

and compile newbranch. That way you can play whatever's in staging.

But you are right that takk's birth option changes are not there. They must be in an unmerged branch of his. Sorry for the noise.

[PowerDiver]

Birth options have been re-worked in staging: they're now *only* accessible during character creation, so no more confusion between birth/adult options etc.

Any idea when staging will migrate? I tried
git clone git://github.com/angband/angband.git
and still see the old style birth options.

I should note that a char I just retired, not sure but I think it was running the official release of 3.2 on rephial, crashed on startup with the git clone above due to an assert

angband: load.c:121: rd_item: Assertion `o_ptr->k_idx' failed.

The game started up just fine when I commented out the assert.

[Magnate]

It might have been the first time, but I was meleeing with an uber-warrior, so it must have been damaged after my first round of attacks.

Perhaps I got very lucky? There doesn't have to be a bug.

You're quite right, there doesn't - if it doesn't find a drainable item in ten tries, it gives up. I hadn't realised that - I thought it *always* drained something (if you had anything to drain).

Very lucky, in that case!