Bash bug?

[Guest]

This seemed a bit buggy to me:

*Bollesedun* pierces you. <<<< He comes in and engages me
You wish that your wounds would stop BLEEDING so much!

HP:Critical MV:Good - Bollesedun: Battered>
bash human <<<< I start a bash on him

Targh tries to pierce *Bollesedun*, but he parries the attack.

HP:Critical MV:Good - Bollesedun: Battered>
HP:Critical MV:Good - Bollesedun: Battered>

* =
Targh pierces *Bollesedun*.
*Bollesedun* barely pierces you.
You wish that your wounds would stop BLEEDING so much!
*Bollesedun* barely pierces you.
You wish that your wounds would stop BLEEDING so much!

HP:Critical MV:Good - Bollesedun: Battered>
= +
*Cifon* has arrived from the north. <<<< Cifon enters the room

HP:Critical MV:Good - Bollesedun: Battered>
+ -
Targh narrates, 'spam bash'

HP:Critical MV:Good - Bollesedun: Battered>
-
*
You can't bash someone else while engaged! <<<< Target has somehow switched to Cifon

[Jerez]

not sure if im right or not, but it could have been that cifon was in the room when you entered bash human and it started timer with him as target then he left and came back again, or maybe its a bug, can't really be sure.

[Axxey]

It has a check at start and finish, has been this way for a long time, human applies to both of them so the check at the end is 1.human(cifon).

Bash by name and is no problem.

[Guest]

For Jerez: Unless he's learned effusion, he couldn't have left the room without me seeing it

For Axxey: So in other words it's faulty coding then right?

[Axxey]

could be intentional, could be unintentional, either way has it's pluses.
You can always bash by name. Had cifon engaged you you would have bashed him, him being 1.human.

[Jerez]

its is not like that for channeling though, i think its kinda wierd that it should be different for bash

[Raiden]

its been like this for decades, its probably one of those faulty codes that the imms never bothered about.

and no i dont mean kinslayer