Stop teasing us please!

[Lykos]

Whatever happened to the dev blogs????

[Thierryu1]

Whatever happened to the dev blogs????

Nothing, those come whenever the Devs feel like updating.

[Thoby]

Whatever happened to the dev blogs????

Nothing, those come whenever the Devs feel like updating.

Development blogs are in quite a weird place now. Originally we used to write dev blogs according to current work in progress, but since we have reached quite a rapidity of producing updates (by getting familiar with the code) it's weird to write up a separate post about something you have already wrote an entire (upcoming) news post about. Most of the written code is now directly handed over to the review-team, ready to be used in an update. So a news post might be completely worked out, the update might be coded in its entirety and it's just a matter of waiting until it's reviewed and released. This makes it so we are unsure if something will be released today, tomorrow, or maybe in a few weeks. It is something we are unsure about.

This kinda removes incentive to write up a dev blog (for me personally). At this very moment, several updates are ready for release. If I wrote an additional dev blog about them, I might as well spend that time coding and preparing a new update (as I am currently doing). It's just hard to get each update reviewed and released properly, which primarily bottlenecks updates and development.

This might change in the future though, we will see. Nonetheless, hopefully this answers your question.

[Monys]

I love @Thoby

[Thoby]

I love @Thoby

Hit me up whenever you make a new dinner reservation. Cheers!

[Thierryu1]

Nothing, those come whenever the Devs feel like updating.

Development blogs are in quite a weird place now. Originally we used to write dev blogs according to current work in progress, but since we have reached quite a rapidity of producing updates (by getting familiar with the code) it's weird to write up a separate post about something you have already wrote an entire (upcoming) news post about. Most of the written code is now directly handed over to the review-team, ready to be used in an update. So a news post might be completely worked out, the update might be coded in its entirety and it's just a matter of waiting until it's reviewed and released. This makes it so we are unsure if something will be released today, tomorrow, or maybe in a few weeks. It is something we are unsure about.

This kinda removes incentive to write up a dev blog (for me personally). At this very moment, several updates are ready for release. If I wrote an additional dev blog about them, I might as well spend that time coding and preparing a new update (as I am currently doing). It's just hard to get each update reviewed and released properly, which primarily bottlenecks updates and development.

This might change in the future though, we will see. Nonetheless, hopefully this answers your question.

<3

[The underdog]

Review fasterrrrrrrr

[Monys]

I love @Thoby

Hit me up whenever you make a new dinner reservation. Cheers!

soon bb soon

[Cancerstick]

I love @Thoby

Hit me up whenever you make a new dinner reservation. Cheers!

soon bb soon

The 4 for 4 deal at Wendy's is pretty nice.... ez date night

[Explozionz]

Can the "Review team" please work faster haha, or can't we do as Mike normally does put the new "cache" updates into a test server but maybe limit the server to the possible update coming to ensure there is no bugs/flaws or is the review team more ensuring there is no Mod Jed shit going on?