March 24th, 2026 - Mikael Talk: Post-1.0 Update release cadence

March 24th, 2026

Mikael Talk: Post-1.0 Update release cadence

https://www.youtube.com/watch?v=OOu9c2fo1_4&t=7686

Suggested Wiki Refrence Code

Topics

Transcription

  1. Mikael

    We love doing it and I'll also chat and actually before we raid I'll end on the one thing that I Said we're not gonna tease anything.

    We're not teasing anything.

    There's this no 1.3 thingy mahjongy but One thing that has come up in meetings that we are actively talking about is that we we have realized that

    We agree internally as a studio that the amount of time it took between 1.0 and 1.1, it was a fair amount of time, it was like 1.10, sorry, 1.0 hit September 24, 1.1 hit June, that's like 9 months, that's fair.

    Not too much longer or shorter than many other in-betweeners.

    And especially us finding our footing post like launch launch.

    So we were fine with that We realized that 1.1 is now nine years old and live and 1.2 is still not out.

    We're not crazy We realized that like it's still like if say not saying that 1.2 will take a full year Or less or more to release but it's gonna be more than nine months at this point.

    It's a bit Time yeah

    There absolutely are what we both, chat, you and I, could consider easy wins.

    Maybe even architecture could be part of this, because honestly, like, new architecture would really not be earth-shattering or that much in need of a hard EXP branch.

    So we are toying with the idea of maybe, with 1.2 in particular, having, like, proper 1.2.1s, 1.2.2s, 1.2.3s, maybe.

    to at least have a trickle of additional stuff, more than just bug fixes coming in your way.

    So you could see stuff you clamor about that are bigger than bug fixes hitting before a supposed, if it's 1.3, if it's paid DLC, if it's free DLC, whatever the fuck the next big beat is, would be good for all of us.

    So that is something we're toying with.

    And how did I even enter this?

    Oh yeah, modders and taking community feedback into consideration.

    We always do that.

    It's just that we can do that and it can feel like it's so long between us hearing it for the first time and then finally it's next on a chopping block for us to push out and it has to be part for...

    Part of a big update for a good reason or for many good reasons But sometimes also once or twice maybe for very arbitrary reasons and finding those arbitrary reasons and detaching the content attached to those arbitrary reasons Detaching those and having them be small standalone quite easily shippable may be doable see if we have the The bandwidth to figure out how and what that is anyway The yap is going too long now