• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Stellaris Dev Diary #161 - Development Update

Hello everyone!

For this week’s dev diary we chose to switch the order of a couple of dev diaries to be able to give you some updates earlier rather than later.

The Stellaris brand has understandably been under more scrutiny than usual for the last few months, and we want to address situations related to work-in-progress art in Federations. As an example, we had some UI design mockups (shown during PDXCon) that contained placeholder art. We want to make clear this is not how the game will appear in its final version.

Moving on to Federations: During PDXCON 2019 we said that we would give more information on the expansion later during the year – and today we want to share some news that Federations is targeted for release in early 2020. Although we understand that some of you might be disappointed that Federations will not be released in December, we want you to know that we are taking more time to make sure that the next update is going to be amazing.

In addition, to give us the best chance of improving some of the pain points you’ve shared with us, we have assigned some of our team members to focus solely on trying to improve performance and AI. It is very important to us that 2.6 does not compound any of the current issues with the game, and that we can take the time we need to address some of the issues remaining from 2.2. It’s important to remember, however, that working on these kinds of issues is not a sprint, but a marathon – it's something that is constantly being worked on over longer periods of time.

If you want to read more about performance, and how we work to maintain it over time, we shared some more information on this topic in Dev Diary #149.

While we have been unable to give concrete information or specifics related to these issues, we can say that it is very important to us. With that said, it's important for us that you know that your feedback is not being ignored, even if we have no news to share.

We want to thank you for being such a dedicated community and helping us by providing feedback and reporting issues with the game. We appreciate this to no end and encourage you to continue voicing your thoughts to us.

From the beginning of next year, we’ll be doing a series of dev diaries dedicated entirely to answering questions related to specific topics each week. The schedule for those dev diaries will be released later in December when we’ll summarize and round up the year.

---

That is it for this week! Dev diaries will resume their regular schedule, and as promised last week, next week we will be talking about some of the new things affecting diplomacy, such as Envoys.

P.S:
Since this dev diary had no pictures I felt it was necessary to add something, so here's a picture of the premade Lithoid-empire that some of you have been asking us to add to the Lithoids Species Pack! (Will also be updated with 2.6)

upload_2019-11-21_15-28-57.png
 
  • 1Like
Reactions:
It just means that you can’t give a democracy a custom title if I read that correctly.
Literally unplayable is sarcasm. But it is pretty damn irritating that it's been in the game for... ever.
 
And I already have a plan in place for what will happen should this bug ever be fixed.

Not that it will, mind you, but I have a plan. Which will require me to coordinate events across multiple time zones and two continents. But I have a plan.

And once that bug is fixed, I'm sure I will still have issues with regular other things in Stellaris, but NOTHING like the level of X. Because X bothers me. To the core of my soul.

Edit: I also like the fact that this bug has become a cause celebre among the Stellaris forum-goers. People can come to the forum and complain about performance, stuttering, pop job shuffling, endless other weird bugs... but in literally ANY thread about "bugs that are important", someone will ALWAYS mention, "And Duuk's literally unplayable bug" and 6 other people will be like, "well yeah of course that bug, but they're never going to fix that" and when someone is like, "What is that bug?" the other forum members immediately school the newbie like, "sheesh, rookie, get up to speed."

I love this forum.
 
@Duuk My favorite part is how the bug is named after you. Someone can just say "Duuk's bug" and almost everyone immediately knows what they are talking about. I like to think that when the final patch for Stellaris is released, @Jamor will personally make sure that bug gets fixed and make a big show of it in the patch notes.

It just means that you can’t give a democracy a custom title if I read that correctly.

The previous game director of Stellaris used to refer to grammatical errors and typos as "literally unplayable" bugs as a joke. He even used that term in patch notes and dev diaries.
 
@Duuk My favorite part is how the bug is named after you. Someone can just say "Duuk's bug" and almost everyone immediately knows what they are talking about. I like to think that when the final patch for Stellaris is released, @Jamor will personally make sure that bug gets fixed and make a big show of it in the patch notes.



The previous game director of Stellaris used to refer to grammatical errors and typos as "literally unplayable" bugs as a joke. He even used that term in patch notes and dev diaries.

Maybe it will be a big reveal in the upcoming patch, *you never know*.
 
@Duuk My favorite part is how the bug is named after you. Someone can just say "Duuk's bug" and almost everyone immediately knows what they are talking about. I like to think that when the final patch for Stellaris is released, @Jamor will personally make sure that bug gets fixed and make a big show of it in the patch notes.
The previous game director of Stellaris used to refer to grammatical errors and typos as "literally unplayable" bugs as a joke. He even used that term in patch notes and dev diaries.
Ah. r/whoosh then.
 
But Duuk only reported it for version 1.1 not already in 1.0 ( i looked into the bug reports from page 913 and before).
I wish you could favorite posts, because this would be mine. You took the time to look when I first reported the bug. I have a feeling it started as "This bug can't possibly have existed since 1.0 it had to have shown up much later" and then when you discovered a bug report from 1.1 you were like "Well hell."

...and 1.1 was released 2 days after 1.0, so I barely had time to report any bugs before they released the first patch. It was there, but I gave them the benefit of the doubt that it would get fixed in the first patch :D
 
I have to say, to many people it seems like a dev diary cannot be anything other than a huge chunk of text explaining new features and a bunch of screenshots. I disagree. A dev-diary is just the devs talking with the players about what they are doing with the game, be it fancy or not.

I really appreciate that you took the time to write those informations. Also, we have a release timetable!
 
I wish you could favorite posts, because this would be mine. You took the time to look when I first reported the bug. I have a feeling it started as "This bug can't possibly have existed since 1.0 it had to have shown up much later" and then when you discovered a bug report from 1.1 you were like "Well hell."

...and 1.1 was released 2 days after 1.0, so I barely had time to report any bugs before they released the first patch. It was there, but I gave them the benefit of the doubt that it would get fixed in the first patch :D
Trust but verify :D. That said I absolutly believe it was there since 1.0 but there is a search function to find all bug reports made by a forum member so...
 
Trust but verify :D. That said I absolutly believe it was there since 1.0 but there is a search function to find all bug reports made by a forum member so...
...now I want to update the tinyurl in my signature to the 1.1 bug report. Just because.

I did one better. I went and updated the bug report (in my signature) with the original 1.1 bug report link. For historical purposes.
 
Last edited:
...now I want to update the tinyurl in my signature to the 1.1 bug report. Just because.

I did one better. I went and updated the bug report (in my signature) with the original 1.1 bug report link. For historical purposes.
It's actually still the 2.1 report. I think you didn't erase all of the first link, pasted the 1.1 link, and it kept the first instead. I had a similar problem when updating my signature the other day.
 
It's actually still the 2.1 report. I think you didn't erase all of the first link, pasted the 1.1 link, and it kept the first instead. I had a similar problem when updating my signature the other day.
No, the one in my signature is still the 2.1 report. But in the 2.1 report I added a link to the 1.1 report. The 2.1 report is the "new" bug tracking system, so it's the "better" one that is in the bug database properly. Prior to like 1.9 bug reports were basically sticky notes that got handed to the devs. After that they actually got entered into the bug system kind of automagically (which is why you have to click which mods/DLC/etc you have, and it generates which checksum you're using).

So the tinyurl is still the 2.1 report, but if you follow it you'll see a link in that report to the 1.1 bug report.
 
No, the one in my signature is still the 2.1 report. But in the 2.1 report I added a link to the 1.1 report. The 2.1 report is the "new" bug tracking system, so it's the "better" one that is in the bug database properly. Prior to like 1.9 bug reports were basically sticky notes that got handed to the devs. After that they actually got entered into the bug system kind of automagically (which is why you have to click which mods/DLC/etc you have, and it generates which checksum you're using).

So the tinyurl is still the 2.1 report, but if you follow it you'll see a link in that report to the 1.1 bug report.
Ohh, I need to learn how to read. I just saw the 2.1 link, and thought the link was messed up. My bad :D
 
@Duuk I actually tried to fix the bug by modding last week. Couldn’t squash the bug. But the local mod “Duuk bug fix” still sits in the list.