The video highlights Cloud Imperium Games’ struggle with maintaining and updating Star Citizen’s decade-old legacy code, which hampers stability and complicates the simultaneous development of new features and Squadron 42. It suggests that prioritizing a stable, minimal viable product for the persistent universe before Squadron 42’s release could improve player experience and reduce negative feedback, despite ongoing efforts and challenges.
The video discusses the ongoing challenges faced by Cloud Imperium Games (CIG) in developing Star Citizen, particularly focusing on the legacy code base that underpins the game. With parts of the code being over ten years old, maintaining and adding new features has become increasingly difficult. Unlike other older games, Star Citizen is unique because it is simultaneously an aging codebase and a cutting-edge project with constant new content and technology being integrated. This duality places CIG in a difficult position, having to deliver new features rapidly to maintain funding while also addressing bugs and ensuring compatibility with Squadron 42.
A major issue highlighted is the lack of time and resources to properly maintain or refactor existing code, leading to persistent bugs and instability. The core architecture and services are under strain due to continuous additions without sufficient optimization. Ideally, CIG would pause new feature development to focus on fixing and refactoring, but this is complicated by business pressures, manpower limitations, and the ongoing focus on Squadron 42’s release. Although some refactor efforts are underway, such as work on transport services and VR support, many parts of the code remain outdated and problematic.
The video warns of potential negative consequences for Squadron 42 upon release, as the single-player experience may attract many players who then transition to the persistent universe (PU) and find it unstable and unpolished by comparison. This disparity could lead to unfavorable reactions and reviews. The suggested approach for CIG is to identify a minimal viable product (MVP) for the PU that prioritizes stability and playability, focusing on reliable core gameplay elements like persistence, inventory, UI, and mission completion. The goal is to provide a smoother experience that can retain new players transitioning from Squadron 42.
Comparisons are made with other MMOs and live service games, which also face legacy code challenges but manage stability better due to longer development cycles and extensive internal and player testing before releases. Star Citizen’s shift from quarterly to monthly updates has reduced testing time, exacerbating stability issues. However, CIG appears to be moving toward a hybrid approach where content updates continue monthly, but major technical changes are delayed until fully ready, potentially improving stability over time.
In conclusion, legacy code issues are common across software development and have no simple fixes. Solutions range from complete rewrites to incremental refactoring, requiring significant effort and planning. The video invites viewers to share their opinions on whether CIG should stabilize the PU before Squadron 42’s launch or revert to a quarterly patch cycle. Despite the challenges, the video acknowledges ongoing efforts and expresses hope for gradual improvement in Star Citizen’s stability and player experience.