Hello,
To explain my use case: I'm trying to set up some sort of 'team leaderboard' functionality.
My plan was to create a 'dummy user', which would hold the stats of the team.
Each of these teams would have a 'dummy user' that holds their stats, so I could then just look up some leaderboard for team_stat_games_won, and the leaderboard would look up the team_stat_games_won statistic, which is only ever set for the 'team dummy user' accounts, so that seems like it would work.
To create these 'dummy user' team accounts, I would:
-Create a shared group, let the unique id be generated
-Use this unique id as the username, and register a new PlayFab user (the playfab username must be between 3-20 chars, question #1 is will the unique generated shared group id be between 3-20 chars? I couldn't find any info besides that it's unique. Question #2 also not sure if everything in the client API is included in the server API, but I was planning on using the client API register PlayFabUser on the server side to create this 'dummy user')
To update the team's statistics, I would:
-Attach a regular 'real user' to a 'team/dummy user' by setting some custom user data linking to either the shared group / dummy user playfab id.
-I could then update the team_games_won statistic for the player's team by looking up which team they were on(playfab dummy user id), and then update that statistic specifically.
-I would still be able to update player_games_won statistic for the actual 'real player'
Some additional notes:
- If the same statistics exist for both players + teams, half of the statistics taking up limit space are wasted.(blank team_ stats for real players, blank player_stats for 'dummy team players'. I guess this is fine for now)
-How would this approach affect my DAU? The 'dummy team users' would never be logging in, but their statistics would be updating frequently
I've heard that you are releasing a new 'clans/teams' feature sometime in Q1, however as of now we don't really need too much functionality in regards to teams, pretty much just the leaderboard stuff explained above (nothing like a shared inventory or anything like that),
Do you think the above approach is a good idea? Is it even possible? Or should I hold off on this and wait for your 'teams/clans' release that I'd assume is going to have some sort of leaderboard functionality.
Also @Brendan, the only use for the 'shared group data' in this example is to use the API to generate a key that I know will be unique (which I believe is the case when creating a shared group and not providing its ID . If no SharedGroupId is specified, a random identifier will be assigned.), I was wondering if this identifier is limited to between 3-20 characters, if this is the case I'm thinking I could use this as the Username field when trying to register a new 'dummy user' for the team.
Thanks for reading and building an awesome service,
-Dan