Angband 4.0 beta release

[Nick]

Originally Posted by PowerWyrm

Terse mode doesn't show terse info.

bool terse = (mode & ODESC_TERSE);

Tested in debug mode, the "mode" flag contains "ODESC_TERSE", the boolean value is set to FALSE. This is because unary operators don't return a boolean value. So the correct code is:

bool terse = (mode & ODESC_TERSE)? TRUE: FALSE;

There are a LOT of such declarations in the code. It's probably a good time to fix them all...

Thanks. Mercifully the actual setting of booleans like this seems to be confined to obj-desc and obj-info - there's a lot of use of things like (mode & ODESC_TERSE) in conditionals, which should be fine.

[Nick]

Update bdd602d:

• Makes a lot of PowerWyrm's suggested fixes to ID
• Fixes some bad object names and descriptions (PowerWyrm again)
• Fixes the bug where immunities were broken, which actually broke a whole lot of resistance-related stuff

Please report wherever ID and anything involving balls, bolts and breaths hitting the player seems not to be working.

[Thraalbee]

Originally Posted by Nick

Update bdd602d:

• Makes a lot of PowerWyrm's suggested fixes to ID
• Fixes some bad object names and descriptions (PowerWyrm again)
• Fixes the bug where immunities were broken, which actually broke a whole lot of resistance-related stuff

Please report wherever ID and anything involving balls, bolts and breaths hitting the player seems not to be working.

When finding rings of known type the message is not as before. You get this also in the item list even before picking it up.
You see a Ring of Reckless attacks {worn}
You see a Ring of the Mouse {worn}
You see a Ring of Protection {worn}

[Nick]

Originally Posted by Thraalbeast

When finding rings of known type the message is not as before. You get this also in the item list even before picking it up.
You see a Ring of Reckless attacks {worn}
You see a Ring of the Mouse {worn}
You see a Ring of Protection {worn}

Thanks - that's an easy fix.

[Thraalbee]

Today's release. Rogue L30, insane amount of armour (AC170). SP = 4/4 in main screen but Character Screen with "C" (roguelike) says SP = 0/0. And I can't cast any spells, so the character screen seems correct.

[passer_by]

I was finding that my mage's SP was usually set to 0 every time I reloaded a savefile. Looks like the problem is that max SP is sometimes calculated with an uninitialised INT of zero. I think this fix does what was intended:

--- a/src/player-calcs.c
+++ b/src/player-calcs.c
@@ -1296,10 +1296,10 @@ static void calc_spells(struct player *p)
 /**
  * Get the player's max spell points per effective level
  */
-int mana_per_level(struct player *p)
+int mana_per_level(struct player *p, struct player_state *state)
 {
        int stat = p->class->magic.spell_realm->stat;
-       return adj_mag_mana[p->state.stat_ind[stat]];
+       return adj_mag_mana[state->stat_ind[stat]];
 }
 
 /**
@@ -1326,7 +1326,7 @@ static void calc_mana(struct player *p, struct player_state *state)
        levels = (p->lev - p->class->magic.spell_first) + 1;
        if (levels > 0) {
                msp = 1;
-               msp += mana_per_level(p) * levels / 100;
+               msp += mana_per_level(p, state) * levels / 100;
        } else {
                levels = 0;
                msp = 0;

[Nomad]

There seems to be an issue with the randomly positioned doors not always being generated correctly for templated rooms, causing the generation process to make a break in the wall. For instance, I've just come across this:

                         
 ####################### 
 #.....................# 
 #.#.#.###.###.#.#.###.# 
 #.#.#.#.'.#.'.#.#.#.'.# 
 #.###.###.###.###.###.# 
 #.....................# 
 #.###.###.#.#.###.###.# 
 #.'.#.'.#.#.#.'.#.'.#.# 
 #.###.###.###.###.###.# 
 #.....................# 
 ####################### 
                         

Which is seemingly supposed to be this layout with the doors in position 3:

D:%%%%%%%%%%%%%%%%%%%%%%%
D:%.....................%
D:%.#2#.#2#.#2#.#2#.#2#.%
D:%.1.391.3.193.1.391.3.%
D:%.#4#.#4#.#4#.#4#.#4#.%
D:%.....................%
D:%.#4#.#4#.#4#.#4#.#4#.%
D:%.3.193.1.391.3.193.1.%
D:%.#2#.#2#.#2#.#2#.#2#.%
D:%.....................%
D:%%%%%%%%%%%%%%%%%%%%%%%

Judging by the pattern of which doors are missing, I'm going to take a stab that the problem is with where the symbols used in room_template.txt have been semi-standardised with vault symbols, and the "place some monsters and treasures nearby" symbol, (previously !) has been changed to a number 9. It looks like the code is possibly reading 3-followed-by-9 as 39 and failing to place a door because it doesn't recognise it's a 3, or something similar.

[Thraalbee]

When my Rogue switches back and forth between super heavy armour (AC 102 adamantite plate) and leather, not only is the SP display incorrect. Also the AC is not always updated correctly, the old values remain even after switch. I will make a copy of the savefile if it turns out to be hard to reproduce.

[Nick]

Originally Posted by Nomad

Judging by the pattern of which doors are missing, I'm going to take a stab that the problem is with where the symbols used in room_template.txt have been semi-standardised with vault symbols, and the "place some monsters and treasures nearby" symbol, (previously !) has been changed to a number 9. It looks like the code is possibly reading 3-followed-by-9 as 39 and failing to place a door because it doesn't recognise it's a 3, or something similar.

Nice guess, but I don't think that's the problem - but I have no idea what the problem actually is, and I'm often wrong. Please keep an eye out for other malformed template rooms that might give clues.

[Nomad]

Originally Posted by Nomad

Judging by the pattern of which doors are missing, I'm going to take a stab that the problem is with where the symbols used in room_template.txt have been semi-standardised with vault symbols, and the "place some monsters and treasures nearby" symbol, (previously !) has been changed to a number 9. It looks like the code is possibly reading 3-followed-by-9 as 39 and failing to place a door because it doesn't recognise it's a 3, or something similar.

Well, the initial example I was actually going to post was this one:

                 
 ############### 
 #.............# 
 #.#.###.#####.# 
 #.#...#.#...#.# 
 #.#...#.'...#.# 
 #.#...#.#...#.# 
 #.#####.#####.# 
 #.............# 
 ############### 
                 

Which follows the exact same pattern.

D:%%%%%%%%%%%%%%%
D:%.............%
D:%.##2##.##4##.%
D:%.#...#.#...#.%
D:%.1...393...1.%
D:%.#...#.#...#.%
D:%.##4##.##2##.%
D:%.............%
D:%%%%%%%%%%%%%%%

I actually specifically scummed for the "Ten little boxes" layout because I remembered seeing one with broken walls before and wanted to see if it bore out my hunch that it was happening in the same situation with the 9s - which it did - and I thought it would make a more illustrative example. (Although from if the code hasn't changed from before, I don't really see how it actually could be reading the two numbers together instead of taking them one at a time - but I confess I'm baffled as to why it follows so predictable a pattern otherwise.)

I'll keep an eye out for any more examples...