Group Public Moderation
Frenetic Furryǃ
~{Issue}~
there's malicious people that make a group just to go around and make group public instance's so they can just ban/ kick people from games for purely no reason & it's getting annoying, for example: crashers have the intent to just remove people from worlds/ VRChat & make things unplayable or unjoinable.
people like me just want to play the world and then get off of vrchat for the day.
~{Feature/ Fix}~
- removal of groups having this power in public worlds all together.
- add an option to report these groups for being malicious.
- add the option for the developer of a world to disable group public instance's entirely &/ or whitelist some groups that're trustable to do this.
(group public instances are generally unnecessary for VRChat because it just adds a layer of potential abuse power, if someone in a public world is doing something they shouldn't then more likely then not the VTK system will be used to remove them BUT that cannot be done for people that make group public instance's to kick everyone instantly.)
~{Quick Q/A}~
Q: can't you just avoid these groups in games?
A: yes! but actually no, VRChat does not tell you group names on the website and that is where i primarily invite myself into games because the VRC client doesn't update servers all that well & can get abit confusing when it does. (doing it through the website allows you to refresh the servers when you want and not when it decides to update.)
Log In
RF_GAMER
The moderation of public instances needs to be under the administration of vrchat team itself, please REMOVE GROUP PÚBLIC INSTANCES FOREVER !!!!
Deantwo
RF_GAMER:
That seems like a very very shortsighted idea, and wouldn't solve the issue at all.
You would have to be paying VRChat a lot more money for that to work, since they would have to hire a ton more staff that can moderate ALL the public instances on the platform. It just isn't feasible.
DAG-XR
Alternatively: Make group public instances require VRChat+ subscription to create - but that would be taking away a pre-existing feature. Your suggestions are good.
Temmie Dola
Delete group publics
Deantwo
> "VRChat does not tell you group names on the website"
Why not just report that as a bug? When that is solved, you can more easily avoid those groups. This would solve your problem without removing the group features that a lot of people are using and enjoying.
I don't see any open canny posts about this information missing on the website, so you should probably make one.
Deantwo
I made a bug report for you, here: website-cant-see-owner-of-group-instances
Frenetic Furryǃ
Deantwo sorry for the very late response lol, "Why not just report that as a bug?" its because it is not a bug, the vrchat website is intended to be like that & even currently it still just says: "Group Public" even though it should really say the group name instead.
"you can more easily avoid those groups." yes this is true! you might be able to avoid 1 being a bad actor but what if a new one comes along and does the same thing? cant exactly avoid it if you've not been there before and it becomes a tedious loop that is just annoying to deal with, while you can just avoid group public instances all together it makes vrchat become limited because taking "Infected" for example it typically only has a single server so that would make it where you cannot play "Infected" (could make your own server but then you need people to join and people are more likely to join larger servers so it takes a long time.)
Deantwo
Frenetic Furryǃ: "the vrchat website is intended to be like that"
Then it is just a feature request instead of a bug report, not a lot of differences between the two. Either way, as I posted above, I made a bug report/feature request already.
Frenetic Furryǃ: "cant exactly avoid it if you've not been there before and it becomes a tedious loop that is just annoying to deal with"
Same thing can be said about normal public instances. I can't avoid the public instances with screaming kids without first checking. The solution there is to either actually go check, or just avoid public instances altogether. If you are that worried about even checking, your best cause of action is to just start your own instances and wait for people.