MaxPlayers and PreferredPlayers properties are completely inaccurate

I have set max players to 8 on both the website and in the game settings in our Team Create enabled place.
On the Players service, a completely different value (60) is present for both the MaxPlayers an PreferredPlayers properties.


This persists in a live game server (playtesting by launching from the site) and the properties are inaccurate even though the server correctly limits the amount of players that can enter. Changing max players again does not seems to do anything at all.

Expected behavior

I expect both of the properties to have the value I set

A private message is associated with this bug report

4 Likes

Hello, the MaxPlayers under Players Service in Studio, is separate from the MaxPlayers in the actual game. The number that shows up in Website is what will be reflected in the game.

It is not accurate in game - neither in studio nor in a live server - that’s what the bug report is about. Sorry if that was unclear.

This persists in a live game server (playtesting by launching from the site) and the properties are inaccurate even though the server correctly limits the amount of players that can enter…

Some context on how this bug affects us:

Our game reads Players.MaxPlayers on startup and creates a team for each player slot. It runs on the first server frame. We have used the same exact system for ~4 years, and it is known to be reliable.

In the specific place linked privately in the report, which is a recently created Team Create enabled place, it creates 60 teams when the max players is set to 8. The system works fine in other places that combined have billions of visits across them all, and that have existed for longer: