Skip to content

chore: correct first_join data for all players #6

@ZakShearman

Description

@ZakShearman

Background

For a long time, the first_join time was being set to 0 (1970-01-01 00:00:00) and this is the case for many players. In some cases, this time would have been updated by the UpdatePlayerData method to the time when that method was called - this is not accurate to their actual first join time either.

Solution

We should use data from another source (likely posthog) to correct each player's first_join time - even those where it is set, if the time determined via Posthog is earlier, we should set it to that time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions