The weekend’s UG Birthday Cup, organised by the Underground CS2 community (known as ‘Red UG’), was intended first and foremost as an opportunity to compete together and celebrate the project’s latest birthday. The free tournament attracted many teams from the Polish Counter-Strike 2 scene, and the organisers emphasised from the outset that the event was intended to have a more relaxed, community-focused atmosphere. Unfortunately, instead of the excitement of the matches themselves, the biggest talking point turned out to be the quarter-final between Adversa Esports and the Turkish Federation.
In the hours that followed, the organiser published an official statement setting out their own account of events and admitting to a mistake made by an administrator. The editorial team at Superion.gg also had the opportunity to review the account provided by the Adversa Esports players and the evidence documenting the entire situation. A comparison of both perspectives reveals that several discrepancies arose surrounding this match, which sparked widespread discussion within the community.
Although each side presents its own version of events, one thing remains indisputable. The organiser itself admitted that, during the FACEIT server outage, the administrator made a mistake. By restarting the match instead of following the procedure to suspend the match or resume it at a later time. It was this very moment that sparked the whole commotion, which ultimately led to one of the most high-profile debates of recent days on the Polish CS2 scene.
The server failure and the administrator’s decision triggered a cascade of problems surrounding the UG Birthday Cup
According to information provided by the organisers and participants, the first map was dominated by Adversa. However, during the match, the FACEIT servers crashed, interrupting the game whilst the team was leading. It was at this very moment that a decision was made which was later described by the organisers themselves as a mistake.
The administrator responsible for managing the match decided to restart the match from 0–0. As Underground CS2 later admitted in an official statement, the match should instead have been paused or restored. Once the restart had been carried out, this option was no longer available. As a result, the organisers lost the opportunity to resolve the issue simply.
From that point onwards, discussions began between the administration and both teams regarding how the match should proceed. The organiser stated that several options were considered… Ranging from playing the match on a private server, to awarding the first map to Adversa in a BO3 format, to a complete restart of the match.
Adversa’s representatives, on the other hand, claim that from the very beginning they proposed solutions designed to ensure the greatest possible fairness in the match. According to their account, one of the ideas was to start a new match by manually recreating the score through conceding the appropriate number of rounds. This approach was intended to preserve the natural economy of the second half. Ultimately, none of the proposals were implemented quickly, and the protracted discussions meant that the whole situation became increasingly tense.
Both sides, however, agree that the technical fault and the administrator’s erroneous decision triggered a series of events which, with every passing minute, became increasingly difficult to resolve in a manner satisfactory to all participants.
Two different accounts of the same event
Following the publication of the official statement by Underground CS2, the editorial team at Superion.gg also received a detailed account from the Adversa Esports players, along with materials documenting the course of the discussions held throughout the incident. A comparison of the two versions shows that the parties have differing perspectives on the course of events in several respects.
One of the most frequently discussed topics was the issue of cooperation in finding a solution. In its statement, the organiser wrote that Adversa only expressed a willingness to compromise after some time had passed. In contrast, a team representative claims that various options for resuming the match were proposed from the outset. Furthermore, discussions with the administration lasted for over ten minutes even before the match was set to restart.
There are also discrepancies regarding the atmosphere during the discussions. The organiser’s statement mentioned offensive messages directed at the administration. However, materials provided to the editorial team suggest that Adversa does not agree with this account of events. At the same time, it points to messages which, in its view, were of a provocative nature from its opponents. However, given the conflicting accounts, it is difficult to assess the course of this exchange unequivocally.
The materials provided also included messages from the administration announcing the planned award of a walkover victory to Adversa. Ultimately, however, this decision was not upheld. Instead, following the refusal to play the next match, the result achieved after the match was restarted remained the official result. Regardless of the differences between the two accounts, the common thread remains the fact that the whole situation began with an erroneous decision by the administrator. The organiser admitted to this in their statement. It was this very moment that led to further misunderstandings and caused the sporting competition to take a back seat.
Lessons for the future are more important than the drama itself
The whole situation shows how little it takes for even a promising tournament to be dominated by discussions about administrative decisions rather than the events on the server. It is also worth emphasising that the organiser did not try to hide their mistake and openly admitted that the first restart of the match was the wrong decision. This is certainly a step in the right direction. However, transparency alone is not always enough when participants feel they have been wronged.
The incident at the UG Birthday Cup could serve as a valuable lesson not only for Underground CS2… but also for other organisers of amateur and semi-professional tournaments. Clearly defined procedures in the event of a technical fault, experienced administrators and swift communication with participants often determine whether a problem can be resolved within a few minutes or whether it escalates into a debate lasting several hours that involves the entire community.
Ultimately, the biggest loser in the whole situation seems to be the tournament itself, with the sporting excitement taking a back seat. We can only hope that the lessons learnt from this weekend will help to avoid similar problems, whether in future editions of the UG Birthday Cup or at other events.
English 
Polish 