As the title says. Also, Cabbage has become less forgiving as of late. The in-game workarounds that I've talked about in other posts have started to become less effective when the error is about to happen. Let me tell you as a reminder, nothing at all has changed on my end when these errors started to become a problem during Season of Opulence. There shouldn't be anything that suggests it's an issue on my end when the only notable thing that happened was that there were updates and changes for Cross-Save and none of my other devices are experiencing any troubles. I've even contacted my ISP, they said we should be good after we had them reset our router/modem on their end. In fact, now other devices load even faster than they did in the past. But these error codes are still here in this one game. Now I've noticed something else just recently about where these errors seem to be happening the most at for me. At the final load zones in Strikes. I've never seen it so specifically in areas like that on my end before. We've only had one patch recently and before that, I've never seen it do that on my end like it's been. It's gotta be something about the updates that are causing these errors for some players. And to all you forum users, keep in mind that every console/platform device is different with different data that can affect other things in different ways. If you grew up with a PS2 and some games that were affected by other game data or corrupted the data of other games, you might know what I mean. It's something that could be the reason why some players experience these errors and others do not. Just a possibility.