{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/15/2021 11:38:24 AM
7
In most cases on pc it’s due to programs running while playing that aren’t considered allowed
English
-
I realise that, I was a forgot to check all other programs (in this case, a trainer for another (solo) game.) were closed before booting destiny. I was honest and open about it in the automated form to them. The thing that's really playing with my nerves is the 'not knowing' y'know?
-
Most trainers are still editing memory even when closed and without a cache clear “which windows doesn’t do on its own” or a physical pc reset these stay active without the users knowledge. I have something that clears cache but I’ve always reset my pc everytime before I join destiny when doing other modded games.
-
My main hope is they're just super busy atm, and have yet to properly go over my form. Also hoping my honest admittance of my fault will stand me in good stead. the nerves(tm) are running high.
-
I honestly wouldn’t get your hopes up unfortunately. I’ve only seen 8 people unbanned since vanilla D2. All of those were discord mistakes and networking issues that were resolved with a shitload of proof
-
That's disappointing, but I guess I shouldn't be surprised. It's kinda bizarre that they use forums instead of some kind of support ticket system though.
-
Your case id is your ticket. The forums is just a way to ask. But as per bungies own policy they don’t have to tell you what caused your ban. 99% of the time it’s a 3rd party program that’s unauthorized or exploiting within game
-
I normally do the same. Just this time I was frazzled due to exterior factors and forgot. Kicking myself.
