No I’m asking for clarification on how you want to accomplish what you think can be done.
There’s no way for us to tell if a kick is genuinely malicious, and the vote to kick system is intended to be used for any reason a group sees fit, so there’s no way to report someone for genuinely malicious kicks in a system that purposely doesn’t care what the reason is, so long as the majority of the group agrees.
I thought this would be in relation to M+, but it looks like LFD problems.
I’ve seen and personally been removed from the group on the last boss of an M+ dungeon. I’ll just say that every single time, it was players from those servers. The ones we do not speak of…
I always thought it was stupid, because the people removed, even if they died, were already in the instance. They still get to loot the chest at the end, so imo it serves no purpose other than to be a jack**s. For those instances I’d say it falls under “Gameplay Sabotage”. Even though they are few and far between, those people deserve a vacation imo.
No they haven’t. Blizz is never gonna leave anything set in stone. They say something one way…until they say it another way. That’s why they have vague policies. So that they can re-interpret them as they feel the need to. It was the exact same thing that happened with the m+ leaver penalty.
Quote me where Blizz said you can abuse (which is what we’re talking about here), the boot feature on a recurrent basis such that it makes a very obvious trend. Go on. I’ll wait.
You seem to be labouring under the misunderstanding (much like the rage about the new m+ leaver penalty), that booting some rando now and then will trigger Blizz. Nobody here is suggesting that. It’s when there’s a pattern of sustained behavior that is detrimental to your fellow players, that starts to get blizz to notice.
That’s always the response (2nd only to form your own group). So I guess if you arent a tank/healer and forming your own group, your chance of being screwed is high.