Alongside the weekly reset today, the reason for the downtime in Destiny 2 today, a hotfix has been applied. Destiny 2 version 1.1.4.1 is now live and it comes with some of the promised features all us Guardians have been after for a while.
As part of the update Rumble matches in the Crucible have been reduced from 8 players down to 6. Anyone who wants to jump in and experience the new version of the multiplayer mode is now more than welcome and fully able. The smaller player count will make the matches far less frantic, but also a bit more enjoyable because it’ll feel a whole lot more tactical, and less like you’re running around like a headless chicken. Changes have also been made in Rumble to reduce the chances of players spawning near each other. Personally this is one of my pet peeves and I’m so happy to see an effort being made to actively do something about it.
In more general terms update 1.1.4.1 has fixed an issue when players weren’t able to load into the Tower when heading there. This has happened to me a few times and it seems to have something to do with the internet connection being slow or overused, at least on my end.
Another issue that stopped Vendors from loading in the Tower has also been seen to with this update. I can’t say I’ve noticed an empty Tower before but perhaps this actually means when you go to speak to them that the animation of them doesn’t load, and therefore you can’t speak to them or buy anything from them. I’ll be glad to see the back of that, but also if anyone has ever had a Ghost Tower experience send us a screenshot because that sounds ultra creepy.
The final general fix is a bit of a big one. The issue that’s been fixed is players finding themselves unable to load into Raid encounters. I’ve had this issue a lot and it is the most frustrating thing in the world, particularly because your team is sat there waiting for you to get in and there’s nothing to be done to solve the issue.
The final change with the update is for error codes. Specifically there is now more monitoring for the ZEBRA error, which seems to be getting fixed as it’s about to be split into two smaller errors, BEET and KALE. This most likely means that Bungie have narrowed down the causes of the issue and have split them into two categories for the developers to fix or monitor on their end to find the absolute cause. Let us know what you think of the update in the comments.
Image Source: GameZone
Community
Exploring Destiny 2’s Seasonal Events
