by outseekerdroid » Fri Apr 27, 2018 5:13 pm
Same codefail just happened again.
My game closed itself with no error, explanation or notification whatsoever - first fail.
I reopened the app and was trying to Reconnect within 5-10 seconds and it somehow never managed - second fail.
It said (extremely briefly) that the battle had failed due to timeout, while I was the one who started it and I was "in" the battle again (reconnecting). This should be impossible, please fix it.
Additionally this timeout and battle fail happened within 30 seconds of the battle starting... As someone who has had many players crash during RH and had them sometimes successfully reconnect, I have had to wait for countdown timers every attack until the battle was done over the course of several minutes... Why is it when the host crashes it always fails the battle within 30 seconds if they try to rejoin?
Even if everyone crashed and the RH was left in limbo, when someone tries to reconnect you should give them their RH. If this means creating a new RH instance, putting the rejoined player in with his teammates on Auto, why not do that? If people have crashed out and won't/can't rejoin, and you will not give their RH attempt back (as it is currently), give them something in their Inbox to compensate them.
This has been a very, very longstanding issue and has been reported by dozens and dozens of players in world chat, if not on this forum and via email. We need you to at least TRY something.. A useful debug log, compensation, smart RH migration code, ANYTHING.
On a less important note regarding how someone could see it as the wrong level, just open a RH lobby, have player 2 go to the RH listings and see the RH, have player 1 close the RH, change its level and reopen it, have player 2 join the still visible RH from earlier in the meantime.
Give us a code snippet so I can rewrite RH for you if need be, sheesh.