first reading the start of a map with a 3 minute delay to overcome the transition period from the previous map

2026-10-04 20:50:33 +02:00
parent 7a6051987e
commit d64f8c3f29
5 changed files with 32 additions and 5 deletions
@@ -0,0 +1,8 @@
+// How long after a map starts we wait before reading its "starting"
+// population. At the exact instant of a map change the player count is still
+// the previous map's (people leaving or reconnecting), so reading it at t=0
+// would blame the new map for attrition that happened before/around the
+// change. Shared by the leaderboard, the population chart SQL and the
+// per-session timeline so all three agree. Safe to import from client code.
+export const START_BASELINE_MIN = 3;
+export const START_BASELINE_MS = START_BASELINE_MIN * 60_000;