An official livestream by Cloud Imperium Games ends in complete chaos as the Star Citizen developers struggle with bugs. The reactions are scathing.
What alpha players have known for years is now on full display for the whole world to see:Star Citizen is far from finished.
Developer Cloud Imperium Games posted aofficial livestreamsuffered a major setback in the eyes of the public—and has been facing harsh criticism for weeks now.& nbsp;What happened?
“The Game as It Should Work”
What was intended to be a demonstration of the intended gaming experience ended in countless bugs, massive frustration, and palpable tension within the team at Cloud Imperium Games (CIG). Star Citizen, a supposed flagship PC project that has been in development for over 14 years and funded via crowdfunding with over one billion U.S. dollars, revealed its far-reaching technical issues on camera.
The event was actually supposed to show how the gamefunctions under optimal conditions. Since the Public Test Universe was suffering from severe performance issues at the time, the team switched to an internal build. Host Jared Huckabe explained at the start of the stream that they wanted to demonstrate the planned vision:
“We’re not playing on the PTU today because it’s not quite delivering what we want it to. That’s why we’re playing on an internal build. This is the game as it’s meant to work.”
However, the reality on the internal serversproved far from optimal and severely hindered gameplay.
Technical Glitches
Instead of a smooth experience, the developers were confronted with serious bugs during the “Siege of Orison” mission. Swapping weapons didn’t work reliably, accessing the inventory was glitchy, and equipment disappeared.
In a particularly bizarre moment, developer Ollie realized in the middle of combat that he had inadvertently swapped out his medical kit, commenting that he had dropped his healing tool for “this damn toy.”
Shortly afterward, the YouTuber—who now works on CIG’s video team—panicked when he ran out of ammo: “I’m out of damn bullets. Reload, reload. I don’t like this at all.” His colleague Max remarked with agood dose of gallows humor:
“We’ve fixed the bug where you die if you’re not standing exactly in the middle of a shuttle. So everything’s perfectly fine.”
Frustration Among the Developers
The ongoing technical glitches took their toll on the atmosphere. As time went on, the frustration among the developers involved grew noticeably. Instead of working together constructively, a passive-aggressive mood set in.
The team began hurling derogatory remarks at one another, and the situation culminated in players intentionally killing their own teammates.The chaosreached its final climax during the mission’s boss fight: All player characters died on-screen.
Developer Elliot had to face the sobering reality: “We’ve all been wiped out—it’s a party wipe. I think we’re locked out of this build now. Our time’s up, guys. We lost.” Since there was no chance for another attempt, the stream was cut short after just under two hours.
One closing remark in particular caused some confusion afterward. Jared Huckabe emphasized that he wasproud of the team’s workand wanted to release this build as soon as possible so that players could have exactly the same experience.
No comments?To support our moderation efforts, the comments section for this article has been moved to our forum. Please follow our rules to ensure a pleasant discussion environment.
Within the community, this statement—whether an expression of personal frustration or a twisted joke—was met with disbelief. Comments under the video described the event as unpleasant, forced, and, in some cases, eerie. It felt like a hostage video where nobody was having fun. Many observers were surprised that those responsible didn’t take the recording offline afterward.
