Posted 17 August 2017 - 09:07 PM

So let me start off this post by saying that I understand the point of a timer that tracks how long you are not connected to a match that will prevent you from getting rewards for that match. The 2 minute timeout also makes sense in terms of a 15 minute standard QP game. However, it makes much less sense in the 30 min FW matches.Here's the situation -- I'm a linux player (through Wine) and sometimes, if I don't restart my computer between running other things through Wine and MWO i get crashes...that's fine, I'm aware of that being part of the price I pay for playing through Linux. The problem is what happened tonight, please see this imgur gallery as evidence https://imgur.com/gallery/tbPbu I don't have screen shots from the match before, but I did about 2600 damage and made about 1.5-1.6 mill CBIlls for that match. In each of the next 2 games (the ones in the imgur gallery), I crashed twice. It is not possible to crash twice and reconnect into a FP game within a total of 2 minutes. It is barely possible to crash once and load into a FP game within 2 minutes (it takes me about 1 min 46 seconds).Now if I had done sub 1k dmg and had 10 assists on a 48 kill team, I could accept not getting a cbill reward for winning the match. Notice, I did get cbills for damage, kills, KMDD, etc but not for the win. Same goes for XP -- it didn't get double as a first win of the day bonus should (I switched drop decs each match except HBR prime in game 1 that I had in the previous matches). Also notice that I'm the 4th highest dmg on my team and 3rd highest dmg on my team in games 1 and 2 respectively. The number of kills + assists I achieved in each match was comfortably not an outlier on my team. I'm also the 5th highest dmg in the match for both matches.Sure, the fact that I was disconnected for ~4 minutes means I got to shoot less, I shared less armor, and I was less helpful than I could've been. But to say that being one of the top performers in a match is irrelevant when compared with the 4 minutes I missed in each is misguided.I have 2 suggestions: 1) extend the time out on FW matches to 3 minutes or 3:30. I can see not strictly doubling it for matches that are possibly twice as long (15m vs 30m), but using the same timeout doesn't make sense. The ratio of the amount of the match you can be disconnected for should be similar. 2) make an exception for cases where players still finish in the top 25% of match performers but are disconnected between that limit (2/3.5 mins) and an upper bound (5/9 mins? don't have a good hold on what this should be, but it SHOULD exist).This way you aren't unfairly punishing players whose hardware and operating systems may not agree with the game 100% of the time but who still contribute meaningfully to their team in a match. Especially a win.