4.0.3 bugs

[Derakon]

At some stage lava will get interesting - probably by causing fire damage to monsters/player walking on it.

Buck the trend of lava as a simple damage field! Have the intense heat from magma deal damage to things adjacent to it (which should probably be denoted as a superheated tile somehow), and the massive wind created by the temperature differential should deflect projectiles and spells that pass near it.

[Nick]

I updated to 4.0.3 just now. I just noticed something and I wonder whether it's deliberate?

When I recall to a level and then try to go upstairs, the game won't let me That goes for both stairs created by the game and those magically created by me.

I don't suppose you still have a savefile for this, do you? I can't immediately reproduce the problem.

[Nick]

Since we are speaking about the lava pockets in town: do they have a gameplay effect that I haven't figured out yet, or are they just isomorphic to permawalls? Even with fire immunity I cannot walk into them.

No, currently they are equivalent to permawalls - they were mainly included in 4.0 as a small advertisement of changes to come (and to add to the sense of doom in the town).

At some stage lava will get interesting - probably by causing fire damage to monsters/player walking on it.

[fph]

Since we are speaking about the lava pockets in town: do they have a gameplay effect that I haven't figured out yet, or are they just isomorphic to permawalls? Even with fire immunity I cannot walk into them.

[Nick]

I can reproduce this. Windows version.
Generate a new character.
Load a pref file with auto-inscriptions.
Quit the Character; the Word of Recall scroll gets auto-inscribed.
Generate Object spoilers (a). Infinite loop.

Thanks, got it.

[Ingwe Ingweron]

The lava pockets around the town are interesting... where did that come from, exactly?

The lava pockets in the town are the first of experiments introducing new "terrain" features. In some future version we may hope to see lava, water, trees, forests, etc., in and around the dungeon. Check out FAAngband (also maintained by Nick) for an idea of what those might be like.

[fph]

(Nothing prevents you from running an outdated 3.5.0 version and finish playing your character, though.)

[gglibertine]

4.0 represents a major code reconstruction (and major improvement for the future of the game).

Oh, it's very nice (though I'm having a rough time adjusting to the use of the pipe for the quiver on my annoying British keyboard). And I managed to quickly kill the unsaveable character anyway. The lava pockets around the town are interesting... where did that come from, exactly?

(Note to self: look for online source of cheap American-layout keyboards.)

[Ingwe Ingweron]

Well, POO.

4.0 represents a major code reconstruction (and major improvement for the future of the game).

[gglibertine]

Well, POO.

[AnonymousHero]

I just tried opening a 3.5.0 savefile in 4.0.3 and I get the following error message: "Savefile block can't be read." I don't see anything obvious in the release notes -- will I need to download an intermediate release to open savefiles from 3.5.0?

ETA: Worse yet, 3.5.0 will open the savefile, but says "Failed" every time I try to save it.

3.x savefiles are not compatible with 4.x. Not even close .

[gglibertine]

I just tried opening a 3.5.0 savefile in 4.0.3 and I get the following error message: "Savefile block can't be read." I don't see anything obvious in the release notes -- will I need to download an intermediate release to open savefiles from 3.5.0?

ETA: Worse yet, 3.5.0 will open the savefile, but says "Failed" every time I try to save it.

[Werbaer]

I ^C'd a character, and tried to generate object spoilers from the tombstone screen.
The game proceeded to show messages of "auto-inscribed a scroll of recall," auto-inscribed a scroll of phase doc," "auto-inscribed a scroll of identify" ad infinitum, without ever returning me to the tombstone screen. The only way out of this is to force-kill the application.

I can't reproduce this - looks like it's related to something character-specific. Did the character have auto-inscriptions for those, or any other, items? And what platform are you on?

I can reproduce this. Windows version.
Generate a new character.
Load a pref file with auto-inscriptions.
Quit the Character; the Word of Recall scroll gets auto-inscribed.
Generate Object spoilers (a). Infinite loop.

[Nick]

I originally filed this under the 4.0.2 bug thread, but it seems to have gone unfixed in 4.0.3, so here goes.

I ^C'd a character, and tried to generate object spoilers from the tombstone screen.
The game proceeded to show messages of "auto-inscribed a scroll of recall," auto-inscribed a scroll of phase doc," "auto-inscribed a scroll of identify" ad infinitum, without ever returning me to the tombstone screen. The only way out of this is to force-kill the application.

Other observations:

• It seems to be looping through the three scroll auto-inscribes I have defined. The auto-inscribes for staves, rods, wands and spell books never seem to come up.
• The bug is triggered regardless of whether I actually have the scrolls in inventory, and is 100% reproducible.
• It is only the object spoiler generation that is affected; other spoilers seem to complete with no problem.
• The object.spo file does get generated prior to the app entering the infinite message loop.

I can't reproduce this - looks like it's related to something character-specific. Did the character have auto-inscriptions for those, or any other, items? And what platform are you on?

[zog]

spoiler generation bug (OS X)

I originally filed this under the 4.0.2 bug thread, but it seems to have gone unfixed in 4.0.3, so here goes.

I ^C'd a character, and tried to generate object spoilers from the tombstone screen.
The game proceeded to show messages of "auto-inscribed a scroll of recall," auto-inscribed a scroll of phase doc," "auto-inscribed a scroll of identify" ad infinitum, without ever returning me to the tombstone screen. The only way out of this is to force-kill the application.

Other observations:

• It seems to be looping through the three scroll auto-inscribes I have defined. The auto-inscribes for staves, rods, wands and spell books never seem to come up.
• The bug is triggered regardless of whether I actually have the scrolls in inventory, and is 100% reproducible.
• It is only the object spoiler generation that is affected; other spoilers seem to complete with no problem.
• The object.spo file does get generated prior to the app entering the infinite message loop.