An unknown reason is preventing anyone with permissions to save any changes to the access settings of our games. This includes changing the max server size and changing the social slots setting, which are the two changes we are currently concerned with.
Expected Results
The Creator Hub should save the changes made to the max server size and social slots setting when the “Save Changes” button is pressed.
Actual Results
The Creator Hub fails to save changes made when the “Save Changes” button is pressed.
Screenshots
Games Affected
Serving Cadland, Potatoburg, and Westpotat, the PTA Fifth Avenue Lines are the first lettered lines of the PCS system.
We recommend that you join our communications server and Roblox group to stay informed.
Do not play if you are on a lower-end...
Serving Potatoburg, Cadland, and Westpotat, the PTA Callaghan & Madison Lines are the second installment of lettered lines of the PCS system.
We recommend that you join our communications server and Roblox group to stay informed.
A good device...
The second piece of Initium.
Serving 4 boroughs;
𝖯𝗈𝗍𝖺𝗍𝗈𝖻𝗎𝗋𝗀, 𝖢𝖺𝖽𝗅𝖺𝗇𝖽, 𝖪𝗋𝗒𝗉𝗍𝗈𝗇, 𝖺𝗇𝖽 𝖶𝖾𝗌𝗍𝗉𝗈𝗍𝖺𝗍
Soon, our first subway comes back to life.
1 Like
weeek53
(weeek53)
June 24, 2025, 10:23pm
2
Hello is this still happening? How are those with access granted permissions? Is it through the new roles or the legacy roles?
1 Like
Yes, this is still occurring. I assume the ability to change the settings is through the group role permissions?
Possibly related, but I haven’t confirmed as the error message is different on my end:
It appears that editing a game name is rejecting “PTA” from being in the game title (likely description as well) again. This was already an issue previously, so either the same cause has resurfaced or another cause is causing the same issue to happen again.
Expected Results
Game title change with “PTA” should be accepted
Actual Results
Game title change with “PTA” is rejected
[image]
[image]
[image]
https://cdn.discordapp.com/attachments/947255567393632276/1388344711496077402/Video_2025-…
It appears to be fixed now! The bug report I linked was also fixed. They were likely connected/the same bug.