Error in player game archive

Investigating this, sorry, we were on a company-wide meetup break so things slowed down but we're back now!

Thank you @Rida

Day 21. No change.

Day 23. No change. No response from support to any of the three bug reports. No follow up from the post by staff 4 days ago.

Day 25. No change.

Yes, Thank you

Day 26.

• Average Time to First Human Response: 1 day 14 hours

Day 28. No response.

Day 29.

Day 31

Hi there. To provide more context regarding this particular issue with this user's game archive (risinghelios-inactive) , we have identified this is an isolated case, and every other account closed for Cheating or Self-closed does not encounter this issue, so it probably is a fluke and will not be fixed just yet, sorry about that.

No it's not a fluke. When the name was changed the flag was changed manually and incorrectly. It was then changed again for another incorrrect one. It's poor management of the dataset.

Day 33

nevermind, only the top of the page displayed "finished". username by 'risinghelios-inactive' still shows "closed"

the js "short for JavaScript" might be written poorly, or either the node may be faulty. when the name was changed, the node might have seen flag changes incorrectly(after which, the node fowarded a POST request to the API). causing the API for incorrect status changes 2 times. then the account was rendered inactive by the backend. if i'm wrong here, please tell me.

Day 40. Still broken.

submit another bug report and wait until staff responds

was the last game you played was against "19twiggy90" where you won 2 games against him?

bruh bugas drive me crazy

btw im new

Day 43