"You fail to harm the thingamy..."

[Chud]

"You fail to harm the [whatever]" -- under what circumstances should I see this message?

I have assumed it's when I hit it, but there is some modifier to damage that reduces the damage to (or below) 0. Is there another case where I'd see this? I ask because I am seeing it, and for no obvious reason that I can tell; okay weapon, no ring of the mouse or escaping or such, I'm fed, not stunned, and so on. Possibly there is such a factor that I'm just not noticing.

This might be a bug, but not sure, so I didn't include it in the bug thread. This is in the Nov 4 nightly to 4.2.0, with the experimental damage dice / O-combat option enabled.

[Ingwe Ingweron]

Is your @ stunned? Or, wearing a ring of the mouse? Just some of the things that could legitimately and easily be causing this.

[PowerWyrm]

You're definitely wearing a ring of the mouse.

[Pete Mack]

Stunned is my guess, too. Stunned melee loses both accuracy and damage, and you might get more stunned. It is a very bad deal.

[wobbly]

... no ring of the mouse or escaping or such, I'm fed, not stunned...

Are you stunned or wearing a ring of the mouse?

Now that's out of the way, str drained? shape-shifted?

I'm not sure how O-combat handles negative deadliness but I had a little try with a 5 str hobbit mage & I was still doing damage. Either there's a bug or you've got a large -dam somewhere.

[Chud]

Not shape shifted (Dwarf warrior), Dex drained a little but not Str.

Save and randarts file attached if you want to take a look.

[wobbly]

Yeah there's definitely something buggy there, possibly with the brand? It goes away when I switch to a non-branded weapon.

[wobbly]

/* Adjust the average for slays and brands. (10x inflation) */

	if (s) {

		die_average *= slays[s].o_multiplier;

		add = slays[s].o_multiplier - 10;

	} else if (b) {

		die_average *= brands[b].o_multiplier;

		add = brands[s].o_multiplier - 10;

	} else {

		die_average *= 10;

	}

add = brands[s].o_multiplier - 10;

is this actually meant to be an [s]?

[Nick]

Ooh, that looks bad - nice find.

[Chud]

I changed this to [b] in the linux port and tentatively (haven't been able to test at length yet) seems to have fixed it. I don't have a compiler handy to do the same under windows, but that probably only matters to my local game. :-)