Editorial illustration: Lightweight Custom Analytics: Dalo’s Unity Client Experience

Lightweight Custom Analytics: Dalo’s Unity Client Experience

Introducing Bunny Circus Analytics

Bunny Circus Analytics is a game analytics tool that I, Kian Paknemat, built to provide a lightweight, controllable reporting path. Dalo uses the tool, but its structure is not limited to a card game. You can define another game with its own events, tabs and reports. Lightweight means starting with clear capabilities and understandable maintenance, rather than a promise of unlimited capacity. If you want to turn questions about a small project into reports, this product is a starting point worth examining.

From Unity to a self-hosted dashboard

The tool has two main parts: a Unity component that sends game events and a dashboard installed on your own hosting. The current server runs on PHP and stores information in JSON files; it does not require setting up a database to run. Each game has separate settings and a collection key in the dashboard. Card-game, tower-defense and blank templates help you start from a relevant example. Choosing a template does not automatically generate game behavior. You still need to decide which actions the game will record.

Build a report around a question

For me, the appealing part is building a report around a question. You can define an event such as a level ending, specify its required information, and build a count or average-duration report. Displays include a number, comparison chart, daily report or table. Filters help you examine only winning results, for example. Report definitions can also be exported and reused in another game, provided that field names and meanings agree. This approach lets us pursue a new question without changing every dashboard page.

Capabilities with clear definitions

The Unity client has a local queue and retries for temporary connection problems. However, queue capacity and event sizes are limited, and delivery of every event is not guaranteed. The dashboard also includes day-one, day-seven and day-thirty retention, calculated from a player’s first observation. Device information is available only when the game sends it. These boundaries help us use the tool correctly: behavior reports do not replace performance measurements or verification of actual game results, and numbers must be read in their context.

Start small and maintain responsibly

Self-hosting brings control and responsibility together. Suitable installation, dashboard access, backups and history archiving deserve attention. The current version is designed for small hosting environments and limited history; substantial data growth may require another approach. To start, send a test event and inspect its report, then move on to the next question. Find the full introduction on the product page. Get the source and installation guidance from GitHub, and use Telegram for updates or contact. Beginning with one small question makes this approach easier to evaluate.

Latest blog posts

Independent editorial illustration about Unity Godot Unreal comparison

Unity, Godot or Unreal: Comparing Engines for One Project

Compare engines against the same small project requirements. Rendering needs, export targets, available skills and maintenance matter more than a general.

Read article
Five cute creepy elemental creatures fire ice pumpkin wind shadow

BoomBo: Exploring Elemental Character Concepts

The early visual direction for BoomBo explores cute-creepy elemental characters: pumpkin, fire, ice, wind and shadow. The goal is to make the cast.

Read article
Editorial illustration: Memory Budgets: Assets Have a Cost

Memory Budgets: Assets Have a Cost

Images, audio and runtime objects all occupy memory, even when their files look small on disk.

Read article
Dalo