Bugs and issues in 4.1.0

[Sky]

Same. I do hate that it disturbs, but i find it useful to see on map exactly how far i have detected, specifically with Treasure Detection.

[PowerWyrm]

You still have the indicator. The border was visually polluting the screen (and was kinda bugged), so I can understand why it is gone.

[kaypy]

Given the current player knowledge vs actual cave implementation of V, I thought it would be much simpler to fill the knowledge map with "undetected" and overwrite it as needed, rather than trying to draw a 'line', per-se...

[luneya]

You still have the indicator. The border was visually polluting the screen (and was kinda bugged), so I can understand why it is gone.

What indication of having been covered by detection do we currently have? All I can think of is that the range of treasure detection can be approximated by looking for where the buried-gold-*s don't appear, but this doesn't really distinguish undetected tiles from those which simply don't contain gold.

[PowerWyrm]

Not really a bug, but an issue with debug commands. If you try to generate an ego for debug purposes, you are asked to enter the ego... index. Which doesn't exist anymore... Using the name instead would be more than helpful.

[PowerWyrm]

I tried to reproduce a problem with remove curse, so instead of scumming for a cursed item, I simply used the debug commands to generate a few scrolls of curse weapon and read them on an equipped mace. After two tries, I used the Perception spell twice to identify the curses and read a third scroll.

a) a Mace (2d4) (-1,-3) {cursed, ??}
     An inheritance from your family
     
     You do not know the full extent of this item's powers.
     It occasionally makes a loud noise.
     It poisons you from time to time.
     
     Combat info:
     2.8 blows/round.
     With +1 STR and +0 DEX you would get 3.1 blows
     With +0 STR and +1 DEX you would get 3.3 blows
     Average damage/round: 20.5.

At this point, using the Perception spell again on the mace does nothing. What could the {??} be?

[Nick]

I tried to reproduce a problem with remove curse, so instead of scumming for a cursed item, I simply used the debug commands to generate a few scrolls of curse weapon and read them on an equipped mace. After two tries, I used the Perception spell twice to identify the curses and read a third scroll.

a) a Mace (2d4) (-1,-3) {cursed, ??}
     An inheritance from your family
     
     You do not know the full extent of this item's powers.
     It occasionally makes a loud noise.
     It poisons you from time to time.
     
     Combat info:
     2.8 blows/round.
     With +1 STR and +0 DEX you would get 3.1 blows
     With +0 STR and +1 DEX you would get 3.3 blows
     Average damage/round: 20.5.

At this point, using the Perception spell again on the mace does nothing. What could the {??} be?

That looks odd - do you have the savefile?

[PowerWyrm]

Here's the savefile after removing the two visible curses. The character screen displays some "?" for the mace, even for stuff like ESP, which should be obviously known after removing and reequipping the mace. That's probably only some knowledge info removed by the curse weapon effect, which doesn't exist anymore unless you use the debug commands to generate some scrolls.

[PowerWyrm]

I generated a ring of feather falling with the debug commands for the same character and equipped it. Casting Perception on the ring revealed the rune of feather falling. At the same time, the {??} on the mace magically disappeared... Very strange. I tried to see if the problem was only occuring when no runes were learned, but it's not the case. I bought a weapon from a store, used a scroll of curse weapon twice on it, revealed the curses with Perception then read a third scroll. It seems that the third time, no curse is added, but the item becomes not fully known. Discovering another rune (equipped a ring of slow digestion this time) removes the problem on the weapon.

[Nick]

Here's the savefile after removing the two visible curses. The character screen displays some "?" for the mace, even for stuff like ESP, which should be obviously known after removing and reequipping the mace. That's probably only some knowledge info removed by the curse weapon effect, which doesn't exist anymore unless you use the debug commands to generate some scrolls.

Basically, yes. Curse weapon also subtracts from to-hit and to-dam, but doesn't re-align the object and its known version - you'll find if you drop the mace and pick it up again, it changes to (-3, -3) and loses the {??}.

Technically a bug, but only if curse armor and curse weapon scrolls come back into the game.

[Nick]

No idea if this is a bug or feature. Tarrasque breathes fire, then cold then disenchantment. @ doesn't take any damage from disenchantment. Player tries to figure out why for ages until he decides to press "l" and get "You are standing in a rubble." message. Not the passable version, the normal one.

That's a bug.

[Sky]

is it?

fire creates lava pools, which cold then freezes into rubble. rubble does not allow spells to pass. i don't see the bug.

[Pete Mack]

It should have the same effect as an earthquake falling on your square.

[Nick]

is it?

fire creates lava pools, which cold then freezes into rubble. rubble does not allow spells to pass. i don't see the bug.

Having terrain change so that the player (or a monster) gets left in impassable terrain should not happen. Handling like for earthquakes, as Pete suggests, seems sensible.

[Nick]

Latest build on the nightlies page makes the following changes:

• Freezing lava can not produce impassable rubble if the player or a monster is on the grid
• The darkness spell no longer results in view weirdness (#2055)
• The number of vaults has been toned down a bit (#2057) - anyone who thinks there are still too many is encouraged to play with the numbers in dungeon_profile.txt
• In persistent levels mode the player gets the choice of which level to recall to from town

A few more small bugs to clean up and some persistent levels issues to deal with, and then it should be time for 4.1.1.