#dev log

[idrellegames]

Since I've been getting a few more asks about Episode 3—no I'm not hiding it from anyone, no it's not going to be released for the public any time soon, and yes, it is being worked on, and yes it is getting closer to being finished!

The majority of it is available to play as an alpha demo on my Patreon, although what currently playable is locked to specific Episode 2 endings.

My quarterly roadmaps are posted both here and on itch.io, and have all the updates about what's going on with Episode 3 and where I am currently am in development (Q1 report is here, Q2 report here!).

Episode 3 is the finale of Act 1. There are a lot of choices, a lot of decisions that will impact the future of your playthrough and your Wayfarer's journey. Many of your decisions from Episode 2 will come back to haunt you (in a good way or a bad way) in Episode 3. This episode is going to change everything, and the game and your Wayfarer will not be the same afterwards.

Finally, Episode 3 is the length of a full IF game due to its complexity. There is a reason why it is taking so long to develop. I know folks are impatient for more, but Wayfarer's episode structure is more like installments in a long-running series than chapters of a book. It takes time to pull off something like this, and I promise it will be worth the wait!

Green parts are playable and in the alpha build; blue is completed but not coded (and therefore are not in the alpha); yellow is in the drafting process; red is not started. word count is cumulative for all variations/routes/paths; single playthroughs will vary greatly in length depending on choices made.

I am very close to the end now, but it is very difficult to accurately estimate how long it will take me to finish. I know some people are angry about this, I know some people are disappointed and frustrated because the game is in-development and not a finished product. I know some people think I died and fell off the map or abandoned the project because it hasn't had a public update in a very long time (I didn't, I've always been here, working away).

I don't like releasing content before it's ready. I also don't like releasing episodes in bite-sized pieces even if it means more regular updates. I don't think that would make the game very enjoyable, and it also would make it buggier, with more time spent fixing stuff that I would have normally caught in the editing phase if I finished more things before coding.

I am well aware that Wayfarer is extremely ambitious in its scale, and I am going to live up to how ambitious it is. Ambition takes time, and also sometimes life hits hard. When you're a solo developer, no one else can pick up the slack if you get sick or have a family crisis or need to take time off, so you are going to perpetually be behind schedule.

(And no, other episodes are not going to be as long or as complicated as Episode 3!)

So, at this point I can't say when Episode 3 is being released. Only that it will be!

[the-kingshound]

What I've been doing (kind of a dev log)

Starting to change the code in the first few passages for Arthur (FArthur). It will be a bit of a long process but it will be rewarding

