Bugs and issues in 4.1.1

[Nick]

Nah, this latest nightly is a bit unstable, but most times the nightlies are improvements. Nick does a great job. I think he just tempted the RNG gods when he said this was ready to be 4.2....

4.1.2, 4.2 is still a long way off.

I've done a little testing and had one crash - looked mimic-related. Sounds like they shouldn't be too hard to generate

[Ingwe Ingweron]

Looks like I'm right to still be using 4.1.0....

Nah, this latest nightly is a bit unstable, but most times the nightlies are improvements. Nick does a great job. I think he just tempted the RNG gods when he said this was ready to be 4.2....

[Pete Mack]

Looks like I'm right to still be using 4.1.0....

[Ingwe Ingweron]

My guess is that this is from the change to slays/brands. Any more detail about what is happening when it crashes - player hitting/shooting/throwing at a monster?

The type of blow doesn't seem to be a deciding factor. Usually, it occurs on a monster's death, but sometimes, seemingly on movement of a monster.

Ugh, it's not only crashing during combat, but also sometimes on level arrival after reading ?Deep Descent or descending stairs.

[Nick]

Unfortunately, this latest nightly has intermittent crashes during combat. Haven't gotten something easily duplicatable, so no savefile yet.

My guess is that this is from the change to slays/brands. Any more detail about what is happening when it crashes - player hitting/shooting/throwing at a monster?

[Ingwe Ingweron]

I believe the only outstanding issue is whether changes are needed to store pricing, and my current feeling is it's good enough for now. So I am regarding this as ready to release as 4.1.2; please let me know if you find anything which contradicts that.

Unfortunately, this latest nightly has intermittent crashes during combat. Haven't gotten something easily duplicatable, so no savefile yet.

[Nick]

New builds are now up on the nightlies page, with the following changes:

• Game no longer crashes when you inspect a weapon
• Superior brands and slays on equipment no longer get overwritten by inferior ones on weapons (or later in the equipment)
• Unknown artifacts no longer leak information on inspection from a distance
• Jewellery flavours are now identified once all standard runes are known - no need to know the activation or curses

I believe the only outstanding issue is whether changes are needed to store pricing, and my current feeling is it's good enough for now. So I am regarding this as ready to release as 4.1.2; please let me know if you find anything which contradicts that.

[Nick]

hmm.. that build on the nightlies crashes when i inspect my weapon. can we replace it with a playable build?

The one before it is probably OK, or I should have a non-crashing build up tomorrow.

[Sky]

hmm.. that build on the nightlies crashes when i inspect my weapon. can we replace it with a playable build?

[Sky]

so, this is how it ends. the machines have taken over.

[Nick]

so .. i'm a bit confused.
i always play the latest build, according to http://buildbot.rephial.org/builds/master/?C=M;O=D
i assumed that these would have every previous bug fixed?

That is the natural thing to think, but in fact you're better using the nightlies page.

The reason for this is that buildbot has started randomly building old versions for no good reason, and so the latest build is no longer necessarily the most recent source. I'll have more of a look at this.

[Sky]

so .. i'm a bit confused.
i always play the latest build, according to http://buildbot.rephial.org/builds/master/?C=M;O=D
i assumed that these would have every previous bug fixed?

[Nick]

angband-4.1.0-86-g5766a6b9, the level at which i recall seems to be completely arbitrary. from DL32 back to DL13.

yes, i do pay attention to the "set recall" message.

Yes, this was fixed immediately after 4.1.1. I'm (still) hoping to get 4.1.2 out soon.

[Sky]

angband-4.1.0-86-g5766a6b9, the level at which i recall seems to be completely arbitrary. from DL32 back to DL13.

yes, i do pay attention to the "set recall" message.

[Nick]

Inspecting any weapon or digger crashes the game. I don't see anything wrong in the code, except maybe using an uninitialized state in obj_known_digging() when calling calc_bonuses().

Yep, that's it.