Like any other weekend I wanted to play some ToO, hopped in as usual with 2 mates ready to go.
The first game was the only 3v3 match played, people were getting disconnected like crazy, we played 3v1's, 3v2's, 2v2's and even 3v0, I got to 8-0 on my trials passage then it decided it was my turn to be kicked (quail error) and left my teammates in a 2v2, luckily they managed to win for their flawless, of course my passage was 8-1 now and wasted thank you bungie.
An extreme amount of people were getting kicked from trials games, you cannot blame my internet, your error code pages are useless regarding this issue, trials was a fun experience in yr1 and 2 but this is far from that, it's virtually unplayable! No one wants to try and go 9-0 if you know you could get randomly booted for no reason any moment.
Raid - perfect connection, Patrol - perfect connection, Crucible, Strikes, Iron Banner, all perfect connection, why just the important 3v3? Makes no sense, any insight would be good.
-
This is the thing that annoys me most about bungie, their error codes never mean anything, I get kicked from trials for the quail error...quail is an error given when kicked from a private match...? People get kicked in the same instance and get completely different error codes! It's a very poor system of telling people what the problem is and it seems like they always try to blame the players internet connection!
-
You won';t find any real "help" from Bungo. All you will get is a link to their networking page. Bunch of clowns can't get anything right.
-
Edited by FLICK: 10/16/2016 9:14:38 PMHaving the same problems and quite frankly I'm sick and tired of it! What's makes things worse is the difficulty of getting trials coins!! Out of the last five cards I've ran I've gone at 8-0 and already used my mercy, then I get booted and raging commences. Please fix this problem your community is reaching out with real concerns!!
-
Yea Today we got auto coconut error on orbit right after the matchmaking found opponents. Error code coconut and auto loose to the card. The fun part is only 2 players got loose. The third one got the error but the -blam!-ing game didnt gave him a loose match to the card like us and he got 9-0 and we two had 9-1 because this -blam!-ing coconut error