Have changed some scenes with Mordred (first meeting, and Morien's answer on him)

Slightly edited the first meeting with Morien

Edited some bugs of the last demo release

Started to slightly edit Arthur's pov scenes. I want to show them as someone who, while seemingly always understanding and calm, is quite anxious and burdened but puts on a very well made persona when in public.

Wrote the very first scene of Chapter 3

What I need to do in the future:

Keep adding the code for Arthur

Add some variations for transfem Arthur and how you expect her (some people refer to her as a man, other as a woman, so MC is understandably confused)

Edit the ch.2 scenes with Mordred

Keep editing Arthur's scenes.

Make some edits to correct the typos + critiques made to ch2 part 2.

Keep writing chapter 3

[qwertyprophecy]

Mortholme Post-Mortem

The Dark Queen of Mortholme has been out for two weeks, and I've just been given an excellent excuse to write some more about its creation by a lenghty anonymous ask.

Under the cut, hindsight on the year spent making Mortholme and answers to questions about game dev, grouped under the following topics:

Time spent on development Programming Obstacles Godot Animation Pixel art Environment assets Writing Completion Release

Regarding time spent on development

Nope, I’ve got no idea anymore how long I spent on Mortholme. It took a year but during that time I worked on like two other games and whatever else. And although I started with the art, I worked on all parts simultaneously to avoid getting bored. This is what I can say:

Art took a ridiculous amount of time, but that was by choice (or compulsion, one might say). I get very excitable and particular about it. At most I was making about one or two Hero animations in a day (for a total of 8 + upgraded versions), but anything involving the Queen took multiple times longer. When I made the excecutive decision that her final form was going to have a bazillion tentacles I gave up on scheduling altogether.

Coding went quickly at the start when I was knocking out a feature after another, until it became the ultimate slow-burn hurdle at the end. Testing, bugfixing, and playing Jenga with increasingly unwieldy code kept oozing from one week to the next. For months, probably? My memory’s shot but I have a mark on my calendar on the 18th of August that says “Mortholme done”. Must’ve been some optimistic deadline before the ooze.

Writing happened in extremely productive week-long bursts followed by nothing but nitpicky editing while I focused on other stuff. Winner in the “changed most often” category, for sure.

Sound was straightforward, after finishing a new set of animations I spent a day or two to record and edit SFX for them. Music I originally scheduled two weeks for, but hubris and desire for more variants bumped it to like a month.

Regarding programming

The Hero AI is certainly the part that I spent most of my coding time on. The basic way the guaranteed dodging works is that all the Queen’s attacks send a signal to the Hero, who calculates a “danger zone” based on the type of attack and the Queen’s location. Then, if the Hero is able to dodge that particular attack (a probability based on how much it's been used & story progression), they run a function to dodge it.

Each attack has its own algorithm that produces the best safe target position to go to based on the Hero’s current position (and other necessary actions like jumping). Those algorithms needed a whole lot of testing to code counters for all the scenarios that might trip the Hero up.

The easiest or at least most fun parts for me to code are the extra bells and whistles that aren’t critical but add flair. Like in the Hero’s case, the little touches that make them seem more human: a reaction speed delay that increases over time, random motions and overcompensation that decrease as they gain focus, late-game Hero taking prioritising aggressive positiniong, a “wait for last second” function that lets the Hero calculate how long it’ll take them to move to safety and use the information to squeeze an extra attack in…

The hardest attack was the magic circle, as it introduced a problem in my code so far. The second flare can overlap with other attacks, meaning the Hero had to keep track of two danger zones at once. For a brief time I wanted to create a whole new system that would constantly update a map of all current danger zones—that would allow for any number of overlapping attacks, which would be really cool! Unfortunately it didn’t gel with my existing code, and I couldn’t figure out its multitudes of problems since, well…

Regarding obstacles

Thing is, I’m hot garbage as a programmer. My game dev’s all self-taught nonsense. So after a week of failing to get this cool system to work, I scrapped it and instead made a spaghetti code monstrosity that made magic circle run on a separate danger zone, and decided I’d make no more overlapping attacks. That’s easy; I just had to buffer the timing of the animation locks so that the Hero would always have time to move away. (I still wanted to keep the magic circle, since it’s fun for the player to try and trick the Hero with it.)

There’s my least pretty yet practical solo dev advice: if you get stuck because you can’t do something, you can certainly try to learn how to do it, but occasionally the only way to finish a project within a decade to work around those parts and let them be a bit crap.

I’m happy to use design trickery, writing and art to cover for my coding skills. Like, despite the anonymous asker’s description, the Hero’s dodging is actually far from perfect. I knew there was no way it was ever going to be, which is why I wrote special dialogue to account for a player finding an exploit that breaks the intended gameplay. (And indeed, when the game was launched, someone immediately found it!)

Regarding Godot

It’s lovely! I switched from Unity years ago and it’s so much simpler and more considerate of 2D games. The way its node system emphasises modularity has improved my coding a lot.

New users should be aware that a lot of tutorials and advice you find online may be for Godot 3. If something doesn’t work, search for what the Godot 4 equivalent is.

Regarding animation

I’m a professional animator, so my list of tips and techniques is a tad long… I’ll just give a few resource recommendations: read up on the classic 12 principles of animation (or the The Illusion of Life, if you’d like the whole book) and test each out for yourself. Not every animation needs all of these principles, but basically every time you’ll be looking at an animation and wondering how to make it better, the answer will be in paying attention to one or more of them.

Game animation is its own beast, and different genres have their own needs. I’d recommend studying animations that do what you’d like to do, frame by frame. If you’re unsure of how exactly to analyse animation for its techniques, youtube channel New Frame Plus shows an excellent example.

Oh, and film yourself some references! The Queen demanded so much pretend mace swinging that it broke my hoover.

Regarding pixel art

The pixel art style was picked for two reasons: 1. to evoke a retro game feel to emphasise the meta nature of the narrative, and 2. because it’s faster and more forgiving to animate in than any of my other options.

At the very start I was into the idea of doing a painterly style—Hollow Knight was my first soulslike—but quickly realised that I’d either have to spend hundreds of hours animating the characters, or design them in a simplistic way that I deemed too cutesy for this particular game. (Hollow Knight style, one day I’d love to emulate you…)

I don’t use a dedicated program, just Photoshop for everything like a chump. Pixel art doesn’t need anything fancy, although I’m sure specialist programs will keep it nice and simple.

Pixel art’s funny; its limitations make it dependent on symbolism, shortcuts and viewer interpretation. You could search for some tutorials on basic principles (like avoiding “jaggies” or the importance of contrast), but ultimately you’ll simply want to get a start in it to find your own confidence in it. I began dabbling years ago by asking for character requests on Tumblr and doodling them in pixels in whatever way I could think of.

Regarding environment assets

The Queen’s throne room consists of two main sprites—one background and one separate bit of the door for the Hero disappear behind—and then about fifty more for the lighting setup. There’s six different candle animations, there’s lines on the floor that need to go on top of character reflections, all the candle circles and lit objects are separated so that the candles can be extinguished asynchronously; and then there’s purple phase 2 versions of all of the above.

This is all rather dumb. There’s simpler ways in Godot to do 2D lighting with shaders and a built-in system (I use those too), but I wanted control over the exact colours so I just drew everything in Photoshop the way I wanted it. Still, it highlights how mostly you only need a single background asset and separated foreground objects; except if you need animated objects or stuff that needs to change while the game’s running, you’ll get a whole bunch more.

I wholeheartedly applaud having a go at making your own game art, even if you don’t have any art background! The potential for cohesion in all aspects of design—art, game, narrative, sound—is at the heart of why video games are such an exciting medium!

Regarding writing

Finding the voices of the Queen and the Hero was the quick part of the process. They figured that out they are almost as soon as writing started. I’d been mulling this game over in my mind for so long, I had already a specific idea in mind of what the two of them stood for, conceptually and thematically. When they started bantering, I felt like all I really had to do was to guide it along the storyline, and then polish.

What ended up taking so long was that there was too much for them to say for how short the game needed to be to not feel overstretched. Since I’d decided to go with two dialogue options on my linear story, it at least gave me twice the amount of dialogue that I got to write, but it wasn’t enough!

The first large-scale rewrite was me going over the first draft and squeezing in more interesting things for the Queen and the Hero to discuss, more branching paths and booleans. There was this whole thing where the player’s their dialogue choices over multiple conversations would lead them to about four alternate interpretations of why the Queen is the way she is. This was around the time I happened to finally play Disco Elysium, so of course I also decided to also add a ton of microreactivity (ie. small changes in dialogue that acknowledge earlier player choices) to cram in even more alternate dialogue. I spent ages tinkering with the exact nuances till I was real proud of it.

Right until the playtesters of this convoluted contraption found the story to be unclear and confusing. For some reason. So for my final rewrite, I picked out my favourite bits and cut everything else. With the extra branching gone, there was more room to improve the pacing so the core of the story could breathe. The microreactivity got to stay, at least!

A sample of old dialogue from the overcomplicated version:

Regarding completion

The question was “what kept me going to actually finish the game, since that is a point many games never even get to meet?” and it’s a great one because I forgot that’s a thing. Difficulties finishing projects, that is—I used to think it was hard, but not for many years. Maybe I’ve completed so many small-scale games already that it hardly seems that unreasonable of an expectation? (Game jams. You should do game jams.)

I honestly never had any doubt I was going to finish Mortholme. When I started in late autumn last year, I was honestly expecting the concept to be too clunky to properly function; but I wished to indulge in silliness and make it exist anyways. That vision would’ve been easy to finish, a month or two of low stakes messing around, no biggie. (Like a game jam!)

Those months ran out quickly as I had too much fun making the art to stop. It must’ve been around the time I made this recording that it occurred to me that even if the game was going to be clunky, it could still genuinely work on the back of good enough storytelling technique—not just writing, but also the animation and the Hero’s evolving behaviour during the gameplay segments which I’d been worried about. The reaction to my early blogging was also heartening. Other people could also imagine how this narrative could be interesting!

A few weeks after that I started planning out the narrative beats I wanted the dialogue to reach, and came to the conclusion that I really, really wanted it to work. Other people had to see this shit, I thought. There’s got to be freaks out there who’d love to experience this tragedy, and I’m eager to deliver.

That’s why I was fine with the project’s timeline stretching out. If attention to detail and artistry was going to make this weird little story actually come to life, then great, because that’s exactly the part of development I love doing most. Projects taking longer than expected can be frustrating, but accepting that as a common part of game dev is what allows confidence in eventual their completion regardless.

Regarding release

Dear anonymous’s questions didn’t involve post-release concerns, but it seems fitting to wrap up the post-mortem by talking about the two things about Mortholme's launch that were firsts for me, and thus I was unprepared for.

1. This was the first action game I've coded. Well, sort of—I consider Mortholme to be a story first and foremost, with gameplay so purposefully obnoxious it benefits from not being thought of as a “normal” game. Still, the action elements are there. For someone who usually sticks to making puzzle games since they’re easier to code, this was my most mechanically fragile game yet. So despite all my attempts at playtesting and failsafes, it had a whole bunch of bugs on release.

Game-breaking bugs, really obvious bugs, weird and confusing bugs. It took me over a week to fix all that was reported (and I’m only hoping they indeed are fully fixed). That feels slow; I should’ve expected it was going to break so I could’ve been faster to respond. Ah well, next time I know what I’ll be booking my post-release week for.

2. This was my first game that I let players give me money for. Sure, it’s pay-what-you-want, but for someone as allergic to business decisions as I am, it was a big step. I guess I was worried of being shown that nobody would consider my art worth financial compensation. Well, uh, that fear has gone out of the window now. I’m blown away by how kind and generous the players of Mortholme have been with their donations.

I can’t imagine it's likely to earn a living wage from pouring hundreds of hours into pay-what-you-want passion projects, but the support has me heartened to seek out a future where I could make these weird stories and a living both.

Those were the unexpected parts. The part I must admit I was expecting—but still infinitely grateful for—was that Mortholme did in fact reach them freaks who’d find it interesting. The responses, comments, analyses, fan works (there’s fic and art!! the dream!!), inspiration, and questions (like the ones prompting me to write this post-mortem) people have shared with me thanks to Mortholme… They’ve all truly been what I was hoping for back when I first gave myself emotions thinking about a mean megalomaniac and stubborn dipshit.

Thank you for reading, thank you for playing, and thank you for being around.

[glitches-and-bugs]

Oh No

PLEASE STOP SCROLLING

I am in Huge Danger. I can't afford ANYTHING. I'm sorry I keep making posts like this I thought I was fine this time and apparently I'm very fucked.

I'm a transmasc disabled autistic person and I am in need of serious help.

P*yp*l

Kofi

DM me for other payment options.

If you want commission info, also DM me I'm very desperate and flexible. SFW and otherwise.

Even if you can't donate, reblog!! Anything helps!

[sanguinesky-if]

[Dev Log] April 2025

Hello, I hope your spring days are going well and that you're doing great!

As for my progress, here's a quick overview of my activity over the past month and my plans for the current one.

What was done last month?

▹ Chapter 3 Pt. 2: finished working on opening scene and K's scene.

The work is well underway, though I'm doing my best to catch up with the plan I originally set, as some of my health issues have slightly delayed my progress.

That's why I'm still working on finishing L's scene, which I was supposed to complete before the start of April.

However, I'm already planning to post sneak peeks of the finished scenes [including L's scene] on Patreon next week.

What will I be working on in April?

▹ Chapter 3 Pt. 2: outlining and coding the ROs' scenes [Morgan's, R's and I's scene] [after L's scene is done].

In addition to that, the bonus content on Patreon that will be released this month will include:

▹ Morgan's Short Story. ▹ L's POV [Chapter 3 Pt. 1].

Author's Note.

At the moment, almost all my energy is going into finishing the update, and I apologize for my slow responses to your asks and messages.

I've also received several extensive error reports that made me aware of many grammatical mistakes in the demo. However, I'm not fixing them right now because:

▹ I'm currently very busy with Chapter 3 Pt. 2. ▹ Uploading a quick fix would break your saves, as CoGdemos currently doesn't handle the upload of the files the same way DashingDon did [forcing the reader to start from the beginning of the game instead of from the specific scene that was updated].

Still, I want to once again say thank you to those who sent me the reports [you are the best!], and to say that I'm truly grateful all of you are reading the demo despite the most hilarious and embarrassing errors I've made.

Thank you for reading to the end! Wishing you a wonderful week and days after that! ♥

[allieebobo]

April Dev Log

Hi everyone! 

A little late, but here’s an update on what I’ve been up to in April! My time has been a little bit divided between CT:OS and Merry Crisis (and my day job/work trip), but progress is steady on both.

TLDR: I hope to have an update for Merry Crisis by End-Mar (and some bug fixes + half-chapter content for CT:OS too, if I can swing it)! 

Read the full dev log on Ko-fi / Patreon

[nightfellfangame]

January Dev Log - UNDEREVENT EDITION

Heya! This is Sam, the project lead for NightFell.

Happy Underevent 2024! We are excited to say we've been featured in this year's UnderEvent.

Thank you to the Underevent team and a personal thanks to Octo, FMS, and Rusty for having us. It was wonderful to work with everyone, it's been a blast!

If you haven't seen the trailer, you can find it on the NightFell YouTube channel!

To all the new followers, welcome! This is NightFell, a different take on Underfell. The game's demo is far along, and we plan to release it early this year. We hope you will enjoy our silly passion project. To help tie you all over during the wait, we've got something special for you...

That's right! Everyone's favorite pumpkin girl named Pumpkin is starring in her own YouTube video series! It'll be a comedic look into the world of NightFell, in all of its violent glory! 🎃

As for NightFell, how'd you all like the trailer? What parts stuck out to you, and what aspects did you like/dislike?

I'm happy to finally show off some video footage of the game. While we can't show too much (spoilers), we did get to have some reveals!

Here's our protagonist, Jackie!

And their new best friend, Flowey! He's grown up a bit since we've last seen him.

We'll see you next month for our next dev log update. Thank you for reading!

Wait! Before you go, are you an animator or a coder? We'd love to have you on board!

Sign up here!

[gravitycircuit]

🎂🥳IT'S GRAVITY CIRCUIT'S ONE YEAR ANNIVERSARY! 🥳🎂 Time sure has flown by, can't believe we're already a full year on from the game's release, and the reception still has us floored! To celebrate, we've got a few things in store for you lovely folks -- starting off with this wonderful group piece by @jmanvelez! Stay tuned for more! Have you played the game? What did you think? Let us know! Remember, Gravity Circuit is available now on PC, Nintendo Switch and Sony PS4/PS5!

[aoi1dee]

'Will She?' Dev Update!

*gets into 5-seat car with no one else inside*

Hello Will She? fandom!

Will She? is still in production, sorry I haven't been updating so much recently. Left on Read and School has taken over the entire month of March.

Since March is now over... I'm back onto Will She!!!

Now here is what to expect in the next update:

Monday!

The entirety of Monday will be included as an update which is around 12k words.

New Sprites and CGs!

Connie and the others have new sprites which fit with my current art style. The CGs that were in the prologue have been redone as well, and Monday will include a new CG.

Updated GUI!

I'm currently reworking the GUI for Will She? as I fear it doesn't fit with the vibe I want this game to bring.

---------

But Noah, when is the next update coming out?

Well there isn't an official date for the release but it is fully written and being coded right now. I say to expect Monday promotions early-mid May!

That is all for now gamers! Thank you for your support on Will She? so far

[taintedsoul-if]

I am super excited—and you might be wondering why. Well, I was mid-editing when I suddenly realized that Chapter 2 had a ton of if statements and branches.

As many of you know, I’m creating this game entirely from my mobile phone. Yes, it may look like a tablet, but it’s actually a phone. I’m currently using QuickEdit, and I just discovered that there’s a play button at the bottom of the screen—meaning I can actually playtest the game directly!

The good news? I passed both randomtest and quicktest! Yes, I fixed over fifty errors; now, this chapter is ready to go live at any moment. That makes me incredibly happy. When I published Chapter 1 a month ago, I literally read over my IF fifty times. But this time, no need for that.

I haven’t decided on a release date yet, but just know: The update is done. It’s here with me.

As for DG’s prologue, I still haven’t decided exactly what I want to do with it. Like I said, the prologue is completed—it’s a short read at around 8k words, but a good amount of stuff happens in there. It’ll probably take about fourteen minutes to get through.

And honestly, I do believe the opening of any IF/book/novel/series sets the tone. It’s what tells the reader—or viewer—whether they’re in it for the long haul. So I definitely want you all to get a taste of the prologue and see if you’re willing to come down this rabbit hole with me, lol.

For DG, all that’s left is fixing some errors, running final tests, and creating some kind of cover for it…

But yeah! You guys—I’m so fricking happy! 💃💃

Anyway, I hope everyone’s week went well—mine was crap, lol.

[idrellegames]

Hello all! 

It is the start of a new year and I’m excited to announce Wayfarer’s new development plan. Unlike previous years, I will be doing quarterly roadmaps so I can be more transparent about how things are going and make adjustments should I fall behind. 

The goal for Q1 (January to March) is to finish the Episode 3 finale. This finale is important—it is not just the end of an episode, but the end of Act 1 and represents a major story shift. Some things will come to a head, some things will be resolved, and you will be left with many, many more questions. The final includes two versions that are split between a story consequence from Episode 2—whether the Wayfarer remained hired by the Order of Lethalis or were fired from their mission. These two versions are then split in two branches, for a total of four branches that lead into 3 separate endings. 

The Episode 3 finale has been in development since last summer, and I am hoping to pick up the pace with it and get it out of the drafting stage in the coming months. Should drafting go well, I will be able to code the new material starting in March. It is undecided as of now as to whether it will be added to the alpha build immediately after coding or not. Right now I don’t want to release the finale until everyone can play it regardless of their route (right now there are incomplete starting routes—if you are not on an Aeran or Veyer route, then you will not be able to play Episode 3), but this may change. 

Wayfarer’s roadmap is an estimated timeline and is subject to change. 

The State of the Episode 3 Alpha

right click for higher resolution

This is an overview of where the Episode 3 alpha is currently sitting. There is a lot of playable material with multiple intersecting sections dependent on previous choices, faction approval, and character approval.

As of January 2025, the Episode 3 alpha contains approximately 483,800 words of total playable content (the average play session is much shorter than that). 

Other stats include (for Prologue to Episode 3):

Average Word Count Per Playthrough: 193,900 words (approximate)

Average Playtime: 11 hours

Total Cumulative Word Count: 1,414,800 words (approximate) 

The build was last updated in July 2024. It is playable on my Patreon.

FAQs

—When will Episode 3 be finished?

There is no release date! The goal is for this year.

—When is the next public build update?

TBD. Episode 3 will not be released publicly until the Episode 4 alpha is finished. As I am still working on Episode 3, it will be a long wait. I will be doing some maintenance patches on the public build this year, but they will not be content updates.  

—It’s been over 2 years since Episode 2, why is it taking so long?

I’m a solo developer, so when I get sick or need to take off due to personal reasons, that is development time lost. Unfortunately, 2023 and 2024 were both unexpectedly difficult years and despite my best attempts to stay on track, delays happened. Wayfarer’s scope is very ambitious and I know this; I am making cuts where I can, but there is a balance between scaling down and losing the vision entirely. Wayfarer is built on the idea that your choices matter, and to make those choices meaningful and impactful takes time.  

—Is every episode going to take this long?

Nope! Episode 3 is unique in how all its threads come together. I certainly do not intend to take this long with following episodes.

—When will we meet the other companions (the characters on the cover art)?

Alexia, Ren, and Calla will be introduced in Episode 4 and 5. Nelani is introduced in Episode 6 and Felix in Episode 7, which marks the end of Game 1.     

Thank you so much for your continued support! Let's get this done. ❤️

~ Anna  Idrelle Games

[titanelite22]

The Coffin Of Andy And Leyley Progress report 9

TW// Mentions Of Abuse

• Interesting to see that we'll get to play as Julia in the future episodes. Julia is the one thing that helps Andrew feel and look "normal," so any cracks under the surface will be really obvious when they're presented while playing as Julia.

• ANDREW IS NOT INNOCENT ‼️ Yes, Ashley has fucked him up, but she's only half the reason. This guy did not give a FUCK about Julia telling him that she was receiving explicit and graphic threatening voicemails. Like, dude, that's your GIRLFRIEND... He didn't even offer to call the police or anything...

• We need to see more of how Julia and Andy act around each other, but the whole snapping because she's asking valid questions? It feels so controlling in the sense that now that he's snapped at her like this, she's probably gonna be afraid to bring this conversation up again in the future. She'll probably be afraid to say something he won't like or disagree with him as well.

And if she DOES bring it up again, he's gonna snap again, and she'll immediately bend and apologise to him. It's a cycle. The last text reads, 'You forgot what you wanted to talk to him about'. That's the goal. He's gonna react like that everything she brings it up. Also, the casual language ("Nah", all the sighing, his facial expressions), saying things like "is that it?". It's so demeaning.

• Ah, yes, the high school rumours were incest rumours as we expected. I wonder how they (mainly Ashley lol) acted around everyone else for these rumours to even start.

• A lot of people picked up on this, and I'm glad I wasn't the only one - What Andrew said at the end? Those are literally the things he would say to Ashley. "Nothing will ever fustrate me like you do," "I'll forgive you for everything and for anything." He's literally talking to Julia like she's Ashley... Even the way he hugs Julia is similar to how he hugs Ashley.

TLDR;

• Nemlei got tired of people victimising Andrew lol

[notoh-dev]

The Doctrine of Perseverance (Re)Announcement

The Doctrine of Perseverance is an indie horror and mystery game currently in development. It is being developed in RPG Maker MV and includes visual novel elements. A freeware demo was released in 2016. At the time of initial demo release, I was a senior in high school. Since then, I have spent many years developing my art and have returned to my first project. The game is still early in development, so everything is still subject to change, but I still hope you find interest in my project! I'd like to showcase some updated portraits from the 2016 version.

Melrose, the main character. The story begins on her thirteenth birthday (this portrait not yet shown), where a traumatic house fire takes place. Three years later, on Melrose's sixteenth birthday, the events of the past manifest themselves once again, showing that what happened on that day is far from over.

Suzetta, a childhood friend of Melrose. A stark contrast to Melrose, she is upbeat, mischievous, and more often than not, the most mature in their friend group. Her father is a close friend of Melrose's mom, Florence.

Silas is a friend of both Melrose and Suzetta and also Suzetta's neighbor. His family harbors distrust toward Melrose's family and the renowned 'founding families' in the city of Noxton.

For those interested in the previous rendition of the game, @flareblitzedyt has a great playthrough and playlist featuring it on Youtube. Although, I must advice that many story elements have changed since then.

The previous demo was taken down a couple of years ago, but the game page for it is still up. I intend to update it in the future. Thank you for reading, stayed tuned for additional information and screenshots!

[entryn17]

I MADE A SITE FOR MY GAME !!!

VISIT IT HERE!

for now there is only a home page, an about with a summary and links to 6 different characters and their short descriptions. FAQ not available at this time. please note that this site doesn't look quite right on anything other than desktop. i'm still working on mobile compatibility!

[sanguinesky-if]

[Dev Log] June 2025

Hello, I hope you're doing well!

Summer arrived so quickly that I barely noticed while working on the update, but I hope to catch up with everything once it's released.

As for my progress, here's a quick overview of my activity over the past month and my plans for the current one.

Announcement.

For Patreon members: The release date is scheduled for June 28.

In mid-June, I'll post a progress update to let you know how things are going.

Please note that access to the code for the Patreon demo will be disabled until the public release.

For other readers: I'll share some of the sneak peeks previously posted on Patreon a week before the release date [here on the Tumblr blog].

I'd like to note in advance that I don't have an estimated time for the public release. The update may need additional polishing and changes before it's ready to go public.

Thank you so much for your support and interest!

What was done last month?

▹ Chapter 3 Pt. 2: finished working on I's scene and rewrote R's scene.

It's still a bit hard to admit because it slowed my progress, but while working on R's and I's scenes, I realized that what I had originally written just wasn't working well. I had to rewrite both scenes. While I'm happy with how I's scene turned out, I still have some doubts about R's. In short, this rewrite means that a few answers I gave to previous asks are no longer valid [you won't be able to get your MC drunk, and you won't meet another secondary rival]. Even though it was a stressful process to change what was originally planned, I don't regret my decision [I might even reuse the cut content in future scenes].

▹ Stats Changes.

I also spent time revising and refining some of the stats. Here's what the stats will look like in the update [comparison to the public version]:

I know that the stats still aren't perfect, but I think the change made them represent the choices readers can make much better than they did before. Also, there's a small coding feature I wanted to mention: If the MC has a higher "Genuine" stat than "Guarded", some of the ROs will lose alignment points if you choose to lie to them or hide things. It's a very simple mechanic:

However, there are also several ROs whose alignment points increase if the MC shows distrust or acts more guarded, so it's a situational feature.

What will I be working on in June?

Since I've paused Patreon billing, I'll be focusing on releasing the update by the deadline [T's and S's scene are last for a reason].

As I mentioned on Patreon, I was recently prescribed medication, and I'm a bit concerned about potential side effects which could impact my ability to work [and possibly the deadline as well].

Still, I hope that won't be the case. I know you've already waited a long time, and I'm doing my best to make sure the final result lives up to your support.

Thank you for reading to the end! Wishing you a wonderful week and days after that! ♥