Mocah wrote:
I feel like this work better then an automatic raid kick based on RPP or activity because everyone has things to do other then BoH (sometimes.
)
Other things to do? I don't understand....?:p
Seriously, I'd like to see belt and braces.
1. Blacklist by player.
2. Auto-boot after 5 mins if RPP stays at <=100*
3. Manual boot option by GM / Officers.
The reason I say by player is that if a player skunks with one toon, he's probably gonna skunk with another if you block that one and you can end up chasing your tail, esp at low-mid range raids where new toons can be created and reach the required might for the raid by the skunking player quite easily. The block would not just be by player name, but linked to the player's primary ID record, so if they change their name, the block stays. It's up to the GM and officers to track their blocked list and remember why a given player is banned, if they change their name, I'm sure most of our GMs can figure it out.
The autoboot I like. Fine, everyone can suffer interruptions and/or suddenly not be available to play for a period. But in doing so, they're taking up a slot that could be used by someone who is available, and penalising the hosting guild. It's not their fault that your dog decided to eat your table at the point you pressed Enter.
Giving the hosting GM /officers the power to boot would be welcome. I'm not currently aware of any method by which a hosting guild can silence a player who joins as a merc and proceeds to be... "unsavoury", esp in younger guilds.
Whether auto or manually booted, a booted merc should not gain any rewards from the raid. It would also be sensible to restore any hits they have made. So if a toons joins, makes 2 hits and goes inactive in Phase 1, then is booted in phase 4, those 2 hits should be added to the phase 4 baddie so that the "rolling merc slot" tactic couldn't be used - ie have a slot where a succession of toons join, make a few hits, then get booted to make room for the next.
* Boot trigger point could be set by the guild, or be predetermined by raid. It would have to be visible to mercs before entry - no merc would want to see a 5kRPP req on a raid they join in phase 4 AFTER joining!
Setting a low trigger point increases the risk of being skunked and/or having multiple low-scoring mercs. Setting a high trigger point increases the risk of suddenly losing a bunch of hits during the raid as players get booted for not having reached that point, and putting mercs off joining - that could be another strategic decision for the guild to make as part of the raid.