{"id":84021,"date":"2025-01-28T23:18:36","date_gmt":"2025-01-28T23:18:36","guid":{"rendered":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/payday-3-dev-blames-player-progression-wipe-for-long-day-one-patch-delay-dexerto\/"},"modified":"2025-01-28T23:18:36","modified_gmt":"2025-01-28T23:18:36","slug":"payday-3-dev-blames-player-progression-wipe-for-long-day-one-patch-delay-dexerto","status":"publish","type":"post","link":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/payday-3-dev-blames-player-progression-wipe-for-long-day-one-patch-delay-dexerto\/","title":{"rendered":"Payday 3 dev blames \u201cplayer progression wipe\u201d for long day one patch delay &#8211; Dexerto"},"content":{"rendered":"<p>Payday 3 dev blames \u201cplayer progression wipe\u201d for long day one patch delay Deep SilverThe Payday 3 studio says the monthlong day one patch delay is due to concerns about a \u201cplayer progression wipe.\u201d Payday 3 launched in late September, though it did so in a state of disarray. The rocky release was beset by server troubles, crashing, audio-related issues, and myriad other issues. Developer Starbreeze Entertainment promised to deploy a major patch packed with over 200 fixes. The update was meant to arrive on October 5, then got postponed to mid-October. On October 16, Starbreeze shared a message saying the day one patch needed more time in the oven because of newly identified issues. The studio\u2019s back in the news once again, this time offering players an explanation for the unfulfilled promises. Payday 3 dev explains the day one patch\u2019s lengthy delay In a \u201cQuick Update\u201d post on the Payday 3 website, Starbreeze apologized for being radio silent for the last several days. The team does have a small update to offer now, however \u2013 the long-awaited day one patch is currently making its way through a \u201ctesting and certification process.\u201d It still lacks a firm release date, but the Starbreeze post explains what\u2019s been taking so long. The reasoning is \u201cvery long and complicated,\u201d the post says; the short of it is this \u2013 after launching Payday 3, the team uncovered \u201ccritical errors\u201d affecting its update pipeline. Their findings revealed that player progression was at the risk of being wiped, meaning holding onto the day one patch represented the best path forward. The message reads in part, \u201c\u2026we discovered critical errors with our update pipeline shortly after the game released. There was a significant risk to player progression being wiped if we didn\u2019t address this and ensured a solid test environment.\u201d Discussions about the message on Reddit show most players are just happy the update is finally on its way. And they now have a better understanding of the need for repeated delays. As one user put it, \u201c\u2026can you imagine if they dropped the patch and everyone\u2019s progression got wiped? That would do more damage to the community than continuing to delay it.\u201d Still, others wish this information would\u2019ve been relayed much sooner. One such comment reads, \u201cI\u2019m glad they were able to tell us at the very least. Had they told us sooner, we wouldn\u2019t be doomposting, probably.\u201d Hopefully, in taking their time, the Payday 3 developers will be able to deliver a patch that truly turns things around for the shooter.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Payday 3 dev blames \u201cplayer progression wipe\u201d for long day one patch delay Deep SilverThe Payday 3 studio says the monthlong day one patch delay is due to concerns about a \u201cplayer progression wipe.\u201d Payday 3 launched in late September, though it did so in a state of disarray. The rocky release was beset by [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-84021","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/84021","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/comments?post=84021"}],"version-history":[{"count":0,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/84021\/revisions"}],"wp:attachment":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/media?parent=84021"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/categories?post=84021"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/tags?post=84021"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}