Imperator Dev Diary 20/04/2020 : Dev Diaries

  • 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.
Showing developer posts only. Show all posts in this thread.

Arheo

Game Director - Hearts of Iron
Paradox Staff
Feb 13, 2018
1.176
22.010
Greetings all!


It’s been a little while since our last dev diary due to a combination of public holidays and schedule, but we’re back again, and I’ve a few changes to mention regarding the way you’ll be getting information from us in future.


Firstly though, I’d like to thank you all for the great feedback on 1.4 Archimedes, I’ve particularly enjoyed seeing the various stories and playthroughs that you’ve all been posting here and on our other social media platforms.


As I mentioned back at the beginning of the year, Imperator has been aiming at a faster frequency of smaller releases compared to some of our other studio titles. One thing that has been becoming apparent here, is that our old method of dev diaries on a weekly basis does not mesh well with this. Going forwards, we’re likely to have a couple of weeks of downtime after a major release such as Archimedes, before we launch into a more packed schedule of information filled diaries.


This achieves two things: it allows time to breathe and plan the workflow for our next release without having to make any snap decisions at an early date; and it ensures that there’s enough to talk about in dev diaries leading up to a release. There were reasonable criticisms that some of the DDs from the last release cycle didn’t contain enough ‘substance’. I think part of this is that it’s hard to see very focused feature-breakdowns in the context of the whole, so we’ll be aiming to look at features as they relate to game, and other parts of a release, going forwards.


Thus, since we’ve had a couple of weeks of down-time, we’ll start off our development diary cycle next week with a comprehensive overview of the subjects that will be covered in Menander, followed up by weekly, in-depth diaries on each one of those.


With all that said; this week I have a couple of teasers from 1.5 for you. Let me know what you think they might mean, and I’ll reveal all next Monday, as we dive into a full feature overview of the Menander update….


89P5syBIkQwqksKw7ELy0-OXkydsAKkCiclvggzDcUlXHaqxKViNSSZN2892Og1hB3y1U3sejPVBAdKqWpNjxzP-syTnGYxmWFw_YtMaRXT_o8T8whUCpYru6EkZ9UYHcbkdU8fm



khMXvE0yqgL4NxaGAdKYv_rWRhRgJPGWJ3axERMt-g7HMsdE0qAZlpWQFxsa72JEum1EPToHKPIMIz3tldUZnpAAZs_tBlA-AubD41yngTyqFTfqIS8GGPyf_sRJbZqUaC7LyiGD
 
  • 1
  • 1Like
Reactions:
I feel like you guys are going in circles.

You used dev diaries as marketing before. It lead to a whole bunch of devs telling us about the importance of early feedback. About how important it is to inform us at the beginning of the dev cycle, because it's impossible to change course at a later point in development. And so on.

Now you are going for shorter releases AND later dev diaries. Because you don't want us to be involved in the early decision making process.

Did I misunderstand something, is this a middle ground kind of thing or are we just going to be at telling us how important feedback is in a couple of month?

In reality, the difference is not so much 'when' but 'how'. A lot of our time post-release is spent on support for the preceding release - it's difficult to also commit to planning and features for the next update while that is going on.
 
  • 1
Reactions: