A Destiny 2 sparrow speed bug that makes the vehicle faster than all others has deeper underlying development issues that render it impractical to apply to more sparrows, a Bungie community manager has confirmed.
Some time ago, players noted the Always on Time Exotic sparrow was faster than other sparrows in the game, which max out at 160 speed. Always on Time is also listed as 160, but due to the bug, it’s significantly faster than other sparrows in the space game.
YouTuber Sweatcicle tested Always on Time against another 160-speed sparrow and showed how it saves several seconds of commuting time.
This led to members of the Destiny 2 community questioning why Bungie couldn’t create more sparrows that operate at faster speeds. However, Bungie’s senior community manager Dylan ‘dmg04’ Gafner recently offered insight into why the the speed hasn’t become standard and why the development team hasn’t fixed the bug.
While beneficial to individual players, the bug causes the sparrow to move too quickly to allow the FPS game‘s public areas to populate with other Guardians properly. Guardians who use this sparrow may find public areas empty, making it difficult to find other players to complete group activities like public events.
The issue appears unique to the underlying code driving the exotic itself. dmg04 states that fixing the bug would effectively require removing the sparrow from the game and replacing it in players’ inventories. However, he insinuates that while the population issue could be a significant issue if widespread, it doesn’t currently impact most of the player base, which is why the team has chosen not to implement a fix.
“Team’s looked at data (community wide) to check impact. Lots of folks still use other sparrows, and the speed differential isn’t as big of a deal to most players,” he tweeted. However, he noted that he also understood people’s feelings about losing speed when using sparrows not impacted by the bug.
Always on Time’s increased speed is a bug “rooted a bit deeper in the sparrow itself” and would require to “remake the item to remove it,” says Bungie.
So, we’re probably not going to see another…