Player knowledge

[Nick]

[Not sure what the "(2)" is for at the end of that message line.]

That's the quiver slot label.

[Not sure how @ knows this, since it apparently happens out of LoS.]

Well spotted - I had vaguely noticed this too, and it's a bug in 4.0.x as well as here. Monsters are picking up objects on squares they try and fail to move to.

[CRASH]

Bug found and fixed - I had overlooked one detail involving deleting objects with brands or slays.

New builds will be up before too long.

[Ingwe Ingweron]

Bugs? What bugs?

Why? Why, oh why do you tempt the Gods that way?

@ didn't get very far. Not even enough time for his fear to wear off. Currently he is being assaulted by some carrion crawlers and a master rogue. In the midst of this battle -- a replicable crash and other questions.

Fire f2 (shot of lightning) at the nearest carrion crawler ...

"Your Iron Shots of Lightning crackle! -more-
"Your Iron Shot of Lightning (1d4) (+3,+10) {@f2=g} shocks the Carrion crawler (75). -more-
"You have 15 Iron Shots of Lightning (1d4) (+3,+10) {@f2=g} (2). -more-

[Not sure what the "(2)" is for at the end of that message line.]

"You feel something roll beneath your feet. "The Carrion crawler hisses furiously. -more-
"The Carrion crawler flees in terror! -more-
"Something picks up 2 Iron Shots of Lightning (1d4) (+3,+10) {@f2=g}. -more-

[Not sure how @ knows this, since it apparently happens out of LoS.]

The Master rogue picks up 3 Rounded Pebbles of Flame (1d2) (+3,+3) {@f1=g}. -more-"

[CRASH] Blind_Bat.zip

[Nick]

Thanks, Nick. I'll continue the bug hunt tomorrow.

Forgot to mention - the shots should now identify properly on use, Turmil you will probably have to actually magically identify again, but after that IDing should all work properly.

EDIT: Bugs? What bugs?

[Ingwe Ingweron]

Once I get the current crop of bugs fixed, I can also give you a save with the staff fixed.

Thanks, Nick. I'll continue the bug hunt tomorrow.

[Nick]

Latest compiled versions now up for Windows and OS X, with all known bugs (I believe) fixed. Attached has the staff now droppable.

[Nick]

Hadn't noticed the history bug. Doesn't show the Phial or Turmil. As for the staff, I guess the only options are to start a new @ or forever carry the staff in inventory.

Once I get the current crop of bugs fixed, I can also give you a save with the staff fixed.

[Ingwe Ingweron]

....Looks like the cause of the crash was fixed in the last update, but that staff has been in the inventory since before then

...Also, the player history is a bit dismissive about your artifact finds

Hadn't noticed the history bug. Doesn't show the Phial or Turmil. As for the staff, I guess the only options are to start a new @ or forever carry the staff in inventory.

[Nick]

Replicable crash. @ is standing on an Exorcisms and Dispelling Book and has an empty staff of Detect Invisible in inventory. Drop the staff and there is an immediate crash. Note also the "special" Turmil and "splendid" ammunition with mutilple brand description, even though fully identified. [ATTACH]1338[/ATTACH]

Thanks for all your efforts on this, they are invaluable.

Those shots are hilarious

EDIT: Looks like the cause of the crash was fixed in the last update, but that staff has been in the inventory since before then

EDIT2: Also, the player history is a bit dismissive about your artifact finds

[Ingwe Ingweron]

Replicable crash. @ is standing on an Exorcisms and Dispelling Book and has an empty staff of Detect Invisible in inventory. Drop the staff and there is an immediate crash. Note also the "special" Turmil and "splendid" ammunition with mutilple brand description, even though fully identified. Blind_Bat.zip

[Ingwe Ingweron]

And another. @ just found a staff of identify (which did correctly auto-inscribe, by the way) and used it to identify Turmil, but Turmil still retains the {special} modifier and "You do not know the full extent of this item's powers." ID'd it twice, just to see if I'd screwed up somehow, but the problem remains. Everything else about the weapon was identified.

Edit: Same weirdness with some Iron Shots of Lightning. The hit and dmg modifiers are known after shooting them and that they shock non-resistant monsters, but they still have the {splendid} identifier and that the full extent of powers isn't known. Additionally, the description says, "Branded with lightning, lightning, lightning, lightning, lightning, lightning, lightning, lightning, lightning, lightning, lightning, lightning, lightning, lightning."

Yes, that's right, it lists "lightning" fourteen times!

[Ingwe Ingweron]

Another issue. The fix for the auto-inscription problem introduced another problem, now auto-inscription doesn't work at all. @ picks up the item that should receive an automatic inscription, but no inscription occurs.

Edit: More specifically, a potion of speed. It does work on a prayer book.

[Nick]

You just had to tempt the Gods, didn't you? Have had repeated crashes in melee. Not specifically replicable, but if you melee the monsters right near @ now, there is a crash at some point, usually when the multi-hued dragon breaths fire. [ATTACH]1337[/ATTACH]

Thanks. I see the problem (it's to do with the fire breath destroying an ignored torch), but need to think a bit more about the correct way to fix it.

[Ingwe Ingweron]

Must be getting close to bugfree now, surely

You just had to tempt the Gods, didn't you? Have had repeated crashes in melee. Not specifically replicable, but if you melee the monsters right near @ now, there is a crash at some point, usually when the multi-hued dragon breaths fire. Blind_Bat.zip

[Nick]

And, of course, updating leads to the finding of new bugs. So here are the latest versions for Windows and OS X. Relevant bugs were crashing (sometimes) on dropping or ignoring a dungeon item in town, and crashing or corrupting the savefile on wielding an item from a stack (like a torch).

Must be getting close to bugfree now, surely

[Nick]

OK, improved Windows and OS X builds up now, and latest source still at the same link.

Crash and autoinscription issues fixed, I think, and also some tightening up of potential crashes.