Iron Banner has come around again as of this post. It looks like after Thanksgiving, reports of error codes have started to jump up again aside from things like Tapir, Weasel, Nightingale and all of the other usual ones that have been reported left and right for at least a month. The thing is, there seems to be a trend. It looks like every time Iron Banner comes around, more errors jump up and sometimes the game just gets a bit laggier. Error code Currant spam gets worse. Anteater errors rise up as well. There have been a lot of reports about error code Kale in Iron Banner just recently. And also just recently, Cabbage and Lettuce errors have started to come up a lot in the forums again. Haven't been on the game much this week to see any of that, but we'll see (see EDIT below). I've even noticed some traffic in the forums lately and saw that forum users have gone back to my old post about Cabbage and Lettuce errors, "To Players Reporting CABBAGE and LETTUCE Errors, Please Read This Post (and Bungie please fix these errors!) (FINAL UPDATE ON THIS POST)", and started to upvote it more here and there since a couple weeks ago. That post lost traction some time ago and was last edited October 28th just in case users came across it, but all of a sudden it's been getting attention again in the Help Forums. It's been over a whole month since I last edited that. I don't know about you guys at Bungie, but I think your servers are hitting some limits already based on everything that's been reported since Cross-Save was implemented. Besides that, among a bit of the community, Iron Banner has always been known to stir up errors and lag since Destiny 1. Why is that? - EDIT: Alright, I just checked up on the game and how it is on my end. After I got finished at the Tower and the Tribute Hall, I started to do some strikes. Within the first hour of doing strikes, I've already had a Lettuce trying to fly into an activity once and I got Anteater in the middle of another strike. To me, Lettuce happens here and there, but I do not normally get Anteater anymore these days, so clearly something is wrong. I ran a few tests on my end and checked up on some info to see if my net has changed since last week, because it was working alright then. But nothing has changed. Even the internet on my laptop is working fine. And from the looks of it, everything I've stated to happen above the edit of this post appears to be holding true still. I encourage you guys to check up on Iron Banner and see if there's something not working properly with it being active. Of course, not everyone is experiencing these problems right now, but a chunk of us all are and I doubt it's just a coincidence that we all got this problem at around the same time. And I'm very sure we aren't all using the same ISP.