Angband 4.0.2 released

[Nomad]

Could that cause this?

It really shouldn't, but I have no clue what else would either. Let us know if you see this sort of thing again, and in what circumstances.

Playing 4.0.2 on Windows with tiles, I've seen @ double up a couple of times when a pseudo-ID message interrupts running. (It doesn't seem to happen every time - possibly it only occurs when @ is about to run off the edge of the screen and trigger a map redraw?)

I believe pseudo is supposed to completely interrupt running and cause @ to stop in the square that the pseudo message triggered, but what I'm getting when this bug occurs is a temporary interrupt: running is paused until I press a key to clear the message bar, and during that pause, @'s current position on the screen is overlaid with @'s future position (the square that @ would have come to a natural stop in if running hadn't been interrupted). After I press a key to clear the message, the duplicate @ disappears and @ starts running again.

Basically, imagine @ is about to run off the right-hand edge of the screen here:

[tt]A.
[bc=black][color=white]                          
                  ####### 
                  .<...@. 
                  ####### 
                          
                          
                          
                          
                          
[/color][/bc][/tt]

causing the map to scroll sideways and update to this:

[tt]B.
[bc=black][color=white]                          
########                  
.......#                  
######.#                  
     #.#                  
     #.#                  
     #.###                
     #..@:                
     #####                
[/color][/bc][/tt]

When a pseudo-ID message interrupts that running path, I actually see this:

[tt][bc=black][color=white]                          
########          ####### 
.......#          .<...@. 
######.#          ####### 
     #.#                  
     #.#                  
     #.###                
     #..@:                
     #####                
[/color][/bc][/tt]

Until I press a key to clear it, and then @ gets running again and continues on to position B.

ETA: it's not just pseudo-ID - I just had the same effect occur with a level feeling message, so presumably any sort of message interrupting running could cause this.

[Thraalbee]

No, this is a side effect of the fact that randarts are generated from the previous set, not the standarts. That is really a bug, and I may do a fix for it for 4.0.3 if and when that happens, but randarts need to be overhauled anyway for 4.1. So we'll see what happens.

Ok, No problem.
I found another issue with randarts. Max Level should always be >= Min Level

the Short Sword of Turufin (1d7) (-12,-12)
------------------------------------------
Heavily cursed.
Branded with cold.
Cannot be harmed by acid.
Grants telepathy.  Drains experience.  


Min Level 13, Max Level 7, Generation chance 5, Power -9, 8.0 lbs
Based on Turufin.

[Derakon]

Ok, No problem.
I found another issue with randarts. Max Level should always be >= Min Level

That tends to happen with cursed randarts; it's definitely not new with 4.x.

I mean, doesn't mean it shouldn't be fixed, just pointing that out.

[Nick]

Playing 4.0.2 on Windows with tiles, I've seen @ double up a couple of times when a pseudo-ID message interrupts running.

Great, thanks.

[Tarrasque]

Let us know if you see this sort of thing again, and in what circumstances.

Here's the save I used for the screenshots. The sling on the floor blocks running, so I stand on it and run to the right, but I get the same effect running back the other way and whenever @ continues running past the edge of the screen. I turned down the animation speed to 10 fps for the screenshots.

I also have a bug where the game hangs and crashes whenever I use the keyboard shortcut to quit (Cmd-Q) instead of using the menu with the mouse. I've attached the crash report for that as well.

[Nick]

I also have a bug where the game hangs and crashes whenever I use the keyboard shortcut to quit (Cmd-Q) instead of using the menu with the mouse. I've attached the crash report for that as well.

I can confirm this - current workaround is to use Ctrl-X instead

[Nivra]

I can confirm this - current workaround is to use Ctrl-X instead

Any luck on tracking down the other OS X crashes? Subwindow-triggered or trap-triggered?

I've been running into them more often in 4.0.2(it seems).

[Zikke]

Poking back in here to see the news on 4.1. Were the level feeling changes from 4.0.2? Or earlier?

[Nick]

Poking back in here to see the news on 4.1. Were the level feeling changes from 4.0.2? Or earlier?

The split monster/treasure feeling happened in 3.3, I believe.

As for 4.1, it has mostly been bugfixing of 4.0 so far, but I'm hoping to get 4.0.3 out the door fairly soon and spend more time implementing actual changes.

[Nomad]

The split monster/treasure feeling happened in 3.3, I believe.

The on-screen indicator for level feelings was new for 4.0, though. (Well, it was included in the 3.5.1 bugfix, but not the main release of 3.5.)

[Zikke]

The on-screen indicator for level feelings was new for 4.0, though. (Well, it was included in the 3.5.1 bugfix, but not the main release of 3.5.)

Ah thank you. I see it in the corner of the new screens, but it's just a number and another number. Wasn't sure what the scale is or which one is which without a label or something.