Show the divine chest in battle reports

[FrutyX]

Show the "Chest of Divine Fate" in battle reports list, the same way as item drops are listed:

The best way (probably) to approach this would be, to save the report id (when it drops) and write it after in the reports list, so GCA doesn't have to check every single report, which would create server load.

The reason:

Sometimes, I forget if I farmed the chest that day, so I have to check every single report to see if I got it.

[GreatApo]

Not finished yet:

• There is a bug in cache (change page, go back, sometimes the reward is not shown)
• I need to double check if chests are given from both arenas (to reduce requests)

[FrutyX]

• I need to double check if chests are given from both arenas (to reduce requests)

It does drop in both arenas.

[FrutyX]

(to reduce requests)

Maybe you could flag only successful attacks, because the chest does not drop when you lose a fight.

[GreatApo]

Maybe you could flag only successful attacks, because the chest does not drop when you lose a fight.

Good idea

[SleepingShadow-bit]

Today i make a Video about the feature.
I had to load the page 2x to make it visible - is it correct?

Truhe.mp4

[FrutyX]

Indeed, noticed it too, but I was waiting for another shot to test it, it does not appear immediately, you have to revisit the reports page.

[GreatApo]

I have seen that too (I also reported that at the top) but I can't find why it happens... Maybe @GramThanos can do a quality check...

[GreatApo]

Found the problem, I messed the asynchronous requests...

[FrutyX]

We good on this feature, no problem found.

[SleepingShadow-bit]

We good on this feature, no problem found.

Yes. Same here. No Problems

[FrutyX]

@GreatApo for some reason, the problem is back, after you get your chest and check your reports, it is not visible, you have to refresh the reports page to see it.

Maybe someone else test this... I am using Google Chrome v97 (GCA v4.3.6).

Not confirmed.

[FrutyX]

Yep, so I am unable to confirm or deny it, I have probably seen once or twice a case, where it does not get loaded (only after a refresh), but now, a few days, it's been showing normally.