Quote Originally Posted by Amberyl View Post
When playing as a DPS, I regularly see DF players attempt to kick-vote inexperienced or under-geared tanks and heals and use words very much akin to the above as their justification. This happens most in non-levelsync'ed content, where players are new to the game, and may not even understand how to lodge a grievance with a GM.

Your acceptance of kick-votes deviating from the specified text in the client encourages a kick-now-and-see-if-it-comes-back-on-us attitude. If you're going to allow such terminology in the justification of kick-votes, then it should be a written option in the client.
This does leave us with 2 possible options.

Option 1: We only consider reasons for dismissal that are specifically stated to be an abuse of the vote dismiss feature. On the plus side, this does provide a clear and definitive set of guidelines for the use of the feature. On the downside, it is limited by the creativity of customers to find ways of disrupting a run outside of what is listed. Otherwise, the list of possible violations will be too extensive to be used efficiently or will be too vague to provide a definitive set of guidelines.

Option 2: Commonly reported reasons for dismissal are listed, although the tool can be used to dismiss anyone for causing a disruption to the duty. On the plus side, the feature can be used to remove disruptions and increase the chances that the duty can be completed. On the downside, it means that there is not one definitive list for reference on when the use of the feature is justified.

Neither option actively prevents abuse of the feature. Abuse of the feature is prevented due to account actions taken by GMs after an investigation to encourage customers who do misuse the feature to discontinue that behaviour. Currently, option 2 is what is currently in place, since a GM needs to investigate either way, and allows the GM to consider new types of disruptive behaviour that arise instead of waiting for a change to the tool while keeping the tool interface easy to navigate and use.

I think what I may not be clarifying in my replies is that this allows for a broader scope to the use of the tool than just one stated example (not fulfilling job duties). It's never just "one more reason"; the possible reasons for proper use of the tool are limited only bt the creativity of those looking to disrupt duties. Once we list something there, some new way of disrupting runs is bound to arise, and this allows customers to try to make sure runs go smoothly while still allowing for GMs to consider if the feature itself was used in a proper manner.

LGM Enkrateia