Setting Environment is not preventing user from being created in both environments via Auth

Unity Services
, ,
1

So I set up a simple example project,

Added Auth and the only identity provider is the Unity Gaming Accounts. Imported the demo UI.

Altered the script to set the environment to one I created in the admin dashboard “dev”. No Error.

When I signed up for a new user, with the dev environment set, and then go back to admin dashboard and go to player management, I see that the user was created in both “dev” and “production”. Is this expected? My assumption is that once dev environment is set (I coded such that from the Unity Editor it would set dev env), all other UGS services would only affect that environment (auth, economy, etc). If that’s not the case, I’m not sure how I can prevent the production environment from getting muddied with test users, and eventually data.

2

Hello,

Here’s how things are scoped for UGS at this time:

  • Players are not scoped to environments and can be used across them.
  • Player data services (like cloud save & economy) are scoped to environments.

This should not affect your end-user experience as they will only be interacting with production.

1 Like
3

Hi @erickb_unity ,

I wonder why players are not scoped to environments, is there a specific thought behind this?

Also, if players are not scoped to environments, why is there an environment dropdown on the find players page? It does nothing and might lead devs to believe that if they delete all players from the “development” environment, all “production” players will remain intact.

image
image416×318 12.1 KB

4

Hi @jordivanduijn,

I think the best answer to this is probably that player authentication was one of the earliest things implemented for Unity Gaming Services and that it predates the support for environments.

Thanks for flagging this. You’re right, this is a potential point of confusion. I’ll log that as an issue.

I’ll see if I can find out what our longer term plans are around players and environments. It seems like it’s one of those things where it’s hard to make changes without introducing a breaking change that subverts expectations from those relying on the existing behaviour, but we should at least be able to clarify the behaviour in the documentation (and on the Player Management UI in the Dashboard).

Best regards,

Iain

1 Like