Thanks for the info
The current public server system is nearly perfect for my needs except being able to close the server after a given point (it’d be a bad experience to join an ongoing game for new players).
The interface for my game is super casual. There is a hole in the ground in the lobby, and you jump in to play.
I’d really rather keep any options or menus or text away from players until they have had QuickStart games a few times.
So, new problems then!
I can recreate the public system… and have… using a complex rig of reserved servers, friends lists, and communication over data stores. I have some concerns about how well this will scale but I think it will be manageable.
What I gain from this is the ability to control exactly who joins a game, so yay!
What I lose is one of robloxes better features, the ability to invite friends into your game and the ability to join a friend from the web interface.
If you are using reserved servers now the following two behaviours happen:
If you use [join] to join a friend who is in a reserved server, you join the lobby place instead.
If you use [invite] to ask a friend to join, the friend joins the lobby place instead.
This isn’t the end of the world, but it’d be nice to have that work for users
My best plan for working around it is: search all the currently active reserved servers (unghhh slow refresh times ahoy) and find your friends, and give you a simple prompt on which friend to join once you QuickStart.
(AFAIK you can’t tell in any way that a player joined a lobby due to invites or join friend or which friend they wanted to join…)
Aannyway, having the ability to programmatically close a public server (let me change maxplayers to a lower value, let me set reserved slots to fill the remainder) would solve 99 percent of making a good experience for my game.
The only thing that would be an issue Then would be if you don’t want to play with your friends, and frankly that’s just not roblox