Development diary: 11 November 2026 · Two-day development update
On Galaxy, we tested how the 100-sector build handles hundreds of pilots spread across the map and dozens gathered in one busy sector. We also made arrivals and departures visible and gave two exploration sites their own models.
What changed
- 500-client load tests. Galaxy met its server timing target in two of three runs across 12 workers. These are test results, not a confirmed launch capacity. The next steps are improving client update delivery and validating performance at a larger scale.
- Galaxy deployment. The new server was updated to protocol 47. All 100 sectors were assigned, and saving passed health checks.
- Single-sector tests. All 50 test clients met the short test’s timing and update criteria. All 64 stayed connected in the larger run, which exceeded the server tick budget.
- Server optimisation. Moved more simulation work into native code, reused traffic calculations, batched patrol work and improved how the server sends updates. Replication and collision emerged as major costs in a crowded sector.
- Visible docking and launching. An external camera shows the ship travelling through the tube. Departures wait for clearance, count down and return control once the whole hull is clear.
- Reactive effects. Added brighter faction shields, cooling scorch marks, muzzle heat, mining fractures, cockpit lighting and jumpgate ripples. Gate paint reflects local territory.
- Authored anomalies. The Open Moon and Winter’s Grave gained fractured lunar rock and glacial debris models in place of their earlier procedural shapes.
- Modular Pirate stations. Six designs built from reusable parts became flyable in a separate prototype sector.
This entry records development at the time. Features, names, figures and test results may have changed since then.