Hey everyone,
as we all know repeatedly kill-stealing a monster is against the rules. However, everyday I see discussions where people argue what actually constitutes as kill-stealing and what doesn't.

I feel before we can tell people to complain/stay quiet/report players, we should first have a shared understanding when a player actually "owns" a monster.

One part of the playerbase goes by: Monster aggro determines ownership
That means if a monster is walking towards a player, that monster now "belongs" to that player and others should not interfer. One exception I would consider is if the player shows no intention to actually kill the monster and just "holds" them for a longer time, weakening healthy respawn of monsters - but so far this is not a behavior I ever really observed.

However, there's also another group of players. They'd argue: Damaging a monster determines ownership
Going by @noks, they'd be absolutely right. A monster is only protected once you start attacking it, any millisecond before that, anyone can jump in and kill it.

Personally, I heavily lean towards the first definition as it seems the most inclusive to all classes.
I want to stress that this is not a matter of "just one-shot and you're fine". Even if you can one-shot everything, you may still take a couple hundred milliseconds to ensure that monsters are in your range of attack/aoe. This seems unfair as one player fulfills the role of pulling/grouping monsters, just for another player to teleport in and kill them. Grouping them is obviously not a waste of time here, as the kill-stealing player clearly benefits in that case.
This specific behavior can be observed in many farming places, but I personally observe it a lot in CTB where e.g. a certain SA player will just alternating between teleport and white tiger without any regard of other players or if there are even monsters to begin with (the latter makes me wonder if they might not even be present at the computer, but this is not what this post is about).
Sorry if this doesn't belong in general, but I felt like it didn't really fit into bugs/suggestions as this is something the community needs to align on, not necessarily something that can be solved by code.