FUT lost a crucial round against 100 Thieves after xeus’s Spectre failed to fire on Split, turning a mouse-input problem into a fresh competitive-integrity headache for VALORANT Champions Shanghai. The incident happened on September 30, five days after players had reported earlier mouse issues and VCT authorities confirmed a fix; the supplied evidence does not verify a new Riot response after FUT’s match.
The failure matters beyond one lost duel. Champions Shanghai brought 16 teams together to compete for a $1 million grand prize, and the FUT incident put the effectiveness of the earlier intervention back under the spotlight. A fix is only reassuring until the next weapon refuses to cooperate.
On September 25, players from Karmine Corp, Team Liquid and NS RedForce reported mouse problems affecting their gameplay. The primary account says VCT authorities confirmed the cause and issued a fix, but it does not provide technical details about that intervention or establish that xeus’s later malfunction had the same cause. The high-pressure VCT tournament environment leaves little room for equipment failures to be treated as harmless background noise.
A Spectre that would not shoot
FUT and 100 Thieves opened their best-of-three on Split. At 1-1, xeus swung toward 100 Thieves’ vora during a 2v1, but his Spectre did not register the mouse input despite having a full magazine. He switched to his Classic, and FUT lost the round.
The primary account says FUT players had reported PC and mouse problems elsewhere during the tournament, alongside complaints about seating positioned in lighting glare and audio issues that made Spike plants difficult to hear. Those reports paint a broader picture of frustrating match conditions, but they do not prove that each problem shared a single technical cause.
In a tournament where a split-second input can decide a duel, the distinction matters. Fans can debate whether officials should restore a round, but confidence in any ruling depends on clear information about what failed, what was checked and how the decision was reached. Riot’s earlier fix, as described in the source account, is not by itself an explanation of the September 30 malfunction.
Frustration that goes beyond one round
After the match, FUT player yetujey declined to take part in the post-match press conference. The team’s coach, identified as Vlad in the primary account, argued that mouse problems had continued despite assurances they were fixed and said the recurring issues were undermining the work his players had put into the tournament.
That reaction makes the issue harder to file away as an isolated glitch. It does not establish that Riot caused xeus’s failure or that the round should have been replayed, but it does show why a previous fix may not settle the argument when another high-profile problem appears. Riot’s handling of competitive-integrity questions in VALORANT can shape how players and fans judge the process as much as the final score.
The result stands, the confidence question remains
The supplied evidence does not confirm a post-match Riot statement explaining the incident, nor does it establish the precise cause of the failed input. That leaves an important gap between acknowledging earlier technical trouble and explaining what happened in this specific round.
For players, fans and anyone assessing a match result, the practical question is not whether hardware can ever fail; it can. It is whether the tournament can identify the failure, communicate the ruling and give teams confidence that the same conditions apply to both sides. In Shanghai, xeus’s silent Spectre has made that question impossible to ignore.
