Home
Creators
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register Favorites Keys Review DMs Logout
Community
Telegram ThePornDude
Home Creators Posts Import Register Favorites Logout

🥳 Friday Poll — Update Release Schedule (Patreon)

Published:
2026-07-10 18:46:49
Imported:
2026-07

Poll

🥳 Friday Poll — Update Release Schedule

  • Content update every 2 months — Smaller updates, but more frequent releases ⚡ 22
  • Content update every 3 months — Moderate updates with a balanced rhythm ⚖️ 140
  • Content update every 5 months — Larger updates, but longer waiting time 🏔️ 29
  • 2026-07-10
  • 191 votes
{'title': '🥳 Friday Poll — Update Release Schedule ', 'choices': [{'text': 'Content update every 2 months — Smaller updates, but more frequent releases ⚡', 'votes': 22}, {'text': 'Content update every 3 months — Moderate updates with a balanced rhythm ⚖️', 'votes': 140}, {'text': 'Content update every 5 months — Larger updates, but longer waiting time 🏔️', 'votes': 29}], 'closes_at': None, 'created_at': datetime.datetime(2026, 7, 10, 18, 27, 8, tzinfo=datetime.timezone.utc), 'description': None, 'allow_multiple': False, 'total_votes': 191}

Content

I want to ask about something very important for the future development of Zendaria’s Corruption.

After these last updates, I understand that many people may feel that it takes too long to receive new content and I am aware of this as well.

Version 0.4.0 was released on December 24th, and Version 0.5.0 was released on June 8th. That means more than five months passed between both major updates, almost six months in total. Version 0.5.0 was a very large update with a lot of story, new systems, new party members, quests, areas, enemies, transformations, and many other things. However, I also understand that many people may not be completely happy with waiting that long between content releases.

Honestly, I am also not fully satisfied with how long the last update took. Because of that, I like to experiment with Version 0.5.10 and future updates to see if we can find a better rhythm.

It is possible to release updates more consistently, without losing quality and without rushing content. Of course, shorter development cycles would also mean smaller updates. But regardless of the schedule, I would always try to make the content as polished and high-quality as possible.

For example, if we choose a shorter schedule, future updates could alternate between:

Main story content

Side content

Bad Ends

Transformation scenes

Smaller quests

Extra character content

Something similar to what Version 0.5.10 is doing right now.

I think this is a very important topic, so your opinions and ideas are extremely welcome.

Poll question:

What update schedule would you prefer for Zendaria’s Corruption?

These are not promises yet, but your answers will help me decide how to organize future development after Version 0.5.10. Please explain your choice in the comments, especially if you have ideas about alternating main story updates and smaller side-content updates.

Comments

joeyjoejoejrshabadoo

Completely cool with something like 3 months, and if you finish something faster you can always push a release sooner if you want. And if it takes longer, so be it. We’ve all been here anyway for that long December to June wait and made it, but there are those that are hungry for new content.

Hildabrand

I say 3 for now. I have not seen the new one yet, so I can't comment if it is big enough for it or not. But at the moment, 3 sounds nice.

J. Lambing

Honestly, I'm fine with whatever you feel comfortable with. I don't mind long waits.

Djentleman

I checked the 3 months as it is the best balance. Although, since you asked for suggestions, I want to propose to you something similiar to what developers do for enterprise companies, but adapted to a game development scenario: 2 or 3 content updates: those are updates like the 0.5.10. Those are updates that simply add content to what the lore has told you. You are in fact adding more scenes here and there, both in act 1 and 2. Nothing stops you from making a second update like this for a 0.5.20 and even a 0.5.30 where you split the load of most mechanical works into more releases, so everything is guaranteed polished and ready to go. In the meantime, since you are doing mechanical works (you are not adding lore or new mechanics in the game, but reusing what you have and implement more "similar" stuff), you can polish a personal table of work for the big lore update. You can scratch the lore and how it has to continue, you can think of new mechanics you want to add, you can think on how characters develop stuff, you can think on what scenario is best for the game, but hear me out, IT'S JUST THEORICAL STUFF. You don't touch the code for that stuff yet. You write it down and maybe ask something in poll to polish the IDEAS and CONCEPTS. You are working on Content Update, you are code-wise, just adding NSFW content. This will give you a great boost in confidence because you will release many stuff even monthly between 0.5.10 and 0.5.20 while having a clear path once you jump on the big lore update. Once Content Updates are done you could potentially work on a Big Lore Update, like the 0.5.0 was. It can AND WILL require more time. The concept behind is: you have planned on what the steps are, but you take the time to add everything to the best of your possibilities in terms of lore continuation, gameplay fun and new mechanics working. In this update you will leave OPEN and "empty" scenes potentiality, releasing a big update for lore and mechanics. You add some specific bad ends and lore transformations, but the core is not NSFW related, the core is about game being shaped and developed. This could require even 3 months if you planned a lot to be added. After that you go back to the circle, faster and quicker Content Updates, where you fill the blank hearing from community about what scene could have happened during those lore updates. This will let you have always Crystal Clear what your milestones are, if something can be moved between further releases and you work on the code ONLY AND EXCLUSIVELY after you had the time to make every decision for it to have actual sense. I wish you the best and the project is turning out great. It would be a bummer for you to feel stressed, that's why I'm suggesting this approach because it will leave you always the time to think about the next steps before dwelving into it.

Void Butterfly

I am perfectly fine with the waiting time between releases especially if you continue keeping us updated with things like the dev logs. So while I went for 3 months I will just say that I would prefer you go with whatever you think is best that is more manageable and comfortable for you and whatever reduces the chances of fatigue/burnout or the overall quality of the content decreasing.

Arkven

I don't mind the time it takes as long as you are happy with what you made, I'm voting 3 months but if it needs 4 or more to finish that's fine with me too, it's much more important that the end result is good than getting them frequently

Taton

I don't realy care, as long as the weekly devblog exists. If you keep on reporting on what you did, plan to do and so on everything else will be ok.