Remove bleed

[duvessa]

It's not any more interesting than headbutt ministun or whatever

[dowan]

But my FLAVOR!

[Sandman25]

I always thought bleed is a hint for new players to use hit-and-run tactics as Tr: you regen faster than usually, monster loses HP instead.

[radinms]

actually how are good about bleed?
please tell me detail.

[Sandman25]

actually how are good about bleed?
please tell me detail.

Oops, now I am all for the OP. Let's remove bleed, it usually does nothing but confuses player. Sometimes it removes 1 HP, right before end. The only situation when it matters is when the bleeding is done by Ds with ignite blood.

  Code:

You claw the orc warrior!(damage 10); Monster lost 10HP
The orc warrior begins to bleed from its wounds!
The orc warrior is moderately wounded.
The orc warrior barely misses you.
The orc warrior hits you with a short sword!
Damage: -10%(-9hp)   hp: 90%(79hp)
The orc warrior hits you with a short sword!
Damage: -12%(-11hp)   hp: 78%(68hp)
Monster lost 1HP
The orc warrior barely misses you.
The orc warrior is no longer bleeding. The orc warrior barely misses you.


I ran similar tests multiple times (all with Tr).

[bcadren]

I'd always heard it was enough damage to stop monster regeneration, but not really anything else. It's a little weird that some random claw attacks cause bleeding, but a long sword doesn't...

[ion_frigate]

It does 9% of the monster's current HP per turn for trolls, 3% for felids and ghouls, in case anyone was wondering. And yeah I definitely agree it's pointless. In addition to being confusing to new players, it also leads to even more battle spam, which is really never a good thing.

[Berder]

3% per turn?

I don't really care about Trolls since they're overpowered, but I'd like to see some quantification of how much bleeding does for melee felids on d1, esp. with hit and run tactics. Felids ought to get a buff if they lose bleeding.

[Sar]

I like bleeding since holding tab against a corridor of yaks and painting it red was always one of those little satisfying things I liked about Crawl. But blood effect differentiation between weapon types was removed already so might as well go and axe bleed as well.

[Pollen_Golem]

It would be more clear if you inflicted the Sick status rather than Bleed, like old Komodo dragon bite.
Stopping monster regen with paws/claws sound ok, but Bleed is confusing because its HP-dependent unlike poison.

[Sandman25]

It does 9% of the monster's current HP per turn for trolls

How do you know? It contradicts to what I see in my crawl:

  Code:

You claw the ettin!(damage 8); Monster lost 8HP, current 62
The ettin begins to bleed from its wounds!
The ettin is lightly wounded.
Monster lost 1HP, current 61
The ettin hits you with a dire flail! x2
Huge Dmg: -27%(-24hp) hp: 73%(64hp)
Monster lost 1HP, current 61
The ettin hits you with a dire flail!!!
* * * LOW HITPOINT WARNING * * *
The ettin hits you with a dire flail!!!
Die?
Thought so.
A goblin and an ettin come into view.
Monster lost 1HP, current 60
The ettin closely misses you. The ettin hits you with a dire flail!
Damage: -13%(-12hp)   hp: 87%(76hp)
Monster lost 1HP, current 60
The ettin misses you. The ettin hits you with a dire flail!!
* * * LOW HITPOINT WARNING * * *
Huge Dmg: -33%(-29hp) hp: 54%(47hp)
Monster lost 1HP, current 60
The ettin is no longer bleeding.

[byrel]

Does it check AC or GDR maybe?

[neil]

It actually did between 0% and 3% HP per turn for one degree of bleed, from any kind of claws.

  Code:

            const int degree = you.has_usable_claws();


player::has_usable_claws() returns a bool, so the added degree is always 1 if it does anything. However, I can't blame ion_frigate for being misled: the code that applies the bleeding had a comment "// 3, 6, 9% of current hp", and the closely-related actor::has_claws() does return the size of the claws, as an integer between 0 and 3. Probably several devs have also looked at this code and thought that it was 9%.

[adozu]

which is the actually intended behaviour then?

[njvack]

for bleed-over-time to go away

[neil]

which is the actually intended behaviour then?

Just did some archaeology with git blame: It looks like the intended behaviour was in fact 0-3%, 0-6%, 0-9% for claws level 1, 2, and 3. This was accidentally reduced by this commit. This is similar to the octopode squeeze damage bug (link goes to the fix), but in reverse.