More detailed rollback desync screen. #3655
Unanswered
jade-midori
asked this question in
Feature Request
Replies: 1 comment
|
Sounds too technical for something that is displayed to the user. It's also not so easy to check the reason automatically. Maybe what we could do is separate the logging config so that desyncs can be logged on their own without the full lengthy log. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
When me and a few friends were trying to test our full game, we kept running into a desync issue several times in a row at the very start of round 2 in a singles match, however there would also be a random chance that this wouldn't happen, therefore our inability to report it. We never anticipated this happenning and sometimes this would ocurr late into our matches and we didn't anticipate having the log enabled as the filesize generated by it can become real big, particularily during lengthy sessions. Furthermore it can be frustrating as the random nature of it would cause the match to carry on without the issue occurring.
Describe the solution you'd like
I would suggest that the desync screen give at the very least an information as to what part of the gamestate was not able to be synced properly, allowing the issue to be recreatable or with an insight as to what went wrong, as the unexpected nature of these errors means we may not be prepared to log them, or worse, may happen to two people playing casually without a detailed report.
Additional context
No response
Search terms
rollback error screen
All reactions