Angband 4.2.2

[fruviad]

I've downloaded the source to an Ubuntu 18.04 box and I'm attempting to compile. It fails with:

Successfully compiled z-type.c.
Successfully compiled z-util.c.
Successfully compiled z-virt.c.
LINK angband.o
main.c:56:1: warning: ISO C forbids empty initializer braces [-Wpedantic]
{
^
main.c:55:28: error: zero or negative size array ‘modules’
static const struct module modules[] =
^~~~~~~
Failed to compile main.c!
../mk/buildsys.mk:242: recipe for target 'main.o' failed
make[3]: *** [main.o] Error 1
../mk/buildsys.mk:110: recipe for target 'all' failed
make[2]: *** [all] Error 2
mk/buildsys.mk:115: recipe for target 'subdirs' failed
make[1]: *** [subdirs] Error 2
mk/buildsys.mk:110: recipe for target 'all' failed
make: *** [all] Error 2

The version-generic compiling documentation at https://angband.readthedocs.io/en/la...compiling.html states that the compiling process requires that you run "./autogen.sh", but my downloaded 4.2.2 includes no "autogen.sh" file. I tried copying autogen.sh from my 4.2.1 install and running it just to see what would happen, but there was no difference in the result; the error occurs both when skipping autogen.sh, and when using the 4.2.1 version of autogen.sh.

As an aside...is there install documentation specific to each version? If the install process changes and every version is pointing at the same set of instructions, older releases will eventually no longer have documentation for their installs.

[Nick]

It looks like no front ends are being enabled.

If you have a

configure

script in your top level directory, you should be able to skip the autogen.sh step. In this case, you can try

./configure --help

, and try enabling different front ends explicitly and see if that helps.

[Bogatyr]

For the same font and font size, the 4.2.1 and later Mac front end will take up more space. That was a side effect of rendering changes to speed things up, avoid clearing artifacts with some fonts, and allow the front end to work reasonably well with some of the variants (Hengband, Sil-q).

Disappointing -- it makes the game visually less appealing. Is there a configure option or way to put the old rendering engine back if I build angband myself?

[Nick]

Disappointing -- it makes the game visually less appealing. Is there a configure option or way to put the old rendering engine back if I build angband myself?

Without checking, I suspect if you replaced src/Makefile.osx, src/main-cocoa.m and the entire src/cocoa directory with their counterparts from 4.2.0 then that would work.

[Bogatyr]

Without checking, I suspect if you replaced src/Makefile.osx, src/main-cocoa.m and the entire src/cocoa directory with their counterparts from 4.2.0 then that would work.

Thanks, I'll try that. My eyes thank you, as I had to reduce the font size with the new release in order to get all the same info as I had before on-screen.

[Bogatyr]

I also noticed that slow (wand and staff) now wakes monsters. I almost always play emphasizing stealth, so this is a bit of a setback... but perhaps non-waking slow was too powerful, it did definitely make dealing with groups much easier.

[Ingwe Ingweron]

I also noticed that slow (wand and staff) now wakes monsters. I almost always play emphasizing stealth, so this is a bit of a setback... but perhaps non-waking slow was too powerful, it did definitely make dealing with groups much easier.

Slow does wake them, but confusion and stunning do not. I think maybe that was an oversight on Nick's part, but maybe he was being purposefully lenient. In the FirstAgeAngband nightly, Nick has made all of them wake the monsters.

[will_asher]

I just used a wand of wonder which caused an earthquake, and the couple ogres I had aimed the wand at slept through it. I'd call that a bug.

[Nick]

I just used a wand of wonder which caused an earthquake, and the couple ogres I had aimed the wand at slept through it. I'd call that a bug.

That's actually working as intended.

[will_asher]

That's actually working as intended.

So ogres are supposed to sleep through an earthquake? (and get waked up by _slow monster.) weird.

(I do have very high stealth, but I wouldn't think my stealth could possibly muffle an earthquake...)

[Nick]

So ogres are supposed to sleep through an earthquake?

They'll wake up if a bit of ceiling falls on them. Otherwise it just feels like their mother rocking them in their sleep

[will_asher]

They'll wake up if a bit of ceiling falls on them. Otherwise it just feels like their mother rocking them in their sleep

Ogres are just big ugly babies, aren't they.

[bughunter]

So ogres are supposed to sleep through an earthquake? (and get waked up by _slow monster.) weird.

(I do have very high stealth, but I wouldn't think my stealth could possibly muffle an earthquake...)

I've lived in Southern California over 30 years. I sleep thru earthquakes all the time.

And I'm not even an ogre...

[Bogatyr]

Slow does wake them, but confusion and stunning do not. I think maybe that was an oversight on Nick's part, but maybe he was being purposefully lenient. In the FirstAgeAngband nightly, Nick has made all of them wake the monsters.

Boo! Always nerfing on stealthy mages. 4.2.0 was SO much fun....(but, admittedly, not much of a challenge).

4.2.2 takes much more tip-toeing and pre-fight prep for mages. More challenging, yes, but definitely slower play. The endgame power of mages is fully justified for all the super-cautious early and mid play. No more nerfing mages, please!

Also definitely not happy about recharge nerfing. If anything, limiting the per-cast # of charges gained would be OK, perhaps even the max # of charges, but increasing the 0-charge likelihood of backfire is quite disappointing. Now I have to stockpile all the critical wands/staves at home.

[Bogatyr]

The stunning effect of Tap Magical Energy happens even if you don't end up selecting a device or otherwise cancelling at the selection step.