vote kick #2818
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2818
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
suggestion: rec room (where I make VR games) has a room based /voteKick system where if >50% of the room votes to kick a disruptive player out, they get moved out of the room. On rec room that simply means they get to try again, in a different room full of players - so it's not like they're out of the game.
Here it could simply move them out of main chat for 20 minutes or something like that for when no staff is around? maybe with an auto-message explaining that they were being disruptive or disagreeable to the majority of players. Just a thought, it's rare no staff is around but it can happen.
i swore we already had another issue about this, but it seems it was just in-game chat or something.
there's a lot of pitfalls w/ votekick and similar systsems, but it at least deserves some consideration, and perhaps some experimentation.
you want to keep it from getting brigaded or allowing someone to create new accounts and cheat the system.
you also want to keep from kicking staff/admins.
using the usual YL mechanism of scaling votes to level is probably a good idea, but that's not the only heuristic that matters (we don't want to turn shanish into a god).
votekick-type mechanics can exist for multiple privileges - perhaps it's not so hard for a single player like daydream to kick someout out of the public farm in haven, at least for a while, but she can't silence or kick or ban a player on her own.
i'm proposing that we experiment w/ mechanics give players such power over other players, w/out saying that we have all the answers right now. admins and staff will have to make decisions, and change previous decisions. getting the opinions of random players will be important.
overall, i fear the ways that such mechanisms can be exploited; we'll have to work defensively to keep such things out at the expense of more democratic approaches. at the very least, such a system should be designed so that the admins can quickly pull the plug on it if it's being abused.
that one your-land/administration#64 ?
Nice finding! We were looking all over for that :)
Note: don't look for stuff close to bed time lol
I do have kick priv but I see your points flux :)
We've had a similar discussion in the administration issue Bla discovered. Please continue there (but repost new reasonings there, so they don't get lost)
If this is for some reason not the preferred proceeding, maybe because others who do not have access to administration should be able to chime in, please let me know, then we'll reopen here.
Until then duplicate of your-land/administration#64