Всі Категорії

Not getting CB chests

Not getting CB chests

Пошук
1 жовт. 2022, 23:1401.10.22
10.08.21
1

Not getting CB chests

Title:  Not receiving clan boss chests

Device: Custom-built PC

OS: Windows 10 Pro (21H2), Build: 19044.2006

WTR: Unknown how exactly to trigger the bug

Description:

The last 2 days, I did not get any clan boss chests (rewards) despite doing > 40 million damage to the nightmare clan boss. I did not do enough damage to other level of CB to know if it's specific to nightmare CB or not.

Yesterday, I did ~50m damage to NM CB + ~12m on UNM CB (not enough to qualify for UNM chest)

Day before, I did ~40m damage to NM CB. Did not do any other level of CB.

Prior to that, I never had an issue getting CB chests. The first time it happened I thought it might have been a glitch because I finished with a little less than 1 minute left before CB resets. But 2nd day I finished well before reset.


Перегляди
5
Коментарі
3
Коментарі
dthorne04Moderator
2 жовт. 2022, 05:2702.10.22
30.12.20
6231

As far as I've understood, this is a visual glitch that should be cleared up by restarting your game. 

If that doesn't work, can you try another device, if possible?

If that doesn't work, please open a support ticket. Sorry about the inconvenience. 

2 жовт. 2022, 11:3102.10.22
2 жовт. 2022, 11:31(відредаговано)
10.08.21
1

I got chests today. 

Unfortunately, I wasn't able to verify if it was just a visual glitch as my PC froze while I was sleeping and I had to reboot it and re-run the game.  So, I didn't get a chance to see if I would have gotten the chests without restarting the game or not. Stands to reason though that restarting the game solved the issue though.

Thanks!

dthorne04Moderator
3 жовт. 2022, 07:3303.10.22
30.12.20
6231
deeveon

I got chests today. 

Unfortunately, I wasn't able to verify if it was just a visual glitch as my PC froze while I was sleeping and I had to reboot it and re-run the game.  So, I didn't get a chance to see if I would have gotten the chests without restarting the game or not. Stands to reason though that restarting the game solved the issue though.

Thanks!

Sorry for the troubles, glad to hear it sorted itself out however. :)