Angband 4.0 beta release

[Nick]

Update 5a6bbf0 fixes

• Spell effect duration typos (thanks PowerWyrm)
• Issues of *slays* not being counted in object power, and slay cache errors (PowerWyrm again)
• Randart activations are back to normal (ie no remove curse with a zillion turn recharge)
• Ring of Power name in randart sets sensible again
• "Arkenstone with light radius 0" problem fixed - it was in fact preventing randarts from having any multiple modifiers (STR & WIS, etc)

As far as I know there are no outstanding issues with randarts - please let me know if any others turn up.

[Nomad]

If you stand adjacent to a floor item and run in its direction, instead of moving one square and stopping on top of the item (previous behaviour), you now run two squares and stop in the next square beyond the item. Most significantly, this can cause you to accidentally 'leapfrog' one square outside the trap-detected area if there's an item lying on the detection border.

(I know it's fairly silly and pointless to be using the run command to move a single square anyway, but I tend to just hold shift and keep tapping arrows if I want to run past several obstacles, rather than bother switching back and forth between run and walk.)

[PowerWyrm]

Angband 4.0 dev aa62c4d

Boulders thrown by Bert, the Stone Troll from just out of sight resulted in the message, "You are hit by something sharp". I don't remember boulders being sharp before.

It's been the case since forever. Maybe juast change the message to "something hard" like for force breaths.

[Thraalbee]

the (LOST) tag on artifacts in char history seems to be broken or disabled

[Nomad]

Thanks for all the latest fixes! Especially the ones for my tileset. I'll play some randart games and see how the results look now.

Also, I see from the ticket for #1889, the "Darkness breath removes wall knowledge" bug that people are having difficulty confirming it, so I should volunteer that I get it too, but it only happens if you're standing inside a defined room, not a corridor. (Also, you don't have to wait for a darkness breather, a Scroll or Staff of Darkness will cause the same effect.)

[Ingwe Ingweron]

Angband 4.0 dev aa62c4d

Finally, @ has ESP (in the form of Dor-Lomin, which is fantastic!) So, here is an apparent pathing problem. If @ just moves back and forth, the Ancient Blue Dragon doesn't come up to get him. There is no rubble blocking the D's path. Tester.zip

[Ingwe Ingweron]

Angband 4.0 dev aa62c4d

Boulders thrown by Bert, the Stone Troll from just out of sight resulted in the message, "You are hit by something sharp". I don't remember boulders being sharp before.

[Ingwe Ingweron]

Angband 4.0 dev aa62c4d

Was able to find another almost identical situation with a ring of digging which causes a replicable crash bug. Wielding a ring of digging from off the floor (not to be confused with the one in @'s pack). "[w]ield" "-"floor "a" item "d" right ring slot "CRASH". If instead @ simply picks up the ring, it is auto-id as a Ring of Digging <+5> and added to the one in @'s pack. Tester.zip

This is using OSX, so like the previous crash bugs I've submitted, it might not crash on other platforms.

[Nick]

Update aa62c4d fixes:

• Brands and slays on randarts (at least partially - there are other randart issues)
• Typos in Nomad's tileset
• Gap between bottom of inventory and quiver contents lines
• Arrows now cycle completely between equipment, inventory, quiver and floor in object selection menus
• Cheat option is now 'x', so as not to conflict with 'c' for edit colours

[Nick]

Nick, please let me know if I should keep submitting these savefiles when I find a replicable crash. I have no idea if it's helpful to you and the rest of the dev team.

EDIT: If instead @ simply picks up the ring, it is auto-id as a Ring of Digging <+5> and added to the one in @'s pack.

Yes, please do - you never know when one of them is going to make the penny drop.

[Ingwe Ingweron]

It is useful to submit the bugs. Unfortunately, this one doesn't crash on windows either!

Bill Gates would be happy.

[fizzix]

Angband 4.0 dev 9f6ea01

And another replicable crash bug. This one simply wielding a ring of digging from off the floor (not to be confused with the one in @'s pack). "[w]ield" "-"floor "a" item "d" right ring slot "CRASH". [ATTACH]1215[/ATTACH]

This is using OSX, so like the previous crash bugs I've submitted, it might not crash on other platforms.

Nick, please let me know if I should keep submitting these savefiles when I find a replicable crash. I have no idea if it's helpful to you and the rest of the dev team.

EDIT: If instead @ simply picks up the ring, it is auto-id as a Ring of Digging <+5> and added to the one in @'s pack.

It is useful to submit the bugs. Unfortunately, this one doesn't crash on windows either!

[Ingwe Ingweron]

Angband 4.0 dev 9f6ea01

And another replicable crash bug. This one simply wielding a ring of digging from off the floor (not to be confused with the one in @'s pack). "[w]ield" "-"floor "a" item "d" right ring slot "CRASH". Tester.zip

This is using OSX, so like the previous crash bugs I've submitted, it might not crash on other platforms.

Nick, please let me know if I should keep submitting these savefiles when I find a replicable crash. I have no idea if it's helpful to you and the rest of the dev team.

EDIT: If instead @ simply picks up the ring, it is auto-id as a Ring of Digging <+5> and added to the one in @'s pack.

[Ingwe Ingweron]

Angband 4.0 dev 9f6ea01

Just got another example of the "run past" bug. @ was fighting a Greater Basilisk in a long north-south hallway. Swinging away from the south, suddenly @ was on the other side of the Greater Basilisk. There was no room to slip past in the hallway and @ wasn't teleported there. Ah, well, this is new behavior. @ just continued swinging away from the north until the monster died.

[fizzix]

Well, damn. I just deleted Angband and redownloaded it, then downloaded the save file I'd submitted, unzipped it and placed it in the Angband save directory, opened the file in Angband, and did the sequence of f1*t (1st shot successful against Medusa) n (CRASH).

Playing on a MacBook Pro using OSX Mavericks. Don't know why it didn't crash for you. With the previous battle crash savefile I submitted, Nick didn't get a crash in Windows or Linux, but did when he tried it with OSX. Don't know if the savefile was any help though in tracking down a cause.

My guess is that it's OSX specific. So I can't test it...