Angband 3.2 released!

[PowerDiver]

Was the monster at full health? The bug is perhaps that if the monster doesn't need healing, it doesn't drain. Still a bug though, IMO.

It might have been the first time, but I was meleeing with an uber-warrior, so it must have been damaged after my first round of attacks.

Perhaps I got very lucky? There doesn't have to be a bug.

[Magnate]

I noticed a possible change, but it wasn't in the log, and I'm not sure it was a change.

Does anyone know if the rules on charge draining have been modified? I was carrying some staves with charges and got "touched" perhaps 4 times by a charge draining unique before I lost any charges.

Oooh, I think that's a bug. We have an open ticket to change draining, but it's not implemented yet and it would always drain at least one charge anyway.

Was the monster at full health? The bug is perhaps that if the monster doesn't need healing, it doesn't drain. Still a bug though, IMO.

[PowerDiver]

I noticed a possible change, but it wasn't in the log, and I'm not sure it was a change.

Does anyone know if the rules on charge draining have been modified? I was carrying some staves with charges and got "touched" perhaps 4 times by a charge draining unique before I lost any charges.

[Magnate]

Please consider changing the default "light violet" color -- I thought "purple uniques" wasn't working because I was expecting to see the same violet color that most of the uniques were in 3.1.x.

Not using that colour was a deliberate choice.

I am red/green color deficient and find the default light violet indistinguishable from grey. Something like FF30FF is much more distinct while still distinguishable from the other pink/purple colors.

That's a very helpful suggestion - thank you. I'll try that out.

I also have had some glitches with text being displayed offscreen on Windows. It seems to go away after saving/reopening, so maybe an issue with angband.ini?

Sorry, not sure about this one.

Just to clarify for all the people out there who might notice odd little visual quirks with 3.2 - there are two key issues to resolve before reporting any bugs for this type of issue:

1. Does it happen when you switch off graphical tiles and just play with ascii? Even if you never play with ascii, please check this before reporting the bug as it will be helpful in tracing it.

2. Does it happen only with any kind of "bigtile" mode (i.e. if tile_width or tile_height > 1), or does it happen with normal-sized tiles? Again, it will be very helpful if you can answer this for us.

Thanks.

[awldune]

Glad it's sorted now - admittedly the "light violet" isn't the most striking colour. But you can intensify it by going to the "interact with colours" option in the options menu and changing the RGB values if you want.

Please consider changing the default "light violet" color -- I thought "purple uniques" wasn't working because I was expecting to see the same violet color that most of the uniques were in 3.1.x.

I am red/green color deficient and find the default light violet indistinguishable from grey. Something like FF30FF is much more distinct while still distinguishable from the other pink/purple colors.

Thanks!

I also have had some glitches with text being displayed offscreen on Windows. It seems to go away after saving/reopening, so maybe an issue with angband.ini?

Otherwise I am excited about the feature changes and look forward to trying out 3.2 some more.

[d_m]

I'm enjoying 3.2, but I'm getting an annoying crash (running Mac OS X 10.6).

Ouch!

I will definitely take a look at this as soon as I can.

Seems like we might need 3.2.1 sooner than we thought :P

[juggle5]

I'm enjoying 3.2, but I'm getting an annoying crash (running Mac OS X 10.6).

I'm using the roguelike keyset, and have my magic books inscribed as @1, @2, etc. If I type 'm 2' to cast a spell from the second book, the game crashes, though typing 'm b' works fine, as does 'm 1' (to cast from the first book).

I've attached my save file (compressed).

Here's the information from gdb:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000008
0x0000ab87 in cmd_lookup ()
(gdb) bt
#0  0x0000ab87 in cmd_lookup ()
#1  0x0005f83b in get_item ()
#2  0x0009be86 in textui_obj_cast ()
#3  0x0000b2d7 in textui_process_command ()
#4  0x000aa4fe in textui_get_cmd ()
#5  0x000b65bb in crb_get_cmd ()
#6  0x00020406 in cmd_get ()
#7  0x000209a0 in process_command ()
#8  0x00016668 in dungeon ()
#9  0x0001730a in play_game ()
#10 0x000b595f in AngbandGame ()
#11 0x9489ff2f in DispatchEventToHandlers ()
#12 0x9489f1f6 in SendEventToEventTargetInternal ()
#13 0x9489f055 in SendEventToEventTargetWithOptions ()
#14 0x948d3bb0 in ToolboxEventDispatcherHandler ()
#15 0x948a0380 in DispatchEventToHandlers ()
#16 0x9489f1f6 in SendEventToEventTargetInternal ()
#17 0x948c19bb in SendEventToEventTarget ()
#18 0x94a4acc3 in ToolboxEventDispatcher ()
#19 0x94a4adfb in RunApplicationEventLoop ()
#20 0x000b7b0d in main ()

[d_m]

Also, new bug: creating an item in wiz mode doesn't redraw the screen, even if the item is created somewhere it should be immediately visible- i.e. it's not created at the player's feet because he's standing on the stairs.

I've seen this bug before, and it's worth reporting, but I consider it a lower priority than the game play bugs that affect regular users

[pampl]

Thanks. I can't reproduce the =Dog problem - they ID fine for me. Or do you mean they don't ID by use? I can't reproduce that either - one hit and the hit/dam bonuses show up.

The other one was deliberate: it's not that to-hit penalties aren't showing, it's that they aren't there any more on ego armour. This was a while ago, but IIRC it was an unintended side-effect of the new code to check for minimum to-hit/dam bonuses on certain egos (mainly launchers of accuracy/power). There was a good thread debating it and in the end we decided we quite like the idea that ego armour had this additional small advantage. Normal and "magical" armours still have the penalties, it's only ego armour that doesn't.

I can't recreate most of the bugs I thought I was experiencing so I'll have to wait until/if they happen again and upload a save. One that I can recreate is the = of the Dog ID problem: once you recognize their flavor, they stop being a valid target for ID. ID by use still seems to work though.

Also, new bug: creating an item in wiz mode doesn't redraw the screen, even if the item is created somewhere it should be immediately visible- i.e. it's not created at the player's feet because he's standing on the stairs.

[Magnate]

I can't seem to identify = of the dog to find out their (+,+) values.. I have to sell them to learn. Also, magical armors don't display their to hit penalty. Other than that, though, great release.

Thanks. I can't reproduce the =Dog problem - they ID fine for me. Or do you mean they don't ID by use? I can't reproduce that either - one hit and the hit/dam bonuses show up.

The other one was deliberate: it's not that to-hit penalties aren't showing, it's that they aren't there any more on ego armour. This was a while ago, but IIRC it was an unintended side-effect of the new code to check for minimum to-hit/dam bonuses on certain egos (mainly launchers of accuracy/power). There was a good thread debating it and in the end we decided we quite like the idea that ego armour had this additional small advantage. Normal and "magical" armours still have the penalties, it's only ego armour that doesn't.

P.S. Since the whole issue of penalties for wearing heavy armour is on our list of things to look at, we decided it wasn't worth "fixing" this issue. After fizzix releases a playable version with the new evasion/absorption combat model, the next combat-related changes are critical hits and armour penalties ...

[Magnate]

The color option seems to work now. I found a unique and switched it off then on and he changed to pale violet. Maybe something changed on my install of Angband between yesterday and today, but now I can't replicate the problem.

Thanks for all your help, and now I look forward to pressing on into the world of randarts!

Glad it's sorted now - admittedly the "light violet" isn't the most striking colour. But you can intensify it by going to the "interact with colours" option in the options menu and changing the RGB values if you want.

[Magnate]

Hmm. I'll have to check. I just copied my 3.1.2 ini into the 3.2 folder and everything looked OK when the game started. <goes to check>

OK, using Windows (Vista), David Gervais 32x32 tiles, Double Tile and Big Tile both on. Both 'enable nice graphics' and 'bizarre display' seem to have no effect and in any case don't affect the glitch. Deleting the ini didn't help either. This glitch does not occur in ASCII mode.

The glitch (yellow box outline) only persists in the black (unexplored) areas of the map, and even then then a font sized??? (8x12???) chunk of it is missing from the upper left corner. So it appears at least part of the box is being erased.

Ok, it's a bigtile glitch - there are a bunch of these, which should be fixed in 3.3, we hope. Glitches with 1x1 tiles are a bigger worry ...

Just as the spells do, at the bottom of the list, underneath the last item. There's plenty of room, at least on my screen.

Ah, that would be difficult, since the menu code uses up all the available space on smaller main windows. Also, the object inspection code can take over 24 lines in some cases! Worth thinking about though - my suggestion would be that it appeared in the "object recall" subwindow.

At the very end of character creation there is a press "['ESC' to step back, 'S' to start over, or any other key to continue]" How about just adding "or 'B' to set birth options" to it (or =).

Yes, excellent idea - now ticket #1295.

[molotov]

The color option seems to work now. I found a unique and switched it off then on and he changed to pale violet. Maybe something changed on my install of Angband between yesterday and today, but now I can't replicate the problem.

Thanks for all your help, and now I look forward to pressing on into the world of randarts!

[Timo Pietilä]

I summoned them, and they are both light grey

That is actually "light violet". Close to light grey, but not quite. Light grey is Grip and Fang color (index 46 and 47 respectively).

I tested this and it looks like that option works in my machine. Summoned Maggot (index 4) without option set = white, with it = light violet. Actually seem to change that color in flight. Summon something like Maggot with clear difference and swap that setting. See if it changes color. If not then your machine doesn't work like mine does.

This also means that you don't necessarily need to use debug-mode, just find a unique and swap that setting to see if color changed.

[Nick]

There's a graphic glitch when 'l'ooking around when playing with 32x32 tiles. The yellow cursor box remains drawn on the screen in every place it's been, drawing and leaving behind a yellow trail in the darkness wherever it goes. Ctrl-r solves it, but...

Sorry, my bad - I thought I'd fixed that.