Alliance Tournaments FAILED Again: Bugs, Bad Communication & Broken Trust | Talking Trek

Alliance Tournaments were supposed to return improved. Instead, Star Trek Fleet Command got another disaster. In this episode of Talking Trek, DJz reconstructs exactly what happened during the August 10 Alliance Tournament rerun, beginning with the conversations that happened before launch and the problems Scopely believed it had fixed. Within minutes of the event beginning, severe lag returned and players discovered an entirely new issue where Alliance Tournament task groups began blending together. High-value tasks disappeared, rerolls appeared to progressively downgrade task options, and some alliances were eventually left staring at boards filled almost entirely with low-value tasks. But the biggest failure of the day may not have been technical. We examine the lack of official communication while the problem unfolded, Scopely's eventual declaration that the issue had been fixed, the mid-event tournament reset, and the discovery that the “fix” hadn't actually fixed the underlying problem. DJz explains what happened to player scores during the reset, which players were potentially hurt the most, and what compensation should look like after such a disruptive event. Then we get into the larger question: how does STFC prevent this from happening again? If Alliance Tournaments function correctly in a development environment but collapse when thousands of real players hit the system simultaneously, should Scopely create a dedicated live test server? DJz proposes cloning player alt accounts onto a server operating 72 hours ahead of the rest of the game, allowing real players to stress-test events before they reach the entire galaxy. We also tackle the bizarre Player Council voting rollout and open the microphones to members of the community and alliance leadership to hear how the day affected their players. And yes, there actually IS some good news: the Gilded Shackle is being fixed so its G7 cost efficiency applies to resources, materials, AND ship parts. The larger question after August 10 isn't whether bugs will ever happen again. It's whether Scopely can learn from them, communicate when they happen, and rebuild the trust that each failure costs. Tell us below: What would Scopely need to do to make Alliance Tournaments right? 00:00 - Gilded Shackle Gets a Major Fix04:14 - Alliance Tournaments: What Happened?05:13 - The Decision to Rerun Alliance Tournaments06:03 - The Four Problems That Needed Fixing07:00 - Why DJz Supported Running It Again11:39 - Testing Looked Ready Before Launch11:56 - 11AM Launch & The Lag Returns14:41 - A Brand-New Task Bucket Bug Appears16:15 - Task Groups Begin Blending Together17:25 - Rerolls Push Alliances Toward Smaller Tasks17:59 - Cam, Connor & The Product Team Get Involved18:34 - The Communication Failure Begins20:39 - Nine Words of Official Communication23:39 - Hours Pass Without a Real Update25:18 - DJz Writes the Announcement Scopely Should Have Sent27:07 - Five Things Every Crisis Communication Needs28:07 - The Official Update Falls Short29:17 - “Mission Accomplished”: Scopely Says It’s Fixed30:15 - What Happens to Players During the Reset?33:06 - Why Your Old Score May Look Missing37:09 - The 3:45PM Alliance Tournament Reset40:11 - The Fix Starts Breaking Again41:13 - Communication Becomes the Bigger Failure42:00 - Why Didn’t Testing Catch This?47:37 - “Bundle Cohesion” Breaks Under Live Load48:50 - The Reset Was Only a Stopgap49:23 - Scopely Needs More Engineering Help49:49 - DJz Says: Pull the Event56:21 - What Should Compensation Look Like?56:51 - No Promotions or Relegations This Run?1:10:24 - The Damage to Player Trust1:13:51 - Testing Under Real Player Load1:15:25 - Proposal: A 72-Hour Early Live Test Server1:25:09 - Can This Disaster Become a Catalyst for Change?1:26:41 - The Player Council Voting Disaster1:31:30 - The Community Calls In1:45:19 - Alliance Leadership Reacts to the Reset1:49:54 - Fisty Joins: “Players Were Just Mad”1:53:22 - Did This Damage Camero