PortuguêsPlay

Behind the scenes

Behind the scenes of Hexapulso

Hexapulso is made by a single developer. These articles explain, without hiding the limitations, how the parts of the game that don’t show on screen work.

How the leaderboard verifies every runHexapulso doesn’t accept the result the browser reports: the server replays the whole run from the keys you pressed. Here is how, and what that guarantees.The fairness rule for the wallsHow Hexapulso works out the distance between two rows of walls so there is always time to reach the gap, and how a bot checks it.Music with no audio filesHexapulso ships no music files at all: everything is synthesised in the browser while you play, and the track gains layers as the run heats up.Seasons, podiums and badgesHow Hexapulso’s 4-week seasons work, who reaches the podium, what each place earns and how each season’s badge is drawn.

The idea that organises everything

The game is split into two parts. One is the core: the rules of a run, with no drawing, no sound and no clock. The other is the client: everything you see and hear. The core is the same file in your browser and on the server, and it always gives the same result for the same keys. That is what lets the server replay your run, lets the game show anyone’s replay, and gives battles a referee that is neither of the two players.

When an update changes a rule (speed, points, a wall pattern), the core gets a new version number and the previous version is kept. That way old replays can still be watched and checked against the rules they were played under. The game is currently on the sixth version of the core.

About the numbers

Several values in the game (daily challenge goals, pause limits, the starting battle rating) were chosen by estimate and tested with a bot, not measured with a large number of players. The articles say so where it applies. Whatever changes shows up in What’s new.