JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Syntactycal: 8/15/2023 12:26:50 AM
2

Matchmaking failed via cabbage kicked to orbit 30 minute comp ban. Thanks.

I have hundreds of completed comp matches with maybe one left-early match in the past several months. You just error code me while a trials match is loading, twice in a row, then ban me for 30 minutes. Thanks. Can you not detect that the match never actually started, you know, before issuing penalties for this kind of stuff? While you're at it, in comp, if you start a match lopsided, why can you not just requeue the match instead of putting me in a 2v3, then docking me 183pts when I inevitably loose? Like, your algorithm really thinks I should have won that match huh? The two aforementioned issues are not hard to implement, don't tell me it isn't. Not putting in checks for this stuff is lazy or indifference to the problem. On the same front. Tower loading. Like seriously? Your game paid any attention it would know that it normally takes me like 5 whole seconds to find and load a tower instance. So you would think there could be a check that would notice I've been "loading" a tower instance for 5X the time it normally takes me because the host you chose for me is obviously some potato so why can you not just drop from that queue and find me a different host instead of just wasting my time in an infinite load screen? This is not rocket science. I'm not a game dev but I am a dev. I know this could all be done and probably without a whole lot of effort.
English
#Help #problems

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon