[翻譯] 斷線選手談賽後感
看板Hearthstone作者rextremistz (Rextremistz)時間6年前 (2017/09/21 12:47)推噓27(33推 6噓 53→)留言92則, 39人參與討論串1/2 (看更多)
前兩天 HCT 接連傳出選手斷線導致輸掉比賽的情形發生。
按照比賽規定，只要斷線就是得 Rematch，受害的兩名選手將自己心情寫在 Reddit 上，
訴說自己的無奈和對於系統機制無法回溯的缺陷感到可惜。
許多網友都為選手打抱不平，甚至嘲諷以後只要快輸了就斷線就好。
而沒有競技機制的確是爐石一直以來在電競上的一大缺失，
且被認為這並不是一個難以解決的問題，
尤其爐石不像 LoL 或 OW 這般有著相較複雜的比賽過程。
--
選手1: Lurker - My thoughts on my top 8 playoffs D/C
影片支援斷線時間點: https://youtu.be/DZV-ShAGAsM?t=39m40s
From Reddit
https://goo.gl/KasEVt
Hey guys! I wanted to post this here just to address everything,
and tell everyone how I feel in more depth than my tweet.
Just a quick heads up,
I'm writing this while in a car on my way home from playoffs,
so please forgive the formatting!
As many of you may know,
I recently finished top 8 of the Americas summer playoffs,
after a heart breaking series to Nalguidan.
During the series, at 1-2,
I was massively ahead as warlock vs pirate warrior.
While the game was going on (at a near impossible place to lose),
the laptop blizzard provided froze.
As per the rules, a regame was called and I lost.
Assuming I won this game;
my priest was slightly favored vs pirate warrior,
and I could complete the reverse sweep.
Now the boring recap is done,
here are my feelings on the matter.
I'm not upset with anyone regarding this situation; not my opponent,
Blizzard or the tournament organizers.
This was something entirely unexpected,
and there's no way to call the game as a win for me,
thus leading to the depressing regame (and my wonderful defile play!).
I also noticed a lot of people called me immature due to my over-expression.
While I realize some of these are trolls,
I want to make it aware that aside from the stream watching me,
I was entirely alone during these games.
The start of the series was extremely stressful,
but after the disconnect,
I lost all focus and let my emotions get the best of me.
Most players are emotional, but a lot won't show it on their stream,
and will let it build up; and that really can't be healthy.
I figured I would 100% be myself on stream and not hold back at all.
I think the HCT circuit could use changing but everyone is aware of that.
We need a tournament mode, we need a better format,
(one where tie breakers aren't considered or weighed as heavily),
and we need better venues/equipment.
There's a lot we need,
but I'm certain Blizzard is fully aware of this so I'm not worried.
At the end of the day,
I still have much to improve on and hopefully can get back here next year.
I'm extremely grateful for all the support I've recieved,
and I truly can not thank everyone enough.
I'll try to answer all messages, so if you have a question just ask!
Ggs to Nalguidan and I hope you do well at championships! :)
Edit: Forgot a Tl;Dr.
Tl;dr: DC was unfortunate, wish it didnt happen.
I'm not upset with anyone and you shouldn't be either.
I strongly believe we will get the fixes we need in 2018.
大家好，我想在這談一些比我在推特上更深的感受。
由於我正在從季後賽回家的車上，麻煩原諒我的排版!
你們許多人也許知道，我這兩天在輸給 Nalguidan 之後，
結束了一個痛徹心扉的美國夏季季後賽8強賽事。
在系列賽中(搶3)，我1比2落後對手，
但在下一場玩術士對上海盜戰中取得了絕對優勢，
那是一個幾乎不可能會輸掉遊戲的局面。
然而這時暴雪提供的筆電當機了，根據規則必須重賽，而重賽結果是我輸了。
假設我贏下了這場比賽，而我接下來的牧師牌組對上海盜戰又有著些微的上風，
我本來是可能讓2追3逆轉的。
結束了無聊的前情回顧，以下是我對於這事情的看法。
我沒有對任何人感到不高興，無論對手、暴雪、或安排賽事的人。
這是一個完全無法預測的事情，不可能反過來判還我一個勝利，
也因此導致接下來令人沮喪的重賽(還有我「美好」的褻瀆play!)
我還注意到了很多人說我不成熟，過於情緒化。
儘管這些人很多只是在戳，
我還是要聲明比賽中除了實況看著我的人以外，當下我是完全一個人的。
系列賽開始的時候充滿了壓力，
但在斷線之後我失去了專注，並且讓心情徹底影響了我。
很多選手儘管情緒化，但不會在實況中表露，這是不健康的壓抑。
我想要在實況中完全做我自己，沒有任何保留。
我認為 HCT 有許多可以改進的地方，但這人人都嘛曉得。
我們需要一個競技模式，更好的賽制(延長加賽的決定性減輕)，
還有更好的會場、設備。
有許多可以改進之處，而我確信暴雪也有充分意識到，所以我不擔心。
到頭來，我也有許多要加強的，並希望明年能再回來。
我非常感激大家給予的支持，真的衷心謝謝大家。
我會試著回答所有訊息，所以如果你有問題儘管問!
Nalguidan 你打得很好，並希望你在冠軍賽也能有亮眼的表現!
Tl;Dr(Too long, didn't read. 類似給 end 的人看):
斷線很不幸，希望它沒發生。
我沒有對任何人感到不高興，你也不需要。
我確信我們會在2018年看到我們需要的改進。
--
選手2: Rpbalance - This HCT is not that I want
From Reddit
https://goo.gl/LDsVts
Dear Blizzard, I am a non-famous Hearthstone player.
Fortunately I won the preliminary to HCT America summer playoffs.
However, my first HCT trip was not fortunate.
I had to wait for 45 minutes since 1st round started,
because my opponent's venue had bad internet connection.
When I saw him jump offline and jump online over and over again,
I felt terrible.
I said that I do not want to have a Disconnect-rematch.
The match started, we had a 2-2 score,
and the last game was evolve shaman VS highlander priest.
This is not a good match-up for me,
but I had an excellent beginning and,
my opponent's priest played too aggressive,
and spent too much resources.
In turn 4, I had both hand and board advantage and I am sure I will win.
Suddenly, the innkeeper said "YOUR OPPONENT LEFT" with a boom.
I think I should win 3-2.
However, the rule said "ALL NON-LETHAL DC GAMES NEEDS REMATCH".
So we rematched, I lost, and lost the first round.
Then I tried hard but still lost second round,
and 0-2 Swiss score broke my Esport dream.
This kind of things happened many times before,
and many HS players suffered from the disconnect issues and rules.
The rule has several problems.
First, it protect the one who disconnect,
but ruin the right of advantage keeper of the origin game,
and it leads to their suspension of the disconnected people.
It is not easy to distinguish the "nature" disconnection
and man-made disconnection.
When the network was unstable,
even a little vibration can cause disconnection.
(I even suspect they let my opponent play on his phone and use mobile data.)
Furthermore it cause more suspension on who are innocent to be disconnected.
Second, the cut line of lethal is unclear and unfair.
It's unclear because some complex situation,
the lethal is hard to figure out in 75 seconds,
and sometimes secrets influence their mind.
For example, your opponent had a random secret,
you may choose another plan other than lethal,
to get rid of the risk of ice block or ice barrier.
Problems regarding fair is even worse.
Lethal is far more likely to reach for aggro decks than control.
For example, you play taunt warrior VS pirate warrior,
and you successfully exhaust all your opponent hand cards
with tons of taunt minions, and your health is absolutely safe.
Suddenly, your opponent DC and you are normally not lethal,
but how could you lose?
Third, this rule punished people who use the bottom "concede".
When you have advantage, you have to play fast to avoid DC-rematch.
When you are in bad position, you tend to play slow even rope,
and try to survive to hope the probability of DC-rematch.
It encourages playing tricks and hence it ruin the esport spirit.
Fourth, even fair, nature and innocent DC-rematch
is not good for HS esport development.
Since HS is about to ultimate your resource to beat down your opponent,
it should not include the percentage of non-cardgame.
Because everyone are "50-50" hurt by the DC-rematch,
it punishes the more skillful players and lower their win rate.
Last, loss due to DC-rematch is a terrible strike for players' mind.
Do you still remember Yoggsaron, the only card nerfed twice in HS?
Being set-back by DC-rematch was even more upset thing than by Yoggsaron.
I can still accept loss due to luck,
but cannot accept loss due to DC-rematch (it is not a part of HS.)
I also think about how to solve the DC problem more reasonably.
The best way is to set up a match mode,
which could have functions like banpick.
If it can record your game and continue the game at a specific turn,
(screenshot), the problem will be perfectly solved.
More easier approch is to add an official assistance software,
can record the card flows (similar to HDT),
and we can somehow load the game record in the main game.
The easiest way is examining the internet before the whole series,
or you can just prepare backup device in different Wi-Fi,
if it already so unstable.
When it shows DC turn to the backup as soon as possible.
The rematch method is the worst.
English is my second language so I may use wrong words or grammar,
thank you for reading until here.
I am just first time to HCT and I write the passage not for myself,
but for HS esports.
HS runs 4 years and becomes popular,
lots of new functions are invited and old problems are solved.
I hope that the DC problem can be solved,
and HS will become better and better in the future.
Rpbalance
P.S. I think "who DC who loses" sound harsh but may be better,
because not only it is more fair,
but also it encourage people choose more stable（wired）internet,
and force the host provide stable internet atmosphere.
(i mean for offline competitions)
親愛的暴雪，我是一個不有名的爐石玩家。
慶幸的是我贏了美國 HCT 的預賽，然而我第一次的 HCT 卻是不幸的。
我必須等45分鐘第一輪才開始，因為我對手網路很爛。
當我看到他不斷下線又上線，我感到很糟，我不想要斷線重賽。
比賽開始了，我們2比2戰成平手，而最後一場是進化薩對卡札牧。
這對我不是一個有利的對戰，但我有了很棒的起手，
且對手玩得過於侵略而花了過多的資源。
第四回合，我同時有場優和手牌優勢，我確定要贏了。
突然，旅店老闆boom的一聲說「你的對手離開了」。
我認為我可以3比2拿下勝利，
然而規則是「所有非即死擊殺而斷線的遊戲都需要重賽」。
我們重賽而我輸了，同時也輸了第一輪。
儘管之後我很努力，依舊是輸了第二輪，對上瑞士0比2摧毀了我的電競夢。
類似的事情發生很多次了，很多爐石玩家都深受其害。
規則本身就存在一些問題。
一，它保護了斷線的玩家，但也壞了上風玩家的優勢，
這也談及了對於斷線玩家的懲罰。
要判斷斷線是自然還是人為是一件很困難的事。
如果網路很不穩，一點震動都會造成斷線(我甚至懷疑我的對手用的是手機網路)，
而有些人的斷線是無辜的卻被懲罰。
二，即死擊殺的判斷很模糊也很不公平。
之所以模糊是因為有些複雜的情況很難在75秒之內看出來，
且秘密有時也會有所影響。
譬如對手有隨機秘密，你會有別的計畫來避免寒冰屏障或寒冰護體帶來的風險。
不公平的情況更是糟糕。即死往往適用於快攻牌組而非控制牌組，
譬如嘲諷戰對海盜戰，
你成功地用一堆嘲諷怪消耗了對手的手牌，且你的血量完全安全。
突然你斷線了，而對手並沒有在即死擊殺的範圍內，但你怎麼可能會輸呢?
三、這規則會懲罰那些投降的人。當你有優勢，你要盡快出牌避免斷線。
而當你弱勢的時候，你要盡可能存活拖時間甚至燒繩，看有沒有機會來個斷線重賽。
這會讓人投機取巧，壞了電競精神。
四、儘管再自然公平沒有爭議性的重賽，對於競技爐石的發展也是不好的。
既然爐石是個盡可能用最少資源換取最大利益的遊戲，它就不該包含遊戲外的變數。
因為每個人都是同等受害於斷線，這會讓實力比較強的一方失利。
最後，因斷線而輸掉比賽對於選手是很沉痛的打擊。
還記得尤格薩倫? (10費 7/5，隨機施放法術)，爐石唯一一張被NERF兩次的卡片?
被斷線比被尤格薩倫放倒還惱人。
我能接受運氣不好敗北但不能接受因為斷線輸掉遊戲，那根本不屬於爐石一部分。
我也有想如何解決斷線的問題。
最好的方法是有個競技模式，讓你可以 BanPick、記錄遊戲、在特定回合重回遊戲，
問題就完美解決了。
簡單一點的話是用類似 HearthstoneDeck 輔助應用程式記錄牌流，
讓我們可以依牌流回溯遊戲。
最簡單的方法是比賽前測試會場的網路，提供不同的備用 Wifi，
如果本身網路就已經很差的話。
至少斷線的時候可以盡快連回來。
重賽是最糟糕的選擇。
英文是我的第二語言，所以我可能有用錯字或文法，謝謝你讀到這邊。
我第一次參加爐石比賽，而我寫這些的目的不是為了我而是爐石的電競發展。
爐石已經四年了，且變得越來越熱門。其中新增了許多新功能也解決了很多過去的問題。
我希望斷線的問題能被解決，爐石也能在未來變得越來越好。
Rpbalance
P.S. 我認為「誰斷線誰就輸」雖然聽起來很刺耳，但至少比較公平，
且它會促使玩家和主辦單位使用更好的網路。
--
兩位選手都挺有風度，
真誠地提出自己看法，希望能增加一個競技模式，
大家也相信暴雪會讓遊戲越來越好。
--
本人喜好翻譯有趣的各領域影片跟文章，
若有人感興趣之內容想要翻譯，不吝站內信。
--
※ 發信站: 批踢踢實業坊(ptt.cc), 來自: 36.231.105.72
※ 文章網址: https://www.ptt.cc/bbs/Hearthstone/M.1505969225.A.30D.html
推
09/21 12:51, , 1F
09/21 12:51, 1F
→
09/21 12:51, , 2F
09/21 12:51, 2F
推
09/21 12:52, , 3F
09/21 12:52, 3F
→
09/21 12:53, , 4F
09/21 12:53, 4F
推
09/21 12:53, , 5F
09/21 12:53, 5F
推
09/21 12:54, , 6F
09/21 12:54, 6F
→
09/21 12:54, , 7F
09/21 12:54, 7F
推
09/21 12:55, , 8F
09/21 12:55, 8F
→
09/21 12:56, , 9F
09/21 12:56, 9F
推
09/21 12:57, , 10F
09/21 12:57, 10F
推
09/21 12:58, , 11F
09/21 12:58, 11F
→
09/21 12:58, , 12F
09/21 12:58, 12F
推
09/21 12:59, , 13F
09/21 12:59, 13F
→
09/21 12:59, , 14F
09/21 12:59, 14F
噓
09/21 13:00, , 15F
09/21 13:00, 15F
→
09/21 13:00, , 16F
09/21 13:00, 16F
→
09/21 13:00, , 17F
09/21 13:00, 17F
推
09/21 13:00, , 18F
09/21 13:00, 18F
→
09/21 13:00, , 19F
09/21 13:00, 19F
推
09/21 13:01, , 20F
09/21 13:01, 20F
→
09/21 13:01, , 21F
09/21 13:01, 21F
推
09/21 13:02, , 22F
09/21 13:02, 22F
推
09/21 13:02, , 23F
09/21 13:02, 23F
→
09/21 13:03, , 24F
09/21 13:03, 24F
→
09/21 13:07, , 25F
09/21 13:07, 25F
推
09/21 13:07, , 26F
09/21 13:07, 26F
推
09/21 13:08, , 27F
09/21 13:08, 27F
→
09/21 13:16, , 28F
09/21 13:16, 28F
→
09/21 13:16, , 29F
09/21 13:16, 29F
→
09/21 13:16, , 30F
09/21 13:16, 30F
推
09/21 13:26, , 31F
09/21 13:26, 31F
推
09/21 13:27, , 32F
09/21 13:27, 32F
→
09/21 13:27, , 33F
09/21 13:27, 33F
推
09/21 13:28, , 34F
09/21 13:28, 34F
推
09/21 13:28, , 35F
09/21 13:28, 35F
→
09/21 13:29, , 36F
09/21 13:29, 36F
→
09/21 13:29, , 37F
09/21 13:29, 37F
→
09/21 13:32, , 38F
09/21 13:32, 38F
→
09/21 13:33, , 39F
09/21 13:33, 39F
→
09/21 13:33, , 40F
09/21 13:33, 40F
推
09/21 13:33, , 41F
09/21 13:33, 41F
→
09/21 13:33, , 42F
09/21 13:33, 42F
推
09/21 13:38, , 43F
09/21 13:38, 43F
→
09/21 13:38, , 44F
09/21 13:38, 44F
→
09/21 13:38, , 45F
09/21 13:38, 45F
推
09/21 13:41, , 46F
09/21 13:41, 46F
→
09/21 13:41, , 47F
09/21 13:41, 47F
推
09/21 13:42, , 48F
09/21 13:42, 48F
→
09/21 13:43, , 49F
09/21 13:43, 49F
→
09/21 13:44, , 50F
09/21 13:44, 50F
噓
09/21 13:49, , 51F
09/21 13:49, 51F
→
09/21 13:49, , 52F
09/21 13:49, 52F
推
09/21 14:03, , 53F
09/21 14:03, 53F
推
09/21 14:08, , 54F
09/21 14:08, 54F
推
09/21 14:09, , 55F
09/21 14:09, 55F
推
09/21 14:11, , 56F
09/21 14:11, 56F
噓
09/21 14:29, , 57F
09/21 14:29, 57F
→
09/21 14:30, , 58F
09/21 14:30, 58F
→
09/21 14:31, , 59F
09/21 14:31, 59F
噓
09/21 14:33, , 60F
09/21 14:33, 60F
→
09/21 14:33, , 61F
09/21 14:33, 61F
推
09/21 14:35, , 62F
09/21 14:35, 62F
→
09/21 14:36, , 63F
09/21 14:36, 63F
→
09/21 14:37, , 64F
09/21 14:37, 64F
→
09/21 14:37, , 65F
09/21 14:37, 65F
→
09/21 14:37, , 66F
09/21 14:37, 66F
→
09/21 14:38, , 67F
09/21 14:38, 67F
→
09/21 14:38, , 68F
09/21 14:38, 68F
→
09/21 14:39, , 69F
09/21 14:39, 69F
→
09/21 14:40, , 70F
09/21 14:40, 70F
→
09/21 14:40, , 71F
09/21 14:40, 71F
→
09/21 14:41, , 72F
09/21 14:41, 72F
→
09/21 14:41, , 73F
09/21 14:41, 73F
→
09/21 14:50, , 74F
09/21 14:50, 74F
→
09/21 14:54, , 75F
09/21 14:54, 75F
→
09/21 14:55, , 76F
09/21 14:55, 76F
→
09/21 14:56, , 77F
09/21 14:56, 77F
推
09/21 14:56, , 78F
09/21 14:56, 78F
→
09/21 14:56, , 79F
09/21 14:56, 79F
推
09/21 15:22, , 80F
09/21 15:22, 80F
噓
09/21 17:04, , 81F
09/21 17:04, 81F
→
09/21 17:40, , 82F
09/21 17:40, 82F
→
09/21 17:40, , 83F
09/21 17:40, 83F
→
09/21 17:41, , 84F
09/21 17:41, 84F
→
09/21 17:46, , 85F
09/21 17:46, 85F
噓
09/21 18:33, , 86F
09/21 18:33, 86F
推
09/21 18:35, , 87F
09/21 18:35, 87F
→
09/21 18:41, , 88F
09/21 18:41, 88F
推
09/21 20:34, , 89F
09/21 20:34, 89F
推
09/21 21:50, , 90F
09/21 21:50, 90F
推
09/21 23:30, , 91F
09/21 23:30, 91F
→
09/21 23:32, , 92F
09/21 23:32, 92F
討論串 (同標題文章)