{"action":"created","issue":{"url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/5560","labels_url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/5560/labels{/name}","comments_url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/5560/comments","events_url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/5560/events","html_url":"https://github.com/HabitRPG/habitrpg/issues/5560","id":92971331,"number":5560,"title":"a quest that is not desired by the majority of a party is too hard to remove","user":{"login":"Alys","id":1495809,"avatar_url":"https://avatars.githubusercontent.com/u/1495809?v=3","gravatar_id":"","url":"https://api.github.com/users/Alys","html_url":"https://github.com/Alys","followers_url":"https://api.github.com/users/Alys/followers","following_url":"https://api.github.com/users/Alys/following{/other_user}","gists_url":"https://api.github.com/users/Alys/gists{/gist_id}","starred_url":"https://api.github.com/users/Alys/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Alys/subscriptions","organizations_url":"https://api.github.com/users/Alys/orgs","repos_url":"https://api.github.com/users/Alys/repos","events_url":"https://api.github.com/users/Alys/events{/privacy}","received_events_url":"https://api.github.com/users/Alys/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-04T04:50:50Z","updated_at":"2015-07-06T01:56:41Z","closed_at":null,"body":"It's possible for a party to contain a quest that the majority of the members don't want. E.g., the quest owner uses a scroll and then immediately starts the quest for purely their own benefit with no other participants, or if the quest owner doesn't log in for many days after sending invitations (a single inactive party member can then prevent the quest from being started). The workarounds currently are for party members to leave the party and start a new one (troublesome and often undesirable) or for an admin to delete the quest (not hard, but we're reluctant to do that prematurely, resulting in further delays for the party).\r\n\r\nI'm creating this issue because @hairlessbear has outlined some interesting and promising ideas to me and I want to hear more from him about it. Even if we end up not going with his ideas, some solution would be desirable.\r\n\r\n<bountysource-plugin>\r\n---\r\nWant to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/23652749-a-quest-that-is-not-desired-by-the-majority-of-a-party-is-too-hard-to-remove?utm_campaign=plugin&utm_content=tracker%2F68393&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F68393&utm_medium=issues&utm_source=github).\r\n</bountysource-plugin>"},"comment":{"url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/comments/118691160","html_url":"https://github.com/HabitRPG/habitrpg/issues/5560#issuecomment-118691160","issue_url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/5560","id":118691160,"user":{"login":"Alys","id":1495809,"avatar_url":"https://avatars.githubusercontent.com/u/1495809?v=3","gravatar_id":"","url":"https://api.github.com/users/Alys","html_url":"https://github.com/Alys","followers_url":"https://api.github.com/users/Alys/followers","following_url":"https://api.github.com/users/Alys/following{/other_user}","gists_url":"https://api.github.com/users/Alys/gists{/gist_id}","starred_url":"https://api.github.com/users/Alys/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Alys/subscriptions","organizations_url":"https://api.github.com/users/Alys/orgs","repos_url":"https://api.github.com/users/Alys/repos","events_url":"https://api.github.com/users/Alys/events{/privacy}","received_events_url":"https://api.github.com/users/Alys/received_events","type":"User","site_admin":false},"created_at":"2015-07-06T01:56:40Z","updated_at":"2015-07-06T01:56:40Z","body":"Some of my comments here come from my feeling that a party should be a collaborative group that can solve at least some of its own problems with communication, or failing that, by removing recalcitrant members (or removing yourself if the party doesn't suit you). This voting mechanism would certainly help with that! I'm also pretty keen to see something like this done, so I'm commenting on things that I think could be done in a second stage after the basics are in place. Note that my comments are not meant to be \"this is how it will be done\"; they're just my current opinions. :)\r\n\r\n_\"If a majority of users click the [vote to cancel/abort] button\"_  -- Yes, where \"majority\" is calculated by not counting the quest leader or any member who has been inactive for X number of weeks. X=1?\r\n\r\n_\"Once clicked, the button would become disabled\"_ -- Or we could allow it to be unclicked to remove your vote. However that could be added in a second stage.\r\n\r\n1 ii _\"... give a reason for their vote ...\"_ -- I'm thinking that's extra complexity that might not be needed, at least in the initial implementation (maybe add in a second/third stage). In small parties, the reasons would be less anonymous. Non-anonymous communication might be better for building a strong, honest party. It it were not anonymous, a PM or chat message would suffice. I'm not against this, I just don't think it's one of the most important requirements.\r\n\r\n1 iii _\"Prevent a user who had a quest cancelled in this manner from starting another quest for 24 hours\"_ -- For simplicity, this could be implemented as a buff that wears off on cron, which I know can be much less than 24 hours, but SO simple. :)  Although really, setting a time and then checking that when the user clicks on a quest scroll wouldn't be that hard.\r\n\r\n1 iii a _\"If a user has multiple quests cancelled in a row ...\"_ -- I don't think we should do anything automatic here. If the user keeps on messing up in the same way, the party should boot them (or leave the party if they are the leader). Letting the party handle this would be MUCH simpler than keeping track of historical information (fewer chances of bugs too).\r\n\r\n2 _\"It may be useful to display the current vote count...\"_ -- I'd be in favour of a vote indicator next to each person's name, so that voting isn't anonymous. That would help with the obnoxious user problem, and allow everyone to know how everyone is feeling. Currently, opinions about current/future quests have to be expressed in party chat, so non-anonymous voting isn't that much different. \r\n\r\n@hairlessbear You might want to let us know your opinions about anonymity, as a contrast to mine."}}