Bungie Cancels Trials of Osiris Event To Fix Connection Issue

This weekend's Trials of Osiris event has been cancelled by Destiny developer Bungie, specifying that main reasons are the numerous connectivity issues and a nasty damage bug.

Trials of Osiris was cancelled by Destiny developer Bungie for the weekend of June 17th. The studio has decided that Trials will not return, while originally disabling the weekend-focused PvP event for a short time.

Some players might be wondering as to why Trials of Osiris was cancelled, but luckily for them, they never knew the handful of serious issues that occurred and impacted Destiny's Crucible. The problems ranged from connectivity issues to loading issues, but the damage bug was the most troublesome. Those who were affected by this bug would be unable to do more than 1 or 2 hit points of damage to opponents, essentially making them as nonexistent in the Crucible.

It's not the first time that Bungie has cancelled Trials of Osiris, but it's the first time that the studio has done so mid-event. Bungie in prior weekends decided not to activate the event because of a newly discovered, exploitive bug, such as the Infinite Shadowshot Glitch and the more recent Unlimited Heavy Ammo Bug. It appears that issues in this case seem like Bungie's own doing, and as a result, more widespread in their impact.

Speculations are circling that the recent update for weapon balancing is to be blamed for the recent connectivity issues and the damage bug. Players have experienced a flood of connectivity errors after the launch of the new update on June 14th, with the Weasel error as most notable. After Bungie has seemingly fixed that problem, reports of the damage bug were coming in.

Everyone may not know that exploits are one thing - but to be unable on making sufficient damage is another. By cancelling Trials of Osiris, it's good to see Bungie is addressing the issue head-on. There's no info on whether this will also affect upcoming events like Iron Banner or next weekend's Trials of Osiris, but it's certain that developers are working hard and fast to fix the issue.