Angband 4.2.1

[moosferatu]

Do rings of damage not affect launchers? When I equip one I see the average damage change on my melee but not on my arrows.

[Ingwe Ingweron]

Do rings of damage not affect launchers? When I equip one I see the average damage change on my melee but not on my arrows.

Correct. Damage rings only affect direct blows. Accuracy, however, can be useful for launchers.

[mrfy]

Yes, I'm not sure what's happened there. The Github release page is correct.

From that page, I download the macosx disk image file, unpack, and the app inside says it's 4.2.1 but it has a create/modify date of July 14 2015. Install and open, and it no longer asks for permission to access the
Documents directory, and the New and Open menu options are greyed out.

The latest nightly says it's 4.2.0-362-gdde695d-dirty with a create/modify date of June 3 2020, install, and it works fine.

[Nick]

From that page, I download the macosx disk image file, unpack, and the app inside says it's 4.2.1 but it has a create/modify date of July 14 2015. Install and open, and it no longer asks for permission to access the
Documents directory, and the New and Open menu options are greyed out.

The latest nightly says it's 4.2.0-362-gdde695d-dirty with a create/modify date of June 3 2020, install, and it works fine.

OK, I'll check that. It's just possible I've made an error, it's happened before.

[Nick]

From that page, I download the macosx disk image file, unpack, and the app inside says it's 4.2.1 but it has a create/modify date of July 14 2015. Install and open, and it no longer asks for permission to access the
Documents directory, and the New and Open menu options are greyed out.

The latest nightly says it's 4.2.0-362-gdde695d-dirty with a create/modify date of June 3 2020, install, and it works fine.

All right, the macOS .dmg file on the Github release page is now correct. But someone else probably should check it...

[mrfy]

All right, the macOS .dmg file on the Github release page is now correct. But someone else probably should check it...

Looks good to me. Thanks!

[Ingwe Ingweron]

All right, the macOS .dmg file on the Github release page is now correct. But someone else probably should check it...

But still not updated on the main rephial.org page or available on angband.live. Any reason it's only released to those aware through the forum, but not to the public?

[Sky]

is anyone else having massive lag issues??

[Nick]

But still not updated on the main rephial.org page or available on angband.live. Any reason it's only released to those aware through the forum, but not to the public?

There were some, ah, technical issues with the release.

[Archenoth]

A little late, but heck yeah! Congratulations on the release.

The Blackguard changes look super-fun, and I think my next character will have to be one of those to try it out~

[Nick]

4.2.1 is up on angband.live now; no news on rephial yet.

[Sky]

any acknowledgment of the lag on this last release? am i the only one experiencing it. i'm talking game-crippling lag, not "barely noticeable".
seems to be attached to light, because whenever a mob casts darkness, it really slows down. Also any sleeping / within-waking-distance mob affects it. Mobs otherwise awake and moving do not seem to, instead.

[Nick]

any acknowledgment of the lag on this last release? am i the only one experiencing it. i'm talking game-crippling lag, not "barely noticeable".
seems to be attached to light, because whenever a mob casts darkness, it really slows down. Also any sleeping / within-waking-distance mob affects it. Mobs otherwise awake and moving do not seem to, instead.

I haven't seen it, but haven't really tested fir it thoroughly either. Anyone else?

[jevansau]

I've seen this at times, but not been sure as to the triggers for it.
To me it looks like each visible creature flickers at least once per player move.
It isn't noticeable every time I see sleeping creatures, but when it happens, it is extremely annoying.

[geoff_tewierik]

I haven't noticed any lag as yet, but I've only done one run through with Pike and he decided that reading three Deep Descents in a row was a bit too deep (1350ft) for his low CL 11 and carcked it.