There is No Way That Error Code KALE is Just a Networking Issue Right Now (posting for the players)
DISCLAIMER: I'm not making this post because I experience this error. I hardly ever do. I think I might've experienced this error once or twice in the past, but I haven't seen it on my end recently. I'm only making this post because I see this come up EVERY IRON BANNER and it just appears everywhere in the Help forums. I have some things to say about it.
EDIT: This Iron Banner is surprisingly not as error-code-heavy this time. As far as the bad things that it usually brings, the main thing that I see is the extra lag.
----------
If there's a chance that it helps, here's the KALE help article.
[url]https://www.bungie.net/en/Help/Article/46905[/url]
Now, I'd be surprised if this is some huge coincidence that KALE only becomes a big problem every time Iron Banner comes around. Why is it fine until Iron Banner comes around every single time? To me, I look at this and think unless Iron Banner is hosted from a different server, this once again sounds like another error code caused by LOADING ERRORS, which are VERY present in the game right now. If there's a vendor or activity icon involved, there's usually a graphical glitch there as well. Lots of players are seeing those things since this season started.
But KALE has been a big problem since mid-Year 2, along with many other error codes that behave in the game in very similar ways. Once again, I see that people check out the help articles for these errors and almost no one reports any notable fixes. All that a lot of players really know is where and when these errors tend to take place, which is at least somewhat specific. Below are some notes that I took about KALE based on what I've seen and heard.
- KALE error codes pop up a lot almost exclusively when Iron Banner is active. That is a pretty specific time for this error code.
- Occurrences are not limited to Iron Banner matches. They can happen in other matchmade competitive modes.
- There is no "Contacting Destiny 2 Servers" message tied to this error code, just like some other error codes such as GUITAR.
- This error code happens while you are flying into a destination/activity. The behavior is similar to, if not the same as, BEET, RABBIT, QUAIL, CABBAGE and LETTUCE.
- Troubleshooting solutions in the KALE help article are not known to resolve these errors.
- Players have reported that leaving your character inventory and other menus off while flying into activities could mitigate KALE error code occurrences. This has also been reported to sometimes work against other error codes as well. Nothing about that sounds like a networking issue.
Those are the main notes that I have about this error. Now don't take this for granted, but some players are reporting that some error codes are happening specifically to their account. They have said that playing in different places on other people's gaming platforms still give them the same errors when those other people don't normally experience those errors. If this is really the case, then it can't be anything BUT a loading error. This isn't something that many players test, so once again, don't take this for granted.
I just wanted to speak my mind about this. As always, I still love the game.
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.