Home Creators Posts Import Register Favorites Logout

Content

Hello!

You know what I just noticed? I never made one of my amazing Dev Log thingies for v0.19. Must've slipped my mind or something, I dunno. Anyway, now I do have another one for you, addressing v0.20's development, the general state of affairs, and maybe some other stuff, we'll see.

But before we get into that, let me wish all of you a Happy New Year! I hope you had a good time over the holidays and are now roaring to tackle 2023 with renewed fervor alongside me and the girls from CH! Either way, I hope you're happy and healthy.

Now that that's outta the way, let's talk about the important stuff: The next update of your all-time favorite game Crimson High!I've used the last couple weeks over the holidays to prepare content for about 3 normal-sized (12k-16k words) updates. Of course they still need to actually be made, but.. well, they are prepared at least! (In case you're interested in learning what exactly that means and how I go about preparations, head over to CH's Discord and let me know - getting into it now would exceed this post's limits)Anyway, back to the original topic of the next update! The update's looking great so far and I think you guys will have a really good time with it.There is one big question on my mind regarding it, though:

How long will the update be?

Let me explain: So far I had imagined v0.20 as one big whole-day-encompassing update. Looking at the prepared pre-script for it, however.. it would be a really long update. While that may sound great at first glance, it also means an extended development time, and I'm honestly not sure that I like that, since it would mean making you wait longer for your next dose of CH.

I'm considering putting this decision up for a vote on here, too, but if I do, it won't be a deciding vote but rather a supporting vote to at least have you guys' opinion on the matter to consider when making the decision.Feel free to let me know what you think about this over on Discord or via DM, too!

Once I know what I'll do, I'll make another glorious Dev Log on here to let you guys know, too.

Alright, enough about v0.20 for now. Let's talk about some other things, shall we?

I've already announced this over on Discord, but I'm planning on hosting a couple different contests this year. Some of them will directly affect the game and/or its public channels (Patreon, Itch, etc.), while others will mostly be for fun and to give you guys a platform to show off your work. The details of each contest will be announced shortly before the respective contests start. 

Aside from that I don't have much to talk about right now, I think. Instead I'll stop here and get back to working on v0.20.

I'll be back with another Dev Log soon!

Thank you all for being here and being awesome, guys and gals!

Cheers!

Comments

Silent Kosmos

I'm in favour of having the whole day finished even if it means I'd have to wait a little longer. I mean, if you end up splitting it into two, I can just ignore v0.20 and wait till v0.21 is out and have my full day playthrough then. ┐(◔‿ ◔)┌

VertigoGaming

That's actually a good point I had not thought about before. Going for two updates instead of one gives you guys a choice. If you want to, you can always wait until the second half is out as well, but those that don't want to wait can play earlier. Interesting. Thanks for your input!

Velgus

I've seen some other VN authors handle things like that by having their updates titled 0.20Part1 and 0.20Part2, for example. Something like that could help making it clear that there is an arc there that is somewhat meant to be read together.

VertigoGaming

Hmm, it's not more meant to be read together than any other updates. If CH were a sandbox game, this would make a lot of sense, but since it's not, the Saturday will seamlessly blend in with the rest of the game in the long run and it doesn't really make a difference if it's played in one big chunk or in two smaller ones. It might be worthwhile to mention the relation in the respective release posts, though. Thanks for the suggestion!