Repository navigation
Defer sending of events until a player ID is assigned #10
LswaN58
started this conversation in
Bugs/Issues
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Obvious caveat, this idea would only apply to games that use player ID.
The issue: currently, games that use player IDs tend to have a few events occur before a player ID is assigned. In particular, when players choose "new game" or "resume," these events always occur before a player ID is given, for obvious reasons. If they choose "new game," a new ID needs to be generated, and if they choose "resume," an existing ID needs to be entered and validated.
The result is that we have these important events disconnected from the rest of that player's data. There are things we could do on the back end to deal with this, like stitching on any events with null player ID that have a session ID matching a session within the player's data. However, it would in general be nice to actually get the player ID included in the first place.
To that end, it may be nice to have the game defer logging of events until the player ID is actually set, for those games that use the player ID field. There's lots of potential technicalities and edge cases to discuss, but I'd like to see those discussions through someday.
All reactions