[CSGO] Copenhagen Games 2013 勝部半決賽17:00
*更新: 賽程http://www.hltv.org/?pageid=45&eventid=1094&bracketid=643
NiP闖進總決賽坐等敗部冠軍上來
[敗部]
fnatic vs. Western Wolves
http://www.hltv.org/match/2238313-fnatic-western-wolves-copenhagen-games-2013
Quantic vs. VG
----------------------------------------------------------------------------
[勝部決賽] NiP 2:0 Virtus.Pro 3/31 00:40
http://www.hltv.org/match/2238306-nip-virtuspro-copenhagen-games-2013
1st - de_dust2_se 16:13
2nd - de_nuke_se 16:11
Stream http://www.twitch.tv/fragbitelive
[勝部半決賽]
Quantic 1-2 Virtus.pro
NiP 2:0 fnatic ( 16-4, 16-8)
[勝部4強]
http://www.hltv.org/news/10355-nip-vg-virtus-march-on-at-cph-games
Quantic Gaming 2:0 mousesports (16-4, 16-5)
Virtus.pro vs. Western Wolves (更看好俄羅斯)
Ninjas in Pyjamas 2:0 VeryGames (16-11, 16-2)
Lemondogs 0:2 fnatic (7-16, 14-16)
the third and final day of Copenhagen Games, whose first matches are
scheduled to start at 17:00.
NiP vs. VG
GOTV: hltv2.verygames.net:27064
Twitch: http://www.twitch.tv/copenhagengamescs
敗部
http://www.hltv.org/?pageid=45&eventid=1094&bracketid=643
這個賽程真的超猛的.......
此外 令人感到遺憾的是Na'Vi在小組賽後退出賽事
http://www.hltv.org/news/10353-navi-pull-out-of-cph-games
Na'Vi在小組賽2-1贏了fnatic後，造成了Na'Vi/fnatic/Epsilon 3搶2的局面
在比較地圖勝利數時，三隊都是3W3L
所以adm又把對戰BX3的成績一起考慮進來
fnatic/Eosilon 2-0 BX3
Na'Vi 2-1 BX3 (註:第一場Na'Vi的電腦未能於比賽規定時間就緒，被adm直接判輸掉
第一張圖，而Na'Vi連贏兩張圖回來)
在結算後 很顯然 Na'Vi掉到第三
Na′Vi then protested against this, saying that the rounds between the tied
teams, rather than the maps, had to be counted. Based on this, the Ukrainian
team would go through as the top-placed side, followed by Epsilon and then
fnatic, who would have to play in the Lower Bracket.
Na'Vi 接著對此判決抗議，認為應該是比較三支隊伍的Round Difference
(贏的局數扣掉輸的局數)
如果按照此慣例，Na'Vi第一，fnatic第三
adm覺得有理 但在30分鐘的會議討論後決定維持原來的判決
於是 Na'Vi的CEO Alexander "ZeroGravity" Kokhanovsky 宣布退出本次比賽
並說到
"他感到非常失望，我要求所有認識我的的隊伍與信任我的電競工作人員
一起思考我們這次所受到的待遇。下禮拜Na'Vi將與其他有前景的隊伍
一起創立一個電競協會，此組織將會為現代電競帶來劇烈的改變。"
我個人的從CS1.6看到現在的印象是
小組賽如果出現積分相同的情況下 都是3搶2的隊伍來比RD(小分)
很少聽到再比地圖數
不過有外國鄉民跟我說 如果要比RD 小組賽會要求每場都打滿30局
加上Na'Vi在打BX3時 也出現了管理人員的爭議
http://www.hltv.org/news/10340-navi-bx3-default-is-unfair
Na′Vi manager Igor "Caff" Sidorenko跟HLTV陳述
由於賽事網站上的賽程表定他們第一場從10:00開始
於是他們9:00就到場， 結果只看到入場登記處有少許工作人員在
他們詢問工作人員接下來他們要做什麼因為他們還要去拿租來的電腦並且登記
沒有人知道答案只告訴他們10點過來就對了
所以他們10點整過來，他們登記入場後ADM告訴他們
5分鐘內要開始比賽否則判輸掉第一張地圖
而他們租來的電腦有一台出現了狀況
adm幫他們更換了電腦 大概花了半小時
Na'Vi從0-1開始
以下是賽事官方的回應
http://www.hltv.org/news/10357-admin-comments-on-navi-dropout
"This morning, Na′Vi showed up at 9 and asked our receptionists when the
matches started," she told HLTV.org. "They were told it was at 10, and at
10:14 they showed up at the venue to collect their rented PCs and set up to
play.
Na'Vi 10:14才出現，我們給他們15分鐘，意思是他們最多遲到30分鐘
否則第一張直接判負，而他們未能在10點半前搞定 所以第一張圖由BX3拿下
第二張圖從11:00開始打
"We told them they had 15 minutes, which meant we would wait for them for 30
minutes to set up and get ready, or they would lose the first map.
"Since they did not get ready, they got the message that they had lost the
first map against BX3 and that the second map would start at 11. So in the
end, we waited one hour for them to be ready.
"As stated in the rules, tiebreakers are solved as follows, using Na′Vi's
group as an example:
Tiebreaker 1: W-L-T in head to head (2 points for Na′Vi, Fnatic and Epsilon,
which means they are equal);
Tiebreaker 2: Point differential in head to head (They all have the same
differential, being 0);
Tiebreaker3: Point differential in all series (Na′Vi were the only team to
lose a map against BX3, which is why they placed third in the group).
其實Tiebreaker2這裡我不太懂 這個point看來應該是map point
反正rule裡面沒考慮到Round Difference
--
※ 發信站: 批踢踢實業坊(ptt.cc)
◆ From: 125.224.246.136
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 12:19)
推
03/30 12:27, , 1F
03/30 12:27, 1F
推
03/30 12:48, , 2F
03/30 12:48, 2F
SK NiP fnatic Mouz V.p 還有另外兩隊以前曾一起創立過G7
協會目的是團結起來追討賽事遲發的獎金XD
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 13:00)
→
03/30 13:11, , 3F
03/30 13:11, 3F
推
03/30 13:20, , 4F
03/30 13:20, 4F
推
03/30 14:35, , 5F
03/30 14:35, 5F
推
03/30 14:47, , 6F
03/30 14:47, 6F
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 17:09)
→
03/30 17:26, , 7F
03/30 17:26, 7F
→
03/30 17:56, , 8F
03/30 17:56, 8F
→
03/30 18:19, , 9F
03/30 18:19, 9F
推
03/30 18:24, , 10F
03/30 18:24, 10F
→
03/30 18:25, , 11F
03/30 18:25, 11F
推
03/30 18:50, , 12F
03/30 18:50, 12F
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 18:51)
推
03/30 18:52, , 13F
03/30 18:52, 13F
→
03/30 19:01, , 14F
03/30 19:01, 14F
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 19:05)
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 19:06)
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 19:08)
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 19:20)
→
03/30 21:20, , 15F
03/30 21:20, 15F
推
03/30 21:25, , 16F
03/30 21:25, 16F
→
03/30 21:26, , 17F
03/30 21:26, 17F
推
03/30 22:20, , 18F
03/30 22:20, 18F
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/30 23:12)
→
03/30 23:13, , 19F
03/30 23:13, 19F
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/31 00:01)
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/31 00:57)
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/31 01:02)
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/31 01:27)
→
03/31 02:04, , 20F
03/31 02:04, 20F
※ 編輯: AsakuRacing 來自: 125.224.246.136 (03/31 02:29)