Force client restarts MUST be reworked

Forced restart aren’t technically pushed to devices, but the client get that restart "flag" upon next sync. Normally the client should not sync and get the flag during a battle. You should only get that restart message when the game syncs up after a battle for example.

"LtGenStu;c-1570521" wrote:
Forced restart aren’t technically pushed to devices, but the client get that restart "flag" upon next sync. Normally the client should not sync and get the flag during a battle. You should only get that restart message when the game syncs up after a battle for example.

That crap happens when you load up this magical
new chat system. Notice the ironic tone when i say magical.

Hotfixes will never be timed perfect, but the team is working on a pop up message as a possible option long term.

Raids and events always going on with payouts globally on the hour , every hour so it can be frustrating.

Gonna have to side with the devs this time. Can't possibly account for every player when pushing restarts. At least it wasn't 5 minutes before payout...

"Vettes4Fetts2;c-1570535" wrote:
Gonna have to side with the devs this time. Can't possibly account for every player when pushing restarts. At least it wasn't 5 minutes before payout...

According to a post above:
Forced restart aren’t technically pushed to devices, but the client get that restart "flag" upon next sync. Normally the client should not sync and get the flag during a battle. You should only get that restart message when the game syncs up after a battle for example.

In my case, I was in the middle of a hRancor, and all I did was open the crap chat window. When I closed it, client restart!
In what twisted universe is that WAI?
It doesn't have to account for anything. It just has to work. It just has to be tested (which the chat clearly wasn't).

"BigSillyPanda;c-1570546" wrote:

"Vettes4Fetts2;c-1570535" wrote:
Gonna have to side with the devs this time. Can't possibly account for every player when pushing restarts. At least it wasn't 5 minutes before payout...

According to a post above:
Forced restart aren’t technically pushed to devices, but the client get that restart "flag" upon next sync. Normally the client should not sync and get the flag during a battle. You should only get that restart message when the game syncs up after a battle for example.

In my case, I was in the middle of a hRancor, and all I did was open the **** chat window. When I closed it, client restart!
In what twisted universe is that WAI?
It doesn't have to account for anything. It just has to work. It just has to be tested (which the chat clearly wasn't).

Exact same as me. That is also a new feature as it never done that before.

"BigSillyPanda;c-1570546" wrote:

"Vettes4Fetts2;c-1570535" wrote:
Gonna have to side with the devs this time. Can't possibly account for every player when pushing restarts. At least it wasn't 5 minutes before payout...

According to a post above:
Forced restart aren’t technically pushed to devices, but the client get that restart "flag" upon next sync. Normally the client should not sync and get the flag during a battle. You should only get that restart message when the game syncs up after a battle for example.

In my case, I was in the middle of a hRancor, and all I did was open the **** chat window. When I closed it, client restart!
In what twisted universe is that WAI?
It doesn't have to account for anything. It just has to work. It just has to be tested (which the chat clearly wasn't).

Opening chat syncs with the server, syncing with the server gets you the hotfix, hotfix requires a client restart. If you hadn't opened chat, you wouldn't have had the client restart "in the middle" of your rancor run.

"EyeG_80ate;c-1570550" wrote:

"BigSillyPanda;c-1570546" wrote:

"Vettes4Fetts2;c-1570535" wrote:
Gonna have to side with the devs this time. Can't possibly account for every player when pushing restarts. At least it wasn't 5 minutes before payout...

According to a post above:
Forced restart aren’t technically pushed to devices, but the client get that restart "flag" upon next sync. Normally the client should not sync and get the flag during a battle. You should only get that restart message when the game syncs up after a battle for example.

In my case, I was in the middle of a hRancor, and all I did was open the **** chat window. When I closed it, client restart!
In what twisted universe is that WAI?
It doesn't have to account for anything. It just has to work. It just has to be tested (which the chat clearly wasn't).

Opening chat syncs with the server, syncing with the server gets you the hotfix, hotfix requires a client restart. If you hadn't opened chat, you wouldn't have had the client restart "in the middle" of your rancor run.

But it makes NO sense to do that in the middle of a friggin' battle.
And the chat is used to... you know, _coordinate_ the raid? Guilds do that, so that everyone can participate...

"BigSillyPanda;c-1570551" wrote:

"EyeG_80ate;c-1570550" wrote:

"BigSillyPanda;c-1570546" wrote:

"Vettes4Fetts2;c-1570535" wrote:
Gonna have to side with the devs this time. Can't possibly account for every player when pushing restarts. At least it wasn't 5 minutes before payout...

According to a post above:
Forced restart aren’t technically pushed to devices, but the client get that restart "flag" upon next sync. Normally the client should not sync and get the flag during a battle. You should only get that restart message when the game syncs up after a battle for example.

In my case, I was in the middle of a hRancor, and all I did was open the **** chat window. When I closed it, client restart!
In what twisted universe is that WAI?
It doesn't have to account for anything. It just has to work. It just has to be tested (which the chat clearly wasn't).

Opening chat syncs with the server, syncing with the server gets you the hotfix, hotfix requires a client restart. If you hadn't opened chat, you wouldn't have had the client restart "in the middle" of your rancor run.

But it makes NO sense to do that in the middle of a friggin' battle.

I'm just telling you how it works, could they tell you were in a battle? Maybe, depends on how they have everything set up, but I doubt that info is sent with every request.

Once a server reboots (to update) no technology on mobile can reconnect 2 mis-matched versions. Thus why you get rebooted currently.

Be awesome if it could do that though