SilentBlade01
New member
I'm curious if there's a way for deadlock to implement a way to detect authentic crashes.
I loaded the game and went to start queuing for a match, then crashed.
- okay weird I thought.
I re-opened the game after restarting steam and queued up for a match and then crashed again.
It was only then that I realized that it was compiling shaders after a delay from starting the game (or at least feedback in the bottom right corner wasn't there at the beginning of the game's launch).
I then got banned for 4 hours for crashing during the search for a match (not even in the middle of a match or at the beginning, but during a search.
I don't know if this is expected behavior or not, but I would argue that you shouldn't be given a 4 hour penalty when crashing during queue.
I loaded the game and went to start queuing for a match, then crashed.
- okay weird I thought.
I re-opened the game after restarting steam and queued up for a match and then crashed again.
It was only then that I realized that it was compiling shaders after a delay from starting the game (or at least feedback in the bottom right corner wasn't there at the beginning of the game's launch).
I then got banned for 4 hours for crashing during the search for a match (not even in the middle of a match or at the beginning, but during a search.
I don't know if this is expected behavior or not, but I would argue that you shouldn't be given a 4 hour penalty when crashing during queue.