{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
6/1/2020 3:47:08 PM
5
6 years of disconnections
Ok now i'm really pissed the -blam!- of. It's been 6 years already this poorly managed game made me crash with stupid ass name errors in the most crucial moments during my destiny 1/ 2 overall experience . And now with the conqueror sigil i'm literally done. It's been already 4 times that my godlike rng makes me get kicked out the 1050 nightfalls during boss phase or close to it. There wouldn't be much of a problem if JOINING ALLIES AFTER YOU LITERALLY JUST GOT KICKED FROM THAT ACTIVITY was turned on but guess what ahahah you -blam!-ing can't. I mean is that hard for real to implement such a straight forward concept of: if i'm the one getting -blam!-ing kicked out then i should be able to join my allies back since i started the nightfall myself. But no , -blam!- that , such quality of life features are not what bungie is interested of , better -blam!-ing fix the wrong seasonal logo on some dumb sparrow instead , yeah that's right this is what any people who got bonded with destiny is getting, a kick in the ass for all the hard work you put in to stuff and that's it. Even funnier they keep stating that " they are listening to our feedback " , yes , yes they are.. except then they don't do shit about it. Lemme be clear, this is a rant post i dont give a -blam!- about ur stupid help guidelines on how to fix disconnections , IN 6 YEARS NOTHING WORKED OUT , 6 YEARS don't give me that shit anymore.
-
It's you.
-
Definitely on your end. I can count on one hand the number of times I've been booted since the D1 launch.
-
4 RepliesSorry dude but this is definitely on your end. I maybe get a code every now and again, so little that I don't know what the time length would be for how often. For six years you have probably needed a, wired connection, new router, faster dedicated isp, not shared network with many devices, prioritize the console (if console) in your network, update your drivers for network card, get a new network card (giga), so many other reasons. Just a few potential things you could have done to optimize for Destiny's multiplayer needs. Also the people that have your experience are such a small minority. If this happened to the majority there would be no players playing at all. Sorry for your stress.
-
Try #feedbackd2 since you aren't actually looking for any assistance.
-
2 RepliesI have to agree with Dex & Hokies. If you’ve had problems for the better part of 6 years, then it’s definitely on your end. Maybe you should spend more time trying to diagnose your connection problems instead of ranting in a forum meant for people to seek help.
