Forum Discussion
I seriously suspect that most of the time when we don't get into the game and we're given one of those errors - in the bad old days we would have gotten itno the game and it would have been slow-mo lagging until we died and quit.
Still, where’s the fix - it’s been so long since this error started !
- 7 years ago
I remember reading from one of their devs that they couldn't pinpoint what was causing the slow-mo servers way back when. They knew that it was individual users, but the users causing the problem changed and there was no unifying criteria that the users they had tracked actually shared.
It sounds like they're honing in on it if they've managed to create conditions that, when met, boot out the specific users who would otherwise be the cause of it. If that's true, then they're already loads closer than they were when I read them admitting to being totally in the dark before S2.
Patience, Daniel-Sahn.
Game still absolutely friggin rocks when you get into it 🙂
- 7 years ago@Anlbrd But that insinuates that I have an unstable or slow connection, which I don’t atall haha .
And yeah I’m trying to have patience and would have a lot more of this was the only issue present , but as there’s about 10 more at the same time , my patience gets run thin x10. - 7 years ago@MassiveVernon Nah I don't think it's the fault of the users, I phrased it badly before. They couldn't identify a reason why the slow-mo stuff was happening before because it didn't just happen on specific servers, and it wasn't the same users leaving the lobbies every time that fixed it. It's as though we all had a turn, it's not that our connections were somehow affecting the server.
- EA_Blueberry7 years ago
Community Manager
It sounds like a good amount of players in this discussion have already seen the latest update from Respawn around the Code:Net/Leaf errors, but in case not Respawn made an announcement to the community around this over the weekend. Thanks for hanging in there and I can't imagine what it would be like to experience it every 4 games. Played over the weekend myself and I tend to only get it 1/15 or so games before going into a match, so I don't mind it as much but from your point of view I completely understand how that would be annoying.
If you're ever up to try out some troubleshooting steps there's some other posts in the forums that are worth a look to see if it can improve a bit while the team is honing in on the fix. Searching "Code:net" in the search bar the top here should yield a lot of results. Hope it helps and we really do value the honest feedback.
- 7 years ago@EA_Blueberry Yeah it’s infuriating , so much time wasted through those errors. And yeah I have tried many of the troubleshooting tips with no luck .
And what about all the other issues I brought up in my original post? There’s a hell of a lot of problems that need addressing and the vast majority of people agree with me and have posted their own topics on all these issues. Any ETA on a patch to address even a few of these issues? - EA_Blueberry7 years ago
Community Manager
The team made some changes to the disruptor rounds right after Season 2 started. They mentioned that here. There's still some great discussions happening around it in the weapons and loot feedback forum. The team will continue to monitor player data and community feedback, but we do not have any details to share right now on future weapon balance changes. A patch is scheduled this week though (at the bottom of this update), stay tuned for more info surrounding what it will contain.
Change to Disruptor Rounds Hopup
-
Reduced the shield damage multiplier from 2.26 to 1.7. It's a minor tweak while we evaluate the full weapon meta next week.
Shooting while downed is mentioned in the dev tracker and although other things might not be mentioned on the tracker, that doesn't mean those are the only things the team is working on. They still have a more extensive internal list of bugs they're tackling.
-
- 7 years ago
I have figured out one quickfix for one of the bugs. You know when you're in a lobby with friends, all press ready and only one or two of them actually get into the match while it doesn't pull you in? If you don't do anything, you won't get pulled into the match and probably get a code:leaf error. I found a fix for it.
Whenever you see that you're teammates are in the match but you're not, just leave the party and rejoin it quickly. If you do it correctly it should pull you into the game last-minute.
- 7 years ago@EA_Blueberry Glad to hear an update on progress and that a patch is on the way , Thankyou for letting us know. I really hope it does fix some of the problems and I can get back to enjoying the game!
- 7 years ago@MassiveVernon Yea I’ve not been playing alot but I hardly ever gotten code leaf or net. Maybe in total 5 times out of the 60+ matches I’ve played. When playing with premade... it was like every other due to one of them having more than me so affecting everyone. I play on Amsterdam server.
No idea why but I’ve heard belgium servers are also good but London servers give errors... so I guess it depends on the servers cause all of those servers have roughly the same ping. - 7 years ago@Koochi-Q Wish it was like that for me too, I went back on today for first time in a while and have kept track of how many times I got code leaf ; out of 32 matches , 19 code leafs and 3 times I’ve had to close the game and restart due to the attempting connection error .
Absolutely drives me insane , so much time wasted on error screens!
Yeah I play on London datacenter and can safely say it’s terrible lol - 7 years ago@MassiveVernon Brexit is interfering! XD try and use belgium or Amsterdam servers and see if that makes the situation more bareable
- 7 years ago
Well, that patch hasn’t fixed a single thing I listed hahahahha . If anything I’m getting even more disconnects now and all those bugs are still present.
Really good ay..
About Apex Legends Feedback
Community Highlights
Recent Discussions
- 14 hours ago
- 2 days ago
- 2 days ago