Can we stop caching Instance Player counts?

Help!
, ,
1

Hi there,

I am making this thread due to an issue that I have noticed for ages. It appears that instances without a queue will always remain ‘full’, even if the instance later has multiple slots open and no players joining, resulting in a HTTP 403 response.

image
image565×257 17.7 KB

This persists until the game is restarted, which makes it outright impossible to join an instance that only has a single slot opening up every ~30 minutes and no queue.

Again, even if the instance has 8/16 players at a later point, if the client attempted to join on 16/16 or 15/16 while another player is already trying to join, this response is still sent back to the client.

The player count itself is refreshed too, which means even the client trying to join the instance can see “7/16” but still get a 403 response until they restart their game, and try again.

2

Error 403 sounds like it’s a response from server, but maybe not? I’ve found that with VRCX you can refresh count of a specific instance. Maybe see where that gets you? Whenever VRChats in game list is acting up, I’ve usually had good results inviting myself via website or VRCX.

If they actually stop caching user counts, that could be very entertaining, maybe they could make it like a game server browser from the 1990s. Hit refresh and then wait as your computer checks in with every server on the planet individually

Actually that’d make a great gimmick for April fool’s

But since we’re in the future, they need to make tweaks to how that caching works.