mysteryamazon06
New member
so, long story short, tonight I was playing some matches, when the game said to close and update the client real quick, so I did, rebooted the game, when after queuing and joining into a new game the game crashed telling me some random file was corrupt & to revalidate my game files, so I tried to relaunch the game and steam said it was downloading at 0% but there was nothing on the actual downloads page so I tried revalidating and it was just stuck at 0%, so I did a full uninstall and reinstalled on a different drive, booted it up, it said I abandoned the match of course, so I queue up, join a game and...bam! same thing happens...! so my dumb a** tries the same steps as before, same outcome, says downloading 0%, not on steam downloads, try to verify, 0%, reinstall on another drive, boot it up, it says I'm NOT being penalized for the last match which seems to be a blatant lie, I join a game, boom, crash into some random file is corrupt, try revalidating, 0%, 0% etc.
so at this point I said screw it, I'll come back later, and I came back later, steam auto validated the game files, I booted it up...and I'm apparently banned for 24 hours and I have 2 wins needed now in the low priority matchmaking queue? I'm not gonna lie I did have one DC earlier this week because f****in' comcast is a terrible ISP and dropped my internet for an hour and a half for no reason, like, if that had happened multiple times I wouldn't have made this post, because I understand at the end of the day that's on my end, it's my fault I live in a comcast ISP fiefdom. now, look, I'm no programmer or developer, but when other games/software I play/use on my pc occasionally crash, a majority of them seem to be able to detect that the game was closed as the result of a crash, and not, say, alt-f4, and will open a bug reporting window, is it not possible for you all to implement something similar for this game, so when I download a quick new game client update between rounds and hop back in and suddenly the game crashes telling me some random file is corrupt which seems to even leave steam itself at a loss as to what to even do about it, that maybe, this game could detect that, and not penalize me with a 24 hour ban for what quite obviously appears to be a small bug of some sort that's likely been resolved already?
Now, also, I realize this game is in beta, and sometimes s*** happens; and it looks like from this forum section, I'm not the only one having issues with getting banned because of these presumed beta growing pains; since this is clearly the case, perhaps it is prudent to tone down this unnecessarily strict dc ban system a considerable amount until these issues become less frequent? I understand that there has to be some negative reinforcement to prevent rage quitting, but since you clearly already implemented a 'ragequitter queue', why not just let all the people in that queue match with each other for a few games instead of the rigid timeout ban system at least while it's still in beta and you guys are still actively tweaking the back end of the netcode and whatnot? there's no reason the dc punishment needs to be/should be this harsh at the moment, honestly.
so at this point I said screw it, I'll come back later, and I came back later, steam auto validated the game files, I booted it up...and I'm apparently banned for 24 hours and I have 2 wins needed now in the low priority matchmaking queue? I'm not gonna lie I did have one DC earlier this week because f****in' comcast is a terrible ISP and dropped my internet for an hour and a half for no reason, like, if that had happened multiple times I wouldn't have made this post, because I understand at the end of the day that's on my end, it's my fault I live in a comcast ISP fiefdom. now, look, I'm no programmer or developer, but when other games/software I play/use on my pc occasionally crash, a majority of them seem to be able to detect that the game was closed as the result of a crash, and not, say, alt-f4, and will open a bug reporting window, is it not possible for you all to implement something similar for this game, so when I download a quick new game client update between rounds and hop back in and suddenly the game crashes telling me some random file is corrupt which seems to even leave steam itself at a loss as to what to even do about it, that maybe, this game could detect that, and not penalize me with a 24 hour ban for what quite obviously appears to be a small bug of some sort that's likely been resolved already?
Now, also, I realize this game is in beta, and sometimes s*** happens; and it looks like from this forum section, I'm not the only one having issues with getting banned because of these presumed beta growing pains; since this is clearly the case, perhaps it is prudent to tone down this unnecessarily strict dc ban system a considerable amount until these issues become less frequent? I understand that there has to be some negative reinforcement to prevent rage quitting, but since you clearly already implemented a 'ragequitter queue', why not just let all the people in that queue match with each other for a few games instead of the rigid timeout ban system at least while it's still in beta and you guys are still actively tweaking the back end of the netcode and whatnot? there's no reason the dc punishment needs to be/should be this harsh at the moment, honestly.
