Cycling management gameIn development
You build the season, write the race plan, then watch from the team car with the radio in hand. The riders decide; you steer them.
Desktop client, single-player, offline · in French and English
The game
Bordure takes the side of the person who isn’t pedalling. You build the season, prepare the team and write the race plan, then watch the race unfold from the car. No commands for power, line or attacks: only intentions.
Seven pillars
The engine did not come from a feature list but from seven pillars, set down before the code and checked by tests.
You issue a plan and radio instructions. Never a power output, a line through a corner or the exact moment of an attack.
With no input at all after the start, the race ends sensibly on the staff’s plan alone.
Opposing teams play the same plans, with the same rules and the same perception as you. No scripted winner.
The interface only receives filtered projections, with their source and their age. Never the engine’s internal state.
An instruction leaves with a delay, gets an acknowledgment, and is tracked per recipient. Repeating an order gives no bonus.
Text, playback speed and pauses have no influence on the race.
Same seed, same content, same commands at the same ticks: same result, on any JavaScript engine.
The post on the race engine follows them one by one, from the tick to the radio.
Read the post on the engine →Simulation
Nobody writes the outcome of a race: not you, not the game. It comes out of the physics, the riders’ energy reserves, groups that form and break up, and opposing teams that play the way you do.
Gradient, aerodynamics and shelter; two energy reserves, one for explosive efforts and one for endurance; groups and gaps that emerge.
Opposing teams play the same plans, with the same rules and the same perception as yours.
What you see is dated and sourced: observed, reported, estimated or unknown. An estimate never looks like a fact.
Same seed, same commands: same race. A statistical calibration bench measures the engine.
Dev blog
Three posts, end to end: what the race engine does, how a season is planned, how you found a team in a draft. Each one exists in French and in English.
Nobody writes the outcome of a race: not you, not the game. Here is what happens between the start and the line: the physics, the riders’ energy reserves, the groups, the AI shared by every team, what each side knows about the race, and a radio that always arrives a little late.
Dozens of races to spread across about twenty riders: nobody should fill in that table by hand. The staff proposes a complete programme as soon as the season opens, you only touch the exceptions, and what you decide is never overwritten.
You can start from a blank sheet: you found a team, then the whole peloton, yours and the opposing teams alike, picks its riders in turn from a single pool. Same rules, same information, no result written in advance.
Screens and figures marked “Demo” are fictional. Bordure is still in development: this site presents the game as it is being built, not a version to download.