Setting BanningEnabled to false is completely forgotten when place is published and reopened

Bug Reports Studio Bugs
,
#1

In studio in any place with team create, you can set Players.BanningEnabled to false and it will behave as expected, BanAsync() will not work. However, when the place is published, the published place has Players.BanningEnabled set to true. Furthermore, reopening to place will also result in Players.BanningEnabled being set back to true.

This bug does not occur in non team create and locally saved places.

Repro for in-game behavior:

  • Open any place that has team create and set Players.BanningEnabled to false
  • Publish the place
  • Join the place and use Players:BanAsync to ban yourself
  • It will ban you instead of throwing an error

Repro for studio behavior:

  • Open any place that has team create and set Players.BanningEnabled to false
  • Save or publish the place
  • Close and reopen the same place
  • Players.BanningEnabled will be true again
2 Likes
#2

Are you developing under a team-create instance? There have been many of these property-saving bugs that are specific to team-create (in fact, StrafingEnabled, a property under the same service as BanningEnabled, had that issue) No clue if this property bug also impacts non-team create places, but I thought I’d mention this just in case it ends up being relevant.

2 Likes
#3

Yes I am developing on a team-create place. This bug does not happen on non team-create places and locally saved places,…, I should edit the post to also say that

2 Likes
#4

Thanks for the report! I filed a ticket in our internal database and we’ll follow up when we have an update for you.

2 Likes
#5

It’s still not fixed, this is really bad since I must turn it off for my game that has places attached to it

3 Likes
#6

Are there any updates on this? I really do need to be able to disable BanAsync and keep it disabled in team create places

1 Like
#7

No updates yet, this is not good at all.

2 Likes