Flightgame

Play online: https://noname-ch.github.io/flightgame/ (updates automatically with every push to main)

What we could build next: see ROADMAP.md.

A small airline management game in the browser, in a dark theme. The start screen lets you continue your saved airline or found a new one: pick its name, the mode, the difficulty, your home airport (30 small airports across the world with cheap slots, startAirports in config.js) and your first leased aircraft (ATR 72, Dash 8-400, E190, A220-300, A320neo or 737-800). The default is Bern-Belp (BRN) with an Airbus A220-300.

Quick start (top of the start screen) skips the setup for testing: one click starts a ready-made airline whose planes already fly daily timetables (Swiss regional, European network, Widebodies, Busy hub with 20 planes, Sandbox with CHF 1 billion, Hard start). index.html?preset=<id> (for example ?preset=europe) starts one straight away, on every reload. The presets are in js/data/presets.js.

Run

Open index.html in a browser (needs internet for the map tiles and Leaflet). Or run it locally: ./play.sh starts a small server (tools/serve.py) and opens http://localhost:8000 in the browser; the airport editor saves its fixes through it. Double-clicking index.html (a file:// page) is not enough: browsers block the 3D view's modules there.

Smoke test: node tools/smoke.mjs (Node 22+, Chrome or Chromium) loads the game headless, starts an airline, flies a timetable for a month of game time, opens every section, the airport editor and the 3D view, and fails on any script error. Run it before you push.

How to play

Screen: top left ⋯ opens the menu (save, load, new game, settings with map style and layers, developer tools, exit) and the ✈ button next to it sets the game speed. The tabs in the middle of the top bar open the sections (Fleet, Airports, Slots, Schedule, Marketplace, Finance, Rivals, Log; icons only on narrower screens), and the airline, money, time and day are on its right. Every plane has a card at the bottom: hover it for where it comes from and goes to, the time left and its fuel; click to select, click again for its stats, double-click to follow it (2D or 3D). A yellow ring marks the plane you follow, with an arrow at the screen's edge when it is off screen.

Plane window: clicking a plane (on the map, in 3D or its card) opens its window, as in OpenTTD: a live 3D camera behind it (the wheel zooms), what it is doing, its speed and height, where it comes from and goes to, the time and distance left, the passengers on board and the runways it takes off from and lands on. Runways: for every airport of its day you choose which runway it takes, or Auto: the shortest runway it can use (long enough, paved where it needs that) whose end is within 45° of the day's wind, so the long runways stay free for the big planes; it takes off and lands into the wind. A choice counts at once while the plane still boards at the gate, else from its next flight there (a flight under way keeps its runways); the route lines on the map show the chosen runways. Plane stats: 📊 Stats (in its window or its Fleet card, or its card at the bottom clicked once more) opens its records, like OpenTTD's vehicle details: maker, age, value or lease, speed, range, seats, size class, the runway it needs, its running cost per block hour (more as it ages) and its crew; then flights, passengers, seats filled, revenue, flying costs, its share of the weekly lease and crew, repairs and profit for this year, last year and all time; a bar per week for the last 12 weeks (hover for the numbers); kilometres and hours flown, how often it left on time, incidents, ferry flights and its last 8 flights. A year is the calendar year in story mode, else 365 game days. 🗓 Timetable opens its timetable in a window of its own (also from a plane's row in Schedule). Every window can be moved by its title bar (also the developer tools, the airport editor and build panel, the bug report, the airport checklist and settings) and opens where it was left last time. On a phone a click shows the plane's card in Fleet instead.

Day and night: the clock at the top is the time at your home base; every airport has its own local time (its real time zone, with summer time), shown in the airport panel with sunrise and sunset, and arrivals say the local time there. The sun rises and sets where it really does: the night moves west over the 2D map, and in 3D the sky turns orange at dusk and dark at night, the ground and buildings darken, terminal windows and taxiway centre lines light up, and planes show their red and green position lights, flashing beacons, strobes and landing lights. Runways have their lights as at real airports, seen from far away (tens of km): white edge lights (yellow over the last 600 m), green thresholds, red ends, centre-line and touchdown zone lights on the big ones, a PAPI beside each end (white above the glide path, red below), and approach lights out in front where an airport has them (by its size and the runway's length: the long ones with crossbars, red side rows and the sequenced flashers that run in towards the runway). Control towers carry a red light and the airport's rotating green and white beacon. In fog or heavy rain the lights are on by day too. Terminals, towers, aprons and taxiways show from zoom 11 near the middle of the view (everywhere from zoom 12), runways from zoom 9. Settings → On the map → Day and night turns it off. The clock at the top is your home base's, but every time written out (departures, arrivals, the timetable, an airport's board) is local at that airport, as on a real timetable: a flight from Kathmandu at 07:00 leaves at 07:00 in Kathmandu. The night curfew (no departures 22:00–06:00) is in local time too, and a plane waits at an airport until morning there.

This is the beginning of the README. Read the rest at the original. Read the full README ↗