Hi all,
As many who tune in last week will know, we have had some issues with the current save of the Stellaris dev clash. The save was started in MegaCorp's pre-release days and has been on the dangerous frontiers of "hot code" since the beginning. Multiple patches and hand-made alterations to this save file has obviously had an impact. Last week's dev clash ended early because of issues with sync issues, but there is yet hope!
Now, we're taking a short hiatus from the dev clash to focus on the imminent 2.2.6 patch. We'll be posting a dev diary tomorrow with a whole bunch of information that you're going to really want to read, and instead of running the dev clash we'll be streaming that. I will bring Daniel Moregård onto the stream to show these things in greater depth and detail, so coming along for that starting at 16:00 CET!
While we're focusing on 2.2.6 patch for the next little while, we're obviously putting the issue with this heavily altered and Frankensteined save file on a low priority - which means we're not dedicating time to trying to test its stability right now. After 2.2.6 releases, we'll be able to get back to that and take the necessary time to test it. There is a very real possibility that the save is beyond repair and rescue, but we're hopeful and will still try. Patch is the priority, though!
On a positive note, we were able to identify and quash an edge case issue* because of the dev clash save.
* I'd tell you what that is, but I'll be honest... when Carl explained it to me, I didn't fully understand what he was trying to explain.
Thanks for being patient with us during the strangeness that has been this dev clash and the many edits we've made to the save. Look out for the dev diary and stream tomorrow!
As many who tune in last week will know, we have had some issues with the current save of the Stellaris dev clash. The save was started in MegaCorp's pre-release days and has been on the dangerous frontiers of "hot code" since the beginning. Multiple patches and hand-made alterations to this save file has obviously had an impact. Last week's dev clash ended early because of issues with sync issues, but there is yet hope!
Now, we're taking a short hiatus from the dev clash to focus on the imminent 2.2.6 patch. We'll be posting a dev diary tomorrow with a whole bunch of information that you're going to really want to read, and instead of running the dev clash we'll be streaming that. I will bring Daniel Moregård onto the stream to show these things in greater depth and detail, so coming along for that starting at 16:00 CET!
While we're focusing on 2.2.6 patch for the next little while, we're obviously putting the issue with this heavily altered and Frankensteined save file on a low priority - which means we're not dedicating time to trying to test its stability right now. After 2.2.6 releases, we'll be able to get back to that and take the necessary time to test it. There is a very real possibility that the save is beyond repair and rescue, but we're hopeful and will still try. Patch is the priority, though!
On a positive note, we were able to identify and quash an edge case issue* because of the dev clash save.
* I'd tell you what that is, but I'll be honest... when Carl explained it to me, I didn't fully understand what he was trying to explain.
Thanks for being patient with us during the strangeness that has been this dev clash and the many edits we've made to the save. Look out for the dev diary and stream tomorrow!