Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Two days in the past, Bungie turned off the Destiny 2 servers whereas the studio regarded into an issue that had gamers apparently dropping progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Today Bungie pulled again the curtain and defined precisely what went fallacious and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at around 2:00 p.m., Bungie tweeted that it was taking Destiny 2 offline whereas it investigated an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” Just a few hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Destiny 2’s servers would come again on-line. Nearly 4 hours later, Bungie tweeted for the final time that night time, saying that Destiny 2 wouldn’t be playable that night. Nearly 12 hours later, at round 9:55 a.m, Bungie announced it had finally solved the problem and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers fearful in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for thus lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you would possibly suppose, going into technical particulars of the difficulty.
According to Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being precipitated after it moved some “currently incompletable” challenges into a unique space of the sport’s knowledge. To do that, Bungie used a “very powerful” device that lets the studio tinker with a participant’s recreation state and account. Apparently, attributable to a configuration error, Bungie by accident “re-ran an older state migration process” utilized in a previous replace. Because of this error, the device copied previous knowledge from this previous replace into the present model of the sport, which principally undid some gamers’ latest in-game accomplishments
G/O Media might get a fee
well being
The Lyma Supplement
10 elements. One super-supplement.
Lyma makes the following technology of dietary supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a brand new patch that eliminated the mistaken change the difficulty was mounted, and following some testing, Bugnie deployed the replace. However, on account of this patch, all participant accounts needed to be rolled again a couple of hours earlier than the troublesome replace went dwell. This means any participant progress made between 8:20 and 11 a.m. on January 24 was misplaced. Any purchases made throughout this time acquired refunded, too.
While it sucks that the sport was down for thus lengthy and that the staff was pressured to spend what seems like many late hours making an attempt to repair their mistake, it’s refreshing to see a developer be so open and trustworthy about what occurred and the way it was mounted. In a time when video games really feel buggier than ever and gamers are fed up with delays, outages, and damaged updates, it’s sensible to tug again the curtain and present everybody simply how arduous it’s to make, keep, and maintain video video games as complicated as Destiny 2.
Hopefully, subsequent month’s new Destiny 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this latest 20-hour hiccup.
Discussion about this post