Development process

They attribute recurring mission breakage to huge content volume, complex interactions, missing automated regression testing and a brittle Mission 1.0 toolset, and say they plan more automated testing and focused robustness work.

A bug-fix check-in that shouldn't have been in the stream made Idris ships incompatible with their saved copies, so game servers crashed on spawning them until Idris spawning was paused and the ships were manually fixed.

Beausejour says 4.8 involved constant firefighting, including two bad check-ins that broke persistence, though the overhauled entitlement system worked well, and Lind says extra protection against such check-ins is needed.

Benoit Beausejour says the game is still being turned into an MMO and content and features are outpacing the guardrails and cross-system validation, so the team needs to add stronger validation.

The team credits a planned year of quality of life and content, a larger vehicle team, process changes and support from other teams for the record number of ships, calling it challenging but good.

Backlog ships that depend on missing gameplay features won't be started, so the backlog has shrunk without additions and its pool is slim, leaving a balance between new ships, upgrades and backlog releases.

Gold standard means bringing an existing ship up to the features and functionality it would have if released today, without stylistic changes that remove its core identity; no 2026 list is given.

A rework is for ships whose existing design doesn't fit their role, gold standard adds missing features, and a Mark II expands a ship that still works; an Aurora gold standard and Mark II are confirmed.

No quantified speed or quality figures can be given yet because a whole planet can't be made and supporting systems aren't done, though quality is already better in some areas and they won't mass-produce planets.

A planet can be built with the tech now as a vertical slice but not to shippable standard, so features will arrive piece by piece, with some planet-patch tech already in 4.0 streams.

Nothing about taming or pets is in active development right now, but it remains a committed stretch goal, with NPC pet systems being worked out that could be built on later.

They agree AI is a nexus of many systems and must look readable and sensible to players, so they add fallback cases and balance it against being too efficient, while feeling pressure to ship experiences, bugs included.

It was partly a eureka moment, but the big change needed approval from many teams, who had to be convinced it wouldn't break racing and other systems.

Feedback has been mixed, with many questions from the community, but internal testing is positive, and they say the questions will be hard to answer until they show it working.

The Polaris has had its interior concept finished, a hangar that now meets the standard hangar metrics, and capital-level components, but it isn't in active development and nothing more will be shown until it is.

Building Blocks now lets game designers and artists across the company build UI themselves, has gained 3D model support, first seen in inventory, and now has reusable, restylable pieces such as buttons.

Support work has grown, mostly debugging calls during releases, but Bone sees it as positive and easier than the old end-of-cycle UI crunch, while Simon says some teams' UI files get tidied up.

There is nothing tangible yet, but a designer has proposed an interior redo for the 600i, including a docking collar, which still needs to go to concept.

John Crewe isn't aware of major Sabre Raven issues, and fixes previously made only to the baseline Sabre were carried over to the Raven in 3.12; further problems should go to the Issue Council.

The team says older ships will get equal gameplay functionality and aren't ignored or underplayed, and that visual updates will come when the time is right, since reworking too early means redoing the work.

The team definitely plans more customization like the 300 series, including cockpit decorations, but weighs it against the schedule delay it adds to a ship's release.

Planet Tech V4 removes much paperwork and is more artist-focused, taking simple planets from weeks to days, though the speakers can't estimate how long entirely new planet or biome types will take.

Planet Tech V4 is not called final, but it is seen as a solid foundation to iterate on, with nothing currently warranting a V5, though they won't rule one out.

Secondary movement does emerge from concept's drive to be new and interesting, but reusing existing assets is more efficient, so new animations or parts are used only where they're essential to the ship.

No real status list is given; ships sit somewhere between not started and done, and with only about five vehicle teams working at once, some ships take a long time to appear.

AI is called the biggest remaining risk to the Squadron 42 schedule, with too few AI programmers and more being sought, alongside the time needed for content and polish.

A rework scraps almost everything and rebuilds a ship from scratch, while an improvement targets one area, such as a cockpit interior or adding hatches for components, without rebuilding the whole ship.

Not everyone dislikes the Redeemer, but it was found to have problems and not fit current standards, so it needs a from-scratch redo that will bring it back as a proper gunship.

The Hammerhead has six manned turrets, the mismatch came from a late design change, and the outdated mass and dimensions are due to be updated though they may still change.

Chris outlines what he wants, and for cargo the requirements, such as a grid, physical cargo and kiosks, largely fell out of the design, which made it easy to pitch to the team.

Engineers receive a feature request with user-story-style steps from design, then work out the underlying systems, resources and timeline, raise concerns early, and plan in a kickoff meeting.

Mocap uses improvised props such as PVC pipe, plywood, scaffolding and ladders since only the measurements matter, and some shoots have used wire work.

Production and management set goals for a release, the team checks existing animations, then plans in detail what and how to shoot, since pre-production avoids capturing unusable footage.

They are focused 100% on Star Citizen, plan frequent content updates and more Squadron 42-style story experiences for years afterward, and have no plans for non-Star Citizen projects.

Elijah McNeil says direction varies, from briefs or Jump Point requests to filling in hangar spaces with a lot of freedom, though Chris O as visual director has final say.