udonomefoo wrote: Cousin Simpson wrote: I just finished a clean round, where I closed the app each time I beat Galactus himself (and before going into the side nodes), though whether that's more RNG fickleness or not, who knows. I just came online to post the same thing. I thought I was really smart, but you beat me to it. At least we have one more instance of data so maybe it is more than just us getting lucky.
Cousin Simpson wrote: I just finished a clean round, where I closed the app each time I beat Galactus himself (and before going into the side nodes), though whether that's more RNG fickleness or not, who knows.
Moon Roach wrote: Just got this from CS: Greetings D3 Go! Customer, Thank you for contacting D3 Go! Customer Support. We do apologize for the inconvenience that this issue is causing for the Holiday Galactus run. Upon our review, it seems that the problem you are experiencing within the game is a known issue. The developers are working hard in order to resolve what is causing the problem. Due to this issue being wide spread, we are unable to offer compensation to players on an individual level. It would be unfair to credit one player without crediting all players affected by the issue. Therefore, if there is to be a compensation, it will be en mass, and it will be announced on the forums:http://d3go.com/forums/ We ask your patience as a decision is reached, and suggest that you keep an eye on the forums in order to receive the most current information regarding your issue. If you require further assistance, please do not hesitate to contact us again and it will be a pleasure to help you. Best Regards, D3 Go! Customer Support Team (TJM) I can almost forgive the use of "en mass" instead of "en masse".
Greetings D3 Go! Customer, Thank you for contacting D3 Go! Customer Support. We do apologize for the inconvenience that this issue is causing for the Holiday Galactus run. Upon our review, it seems that the problem you are experiencing within the game is a known issue. The developers are working hard in order to resolve what is causing the problem. Due to this issue being wide spread, we are unable to offer compensation to players on an individual level. It would be unfair to credit one player without crediting all players affected by the issue. Therefore, if there is to be a compensation, it will be en mass, and it will be announced on the forums:http://d3go.com/forums/ We ask your patience as a decision is reached, and suggest that you keep an eye on the forums in order to receive the most current information regarding your issue. If you require further assistance, please do not hesitate to contact us again and it will be a pleasure to help you. Best Regards, D3 Go! Customer Support Team (TJM)
snlf25 wrote: I got a reply back from customer service today. There wont be any compensation unless it's mass compensation. I hope we get something.
Cousin Simpson wrote: udonomefoo wrote: Cousin Simpson wrote: I just finished a clean round, where I closed the app each time I beat Galactus himself (and before going into the side nodes), though whether that's more RNG fickleness or not, who knows. I just came online to post the same thing. I thought I was really smart, but you beat me to it. At least we have one more instance of data so maybe it is more than just us getting lucky. I managed another full run without getting locked out. Three data points!
SnagglePuss wrote: As mentioned by others, restart the app after you hit boss Galactus. It forces a refresh to the server and had been working for our alliance since second refresh when we were told it's a communication issue. Refreshing after a node hit is too late and doesn't always work
Lystrata wrote: Cleared rounds 1 - 5 without a problem. Happened once in round 6, and now twice (so far) in round 7. Have also tried all the previous advice etc., but nothing works. Frustrating, but nice to know they're at least aware and it's not a blanket 'please check your device' response or similar.