Well if you say 'especially sap', then don't druids rely on a mana kill _and_ sap is envoyed to be deleted? That is a very weak point.

Druid don't rely on a mana kill. They rely on the fact that you essentially can't clot in sap and will bleed to death.

Sap is staying?

A bunch of random envoys wanting to delete sap does not mean sap is being deleted.

So far we have:

To know:
- should not be forcable

Negative:
- a problem for Druids because people have infinite mana, hence mana is a non-issue, and they can cure bleeding quicker in sap, and sap envoys should not be accounted for according to Lehki

Anything else?

Regarding aeon effects and clot, I doubt it would be too difficult to make it only clot once while under those effects. Firstaid, I believe, properly obeys those limitations.

You know, it'd be pretty easy to make it so, if afflicted by choke/sap/aeon, you can't use the number (or if you do, it's ignored). You could even make it so CLOT is forceable but CLOT <#> isn't. Tada, problems solved, easy-peasy.

Maybe just sap, but otherwise, it'd be cool with me.

I think people are forgetting that clot requires mana as does focus body and that is where the real kicker for killing under sap comes in. Running them out of mana so they can't clot or focus body to break free of the sap lock. This change wouldn't lessen that at all, in fact it would be more likely to speed up the process of them losing enough mana fast enough that they can't do other things, like cure the passive paralysis or gyfu rune being slung at them.

Edit:: Also people worried about not being able to individually clot... you can always 'clot 1'

Alternately, you could add some additional cost to CLOT #, like a short eq strip, or something. So that using it not only means dealing with aeon/choke/sap, but also means that there's something else you CAN'T do at the same time. (FOCUS BODY comes to mind)

I'd be happy if they just fixed the bug with clotting in firstaid...

So what happens now?

bump.

I wouldn't hold my breath on this one.

I'm sure it'll be envoyed sooner or later. Problem is, the next earliest is a few weeks + coding/accepting/rejecting time.

I'm fairly sure we're not considering this at this time - it did come up, and it would overly impact abilities like choke, sap, etc. I'm not averse to something that still would go through these abilities in the same way but would act as an in-game alias of sorts to send the command x many times. (You'd type clot 50, but the game would see clot being sent 50 times).

That sounds interesting. I think it'd be better than nothing.

Yes, I agree it is better than nothing, even if the major causers of bleeding are not, interestingly enough, classes that give such slowing abilities (warrior/monk bleeding > redcap).

2/6 warrior guilds can aeon. Not sure how often it comes up, but we can.

If that is in fact the case, then either implementation would essentially be the same, barring things like stupidity and insanity (which should have an effect on clotting going through).