Most annoying bugs

[Philip]

One thing that's not a bug that annoys me sometimes is getting woken up from my rest for every little disturbance message. If a buff wears off, or an item recharges, I sometimes have to R& several times to get to full. I'd prefer that if there's no enemies in line of sight, it completes the rest to full and then displays the messages afterward, rather than waking me up from a nice nap for every little thing.

That could be tough to change, sometimes I want to be woken up for an item recharge, because it could be an ability I want to use. Perhaps there could be two forms of resting, one of which would disturb for monsters appearing in line of sight, one with disturbance settings as normal.

[Raajaton]

One thing that's not a bug that annoys me sometimes is getting woken up from my rest for every little disturbance message. If a buff wears off, or an item recharges, I sometimes have to R& several times to get to full. I'd prefer that if there's no enemies in line of sight, it completes the rest to full and then displays the messages afterward, rather than waking me up from a nice nap for every little thing.

[fizzix]

You have destroyed the Mithril golem.
You have found 46 gold pieces worth of mithril.

It is 'a massive statue of purest mithril. It looks expensive!'

I want to be able to drag its corpse back to the surface and sell it to the fresh meat counter at the general store.

The new drop profiles can fix this! I'll try to submit a pull request for it tonight.

[half]

Or it was Fool's Mithril.

= Silver.

..........

[Nick]

Lol.
Must have been hollow.

Or it was Fool's Mithril.

[MattB]

You have destroyed the Mithril golem.
You have found 46 gold pieces worth of mithril.

It is 'a massive statue of purest mithril. It looks expensive!'

I want to be able to drag its corpse back to the surface and sell it to the fresh meat counter at the general store.

Lol.
Must have been hollow.

[MattB]

Squishtinctions: Dont really care what material armor is made of (why do you ?)

Well at the moment my character would be quite chuffed with an average set of ribbed plate, but soft leather would have to be plus *lots* for me to not just drop it back on the ground (in which case it would probably be at least ego anyway).
Basically it would distinguish the first and worse half of the armour sets from the second, better half. That's all.

Agree with you about caestus - missed that one off my list.

[scud]

You have destroyed the Mithril golem.
You have found 46 gold pieces worth of mithril.

It is 'a massive statue of purest mithril. It looks expensive!'

I want to be able to drag its corpse back to the surface and sell it to the fresh meat counter at the general store.

[MattB]

Some of this is achievable by autoinscription: in mid game I squelch all non-artifact armour other than adamantine and the better DSMs, which I autoinscribe with '!d' (meaning you need to confirm the drop, but once it's dropped it's squelched). Ditto blades of chaos and über-maces/scythes.

The one drawback is that you need to have encountered the item type before you can set the inscription, so you need to keep a close eye out for that elusive PDSM.

Ammo doesn't offer the same distinctions, sadly, so you have to discard those 'ego' 1d4 arrows manually.

Thanks Scud, I really should get to grips with autoinscription (at the moment I just use @q1 etc., etc..
However it would be a lot easier if there were just another 4 or 5 lines on the squelch menu, IMHO.

[scud]

1> Squishtinctions
I too would like to see more options on the quality squelch menu. Especially leather body armour/metal body armour; standard arrows/better arrows (e.g. mithril and seeker, same for bolts); seperate category for uber weapons, e.g. scythe of slicing, mace of disruption.

Some of this is achievable by autoinscription: in mid game I squelch all non-artifact armour other than adamantine and the better DSMs, which I autoinscribe with '!d' (meaning you need to confirm the drop, but once it's dropped it's squelched). Ditto blades of chaos and über-maces/scythes.

The one drawback is that you need to have encountered the item type before you can set the inscription, so you need to keep a close eye out for that elusive PDSM.

Ammo doesn't offer the same distinctions, sadly, so you have to discard those 'ego' 1d4 arrows manually.

Is the issue about the fancy dragon scale mails being squelched as good armors already fixed in 3.4. ? (playing 3.3.2. and just lost a law dragon one in spite of being aware of the issue)

I'm also a 3.3.2 player... is there a specific problem with Law DSM that I haven't noticed before? This is with squelch set to 'average'...

[Estie]

Squishtinctions: Dont really care what material armor is made of (why do you ?), but the one remaining thing that could use its own class is caestus. Similar to elven cloaks, they have that combat bonus so I often want to squelsh good gloves, but not caesti.

Running interrupt: just recently I was pondering if there was a way to have buried treasure make me stop. Normally it does not for me, but playing with no selling option, I often want to dig them out if I happen to have an easy way of doing so (str or spell). The amount found is substantial.
But that means there must be a way of changing wether treasure stops or not. Someone knowledgeable explain please.

[MattB]

Most of the list I have never seen, don't understand or don't care about.
Only these three have any relevance to me:
1718, 1725 and 1733
That's hellhounds, menu overwrite and stacking.
The stacking thing does annoy me. If I have, say, 28 average arrows and pick up a stack of 20, I will usually drop 8 of them. At this stage my quiver shows 2 stacks of 20 instead of 1 stack of 40. Obviously this doesn't matter at all, but it makes my OCD all itchy so I have to drop one stack of 20 and them run over it to auto-pickup, which then combines the two and I can relax again!

Going off menu, there are a couple of minor things which I would like to see changed (although they don't fall under the description of bugs, so apologies if I shouldn't bring them up here):

1> Squishtinctions
I too would like to see more options on the quality squelch menu. Especially leather body armour/metal body armour; standard arrows/better arrows (e.g. mithril and seeker, same for bolts); seperate category for uber weapons, e.g. scythe of slicing, mace of disruption.

2> Running interrupt
I would dearly like an option to stop buried treasure interrupting my morning jog. Usually there's a pretty narrow window when you're interested in mining - namely between when you're strong enough for it not to take forever and when money doesn't matter anymore. It's a bit daft for a character with a million in the bank to stop fleeing from Ancalagon and go 'Oooh look, there might be 57 worth of copper in this seam!', unless he's a dwarf, of course.

3> Immunity message
When you're immune to, say, fire and you get breathed on by a fire vortex it says something like 'You are hit by fire. You resist the effect.' Shouldn't it say something like 'You are hit by fire. You ignore the attack'?

Having said that, it took me ages to think of three things because the game is so fantastic and polished already. Well done devs and THANK YOU!

[Timo Pietilä]

For me it's the cavern bug that causes the display to freak out and seemingly replicate when reaching the southern border of caverns. Has been referred to as "secret multiplayer mode" in other posts.

That's the post I was talking about. I see that same bug in overhead view term window. At least I think it is the same bug.

[scud]

I think the suggested fix was that dragon scale armors should be a different category than regular armor

Which I'm absolutely convinced used to be the case, just as there are 'cloak' and 'elven cloak' squishtinctions.

[quarague]

Is the issue about the fancy dragon scale mails being squelched as good armors already fixed in 3.4. ? (playing 3.3.2. and just lost a law dragon one in spite of being aware of the issue) I think the suggested fix was that dragon scale armors should be a different category than regular armor but I can't recall whether that was already resolved in 3.4. or whether it is still on the desired feature list.