Unable to set Server Sizes to below 11

Bug Description


This bug seems to currently occur on Roblox Studio, at any existing game that is published to Roblox. When accessing Studio Settings > Places > Configure Place, Studio greys out the “Save” button if the place’s Server Size is set below 11.

Expected Behaviour


I should have no problem saving the Server Size if it is set to below 11.

Where it Happens:


This happens on any published game on Roblox.

Simply navigate to your Game Settings > Places, select the 3 dots for the Place you would like to change its Server Size and click “Configure Place”.

When it happens:


As far as I know, this seems to be happening since 22nd June, 2023.





Workarounds


Setting the Server Size on the Creator Dashboard for their respective places.


Reproduction Steps


  1. Go to any published game, either currently existing or a new one.
  2. Go to your Game Settings > Places.
  3. Click on the 3 dots on the Place you would like to configure, and click “Configure Place”.
  4. Attempting to set the server size below 11 causes the bug to occur.
8 Likes



Able to reproduce.
One workaround is to go to your dashboard https://create.roblox.com/dashboard/creations
Select your game
image
On the left, hit “Places”


Click your desired place
image
Click “Access” on the left
image
Put your desired playcount.

image
image

2 Likes

Yup, that seems to be the only workaround. Strange how Studio doesn’t let you set server sizes specifically above 11 though.

2 Likes

Hey there!

As it turns out there’s a funny pattern to this. The limit in studio (11 in your case) is exactly above 20% of whatever is set in the dashboard menu (50 by default).

Dashboard Studio (limit) A fifth (20%)
50 11 10
100 21 20
104 21 20.8

And after 105 (respectively 21 as 20%), studio only begins to allow the player count that is greater or equal to the dashboard setting.

Not like this is any important info lol, but maybe this is about an accidentally implemented limit that was planned before but they later decided not to include it.

1 Like

That’s quite the observation there, didn’t cross my mind when I made this Bug Report.

It might be possible that this is what’s causing the issue, so thanks for sharing this valuable (theory, opinion, insight?)!

2 Likes

Hi MsDeborah! Thank you for reporting this issue. We’ve fixed the bug! Everything should be running properly now. Are you encountering any more difficulties?

2 Likes

No, it’s working as intended now!

Thanks for looking into this!

1 Like