Flood Dashboard
Telemetry receiver for a Roblox game with a dashboard reading the data live.
Context
A project of mine, tied to Flood, an Estúdio Crivy game on Roblox. Every published game reaches the same point: you have to decide what to adjust, and the metrics the platform hands you are too shallow for that.
Challenge
Without data from inside the game, balancing becomes guesswork. You do not know where players quit, which mechanic nobody uses, or whether that change improved retention.
Telemetry built carelessly creates two new problems: a volume of data nobody reads, and an open endpoint anyone can flood with junk.
Solution
A lean receiver. The game sends events, the service validates and stores them, the dashboard shows what is happening. Token authentication is mandatory, to the point that the service refuses to start without one, on purpose. Batches have a size limit, because abnormal volume is almost always a bug or abuse, not a busy match.
The main decision was about scope: a reading dashboard, not an analysis tool. It answers quickly the questions I actually ask after each update.
Want something like this? Let us talk.
Tell me where your brand is stuck. 30 minutes solves the first part.
Let's talk
