Last night's matches were full of drama, with one particular match bringing about images of Déjà Vu from Season 8 playoffs with zEx. The TEC vs. 3D match resulted in a win for 3D, however, several members of TEC were crippled by "packeting" - malicious attacks designed to flood a person's bandwidth so their internet connection becomes nearly unusable. This could have been the match of the night and it's sad to see what some members of the community will stoop to in order to see their favorite team win. Members of TEC elaborate on yesterday's situation inside, click below to view. Unfortunately, other playoff matches were affected by packeting as well, including the Rival vs. e7 match and the TSG vs. SYB match.[break="click for match results and more"]3D over TEC - (13-7)(5-7 3D as T)(8-0 3D as CT) - Demo
TEC had a good chance at winning this match. That chance was all thrown out the window though with internet troubles suffered by several members of TEC. Gouki and Elude offer their views on what happened in their match:
TEC|Gouki: I wish it could have been on an equal playing field, it really sucks being crippled like that. It's over and done with though, and TEC wishes 3D luck in the rest of the playoffs =)
TEC|elude: I'm disappointed at the people in the CS community, that they would go as far as to packet an online match that basically means nothing except braggin rights. I'm fairly confident had our luck been different with the whole team's internet the match results would have been a lot closer. What fun do people get out of ruining our games? I really don't understand why? I'd like to add Good luck to 3D in the rest of playoffs, hopefully their luck is better then ours.
e7 over Rival - (13-11) (4-8 e7 as CT)(9-3 e7 as T)
Apparently TEC isn't the only team that claims to have been packeted last night. Rival was up 11-4 in their match when Icesalmon and Jaden started getting connection problems and also administrative issues.
Rival|cripple: The packeting is very unfortunate. As a whole the CS community is growing, the more it grows the more people will attempt things like this I think. A similar situation happened last CPL when people intentionally disconnected power to computers while matches were being played. I think better guidelines need to be developed for these types of situations. Our two players being "packeted" ran router scans of some sort and have the logs of when the "packeting" started, so we know for sure it was someone trying to sabatoge the match.
TSG over SYB - (16-13) (3-9 TSG as T)(9-3 TSG as CT)(4-1 TSG in OT) - Demo
Just when you didn't think the situation could worsen, right? Well, it did, but in this instance a team overcame their technical difficulties to win their match. Sunman and cbz of TSG feel that they were packeted during the beginning of their match versus SYB last night but managed to evade the attacks of the would-be hacker. SYB managed to do well enough against the TSG powerhouse, bringing them to overtime, but fell short in the end.
TSG|shaGuar: SYB got off to a great start in the match going up about 7-0, then we steadily began to gain some late T rounds, and sunman and cbz began to get blatently packeted, and we were only able to get 3 rounds. Then before we began the CT side, we waited about 15 minutes and the ping seemed fine and packets gone, so we did a fake "LIVE" and 30 seconds in the round they got packeted again. Luckily they were at the stomping grounds LAN center and were able to get on a seperate private connection and play out the match packet free for the remainder of the game.
u5 over shock - (13-4)(11-1 u5 as T)(2-3 u5 as CT) - Demo
Incredibly, the only match last night that was played without any technical issues was the oddball of the matches. No packeting took place here, only a bout of skill between two amazing teams. In an earlier match in the regular season of CAL, shock beat u5 13-11 and many expected their playoff match versus each other to end up with another close score. u5 defied expectations though and forced shock to struggle to get any rounds at all.
u5-hare: Correct [there was no packeting]. I think we were the lucky ones
Is the CS community taking online league play far too seriously and would go to any length to see their favorite team win? Should CAL attempt to protect teams against packeting? Are the planets aligned in such a way causing players of CAL-i matches to get sporadic pings and the packeting is all in their heads? We want your feedback!
TEC had a good chance at winning this match. That chance was all thrown out the window though with internet troubles suffered by several members of TEC. Gouki and Elude offer their views on what happened in their match:
TEC|Gouki: I wish it could have been on an equal playing field, it really sucks being crippled like that. It's over and done with though, and TEC wishes 3D luck in the rest of the playoffs =)
TEC|elude: I'm disappointed at the people in the CS community, that they would go as far as to packet an online match that basically means nothing except braggin rights. I'm fairly confident had our luck been different with the whole team's internet the match results would have been a lot closer. What fun do people get out of ruining our games? I really don't understand why? I'd like to add Good luck to 3D in the rest of playoffs, hopefully their luck is better then ours.
e7 over Rival - (13-11) (4-8 e7 as CT)(9-3 e7 as T)
Apparently TEC isn't the only team that claims to have been packeted last night. Rival was up 11-4 in their match when Icesalmon and Jaden started getting connection problems and also administrative issues.
Rival|cripple: The packeting is very unfortunate. As a whole the CS community is growing, the more it grows the more people will attempt things like this I think. A similar situation happened last CPL when people intentionally disconnected power to computers while matches were being played. I think better guidelines need to be developed for these types of situations. Our two players being "packeted" ran router scans of some sort and have the logs of when the "packeting" started, so we know for sure it was someone trying to sabatoge the match.
TSG over SYB - (16-13) (3-9 TSG as T)(9-3 TSG as CT)(4-1 TSG in OT) - Demo
Just when you didn't think the situation could worsen, right? Well, it did, but in this instance a team overcame their technical difficulties to win their match. Sunman and cbz of TSG feel that they were packeted during the beginning of their match versus SYB last night but managed to evade the attacks of the would-be hacker. SYB managed to do well enough against the TSG powerhouse, bringing them to overtime, but fell short in the end.
TSG|shaGuar: SYB got off to a great start in the match going up about 7-0, then we steadily began to gain some late T rounds, and sunman and cbz began to get blatently packeted, and we were only able to get 3 rounds. Then before we began the CT side, we waited about 15 minutes and the ping seemed fine and packets gone, so we did a fake "LIVE" and 30 seconds in the round they got packeted again. Luckily they were at the stomping grounds LAN center and were able to get on a seperate private connection and play out the match packet free for the remainder of the game.
u5 over shock - (13-4)(11-1 u5 as T)(2-3 u5 as CT) - Demo
Incredibly, the only match last night that was played without any technical issues was the oddball of the matches. No packeting took place here, only a bout of skill between two amazing teams. In an earlier match in the regular season of CAL, shock beat u5 13-11 and many expected their playoff match versus each other to end up with another close score. u5 defied expectations though and forced shock to struggle to get any rounds at all.
u5-hare: Correct [there was no packeting]. I think we were the lucky ones
Is the CS community taking online league play far too seriously and would go to any length to see their favorite team win? Should CAL attempt to protect teams against packeting? Are the planets aligned in such a way causing players of CAL-i matches to get sporadic pings and the packeting is all in their heads? We want your feedback!
Comment