An Open Letter to Cloud Imperium Games Dear Cloud Imperium Games team, For almost ten years, I have followed and supported the development of Star Citizen and Squadron 42 both as a backer and as a content creator. Throughout that time, there have been remarkable highs, painful lows, excitement, disappointment, and renewed hope. Today, after almost fourteen years of development, we have reached a point where neither silence nor excuses will help these projects move forward. I am writing this because I still believe in their potential and because constructive feedback deserves to be heard and taken seriously. Communication Must Change From my perspective, communication is currently the most urgent issue. The situation is serious. Many players are deeply disappointed, critical discussions and videos are spreading across the internet and CIG remains largely silent. Legitimate questions remain unanswered, respectfully written Spectrum posts are being removed, and there is little meaningful dialogue between CIG and the people supporting the project. This needs to change. It is clear that many supporters still want to believe in Star Citizen. But CIG must step forward and speak openly about the problems. Tell us what is going wrong, why it is happening, what is being done, and where the priorities lie. If plans change, explain why. If mistakes were made, acknowledge them. If a problem cannot currently be solved, say so honestly. It would be unreasonable to expect every issue to disappear overnight. Expecting honesty, however, is entirely reasonable. I am not asking for another polished corporate statement or marketing presentation. I am asking for genuine, transparent communication on equal terms with the people whose support made it possible to build Cloud Imperium Games and develop both titles in the first place. Communication must also be a dialogue, not merely a series of announcements. Spectrum and the Issue Council should not feel like places where feedback disappears into a void. It should be clear which major issues have been acknowledged, which are being investigated, which have been prioritised, and which cannot currently be addressed and why. Naturally, not every suggestion can or should be implemented. But respectful criticism deserves a meaningful response, especially when the same concerns have been raised repeatedly for years. A Missed Opportunity The Star Citizen Live episode from two weeks ago could have been an important opportunity to begin such an honest conversation. Instead, it demonstrated that several long-standing problems remain unresolved. Even at 30 server FPS, the AI performed poorly, while server-side issues such as the reload bug and desynchronisation continued to occur. Why were these issues not discussed during the show? What causes them? How close is CIG to resolving them? What have the developers learned? Instead of almost two hours of bug-ridden gameplay the same kind of experience regularly seen on Twitch and YouTube the programme could have addressed current concerns and offered meaningful technical and design insight. That would have been valuable. Instead, another opportunity for honest communication was missed. Quality and Accountability The recurring cycle of releasing unstable updates and then spending weeks or months firefighting their consequences must end. Serious issues are repeatedly reported during testing, yet many still reach the LIVE environment. If a build is not ready, delaying it should be considered a responsible decision not a failure. A smaller, stable update is more valuable than a larger patch whose central features cannot be used reliably. The “Year of Quality” in 2025 did not do nearly enough to make Star Citizen a genuinely reliable experience. While I appreciate the improvements introduced with Alpha 4.9 and the progress visible in Alpha 4.10, considerably more needs to happen. Players should be able to log into the LIVE environment and actually play. Alpha or not, quality matters not only regarding bugs, but also in game design, rewards, progression, and respect for the time players invest. Losing progress because of a bug is not difficulty. Repeating content because of a server failure is not meaningful gameplay. Spending hours preparing for an activity only to have it fail for technical reasons does not respect the player’s time. What Needs to Change If Star Citizen and Squadron 42 are to succeed in the long term, continuing as before will not be enough. CIG should: * Communicate transparently, openly, and honestly. * Address the current situation directly instead of remaining silent. * Explain major problems, their causes, and the intended solutions. * Respond to respectful criticism and constructive feedback. * Establish a visible feedback loop through Spectrum and the Issue Council. * Acknowledge mistakes and explain what will change. * Prioritise reliable core gameplay over additional content. The Time for Change Is Now To be clear: I stand behind Star Citizen. I want this game, and Squadron 42, to become a genuine success. I would not be writing this letter if I no longer cared. This is not an attack on the developers working hard to create something extraordinary. It is an appeal to the leadership of Cloud Imperium Games to address the issues placing both projects at risk. For many years, people have supported this vision with remarkable patience, loyalty, time, and money. That support should never be taken for granted. Under the current conditions, and especially with the current approach to communication, CIG risks losing something that cannot easily be restored: trust. There is still a strong desire to believe in Star Citizen and Squadron 42. But that belief must be supported by honesty, dialogue, accountability, and visible progress. The time for change is now. -Knebel