I hate delays. I hate my delays. If something else is delayed, I can wait. There's plenty to do in the meantime. But when I'm the one that has to make the call, it's a different issue. If you know me very well, you'll know I'm terrible at giving ETAs, which is why I hesitated to give one for VNgen until the very last. And to be fair, based on what I anticipated VNgen 1.0 to be at the time, it was a reasonable estimate. But the more I thought about it, the more I became convinced VNgen was missing something critical to the 1.0 experience, and so I'm going to have to ask everyone to wait just a bit longer. The good news? The wait will now be even more worth it. Today, May 18th, was originally supposed to be VNgen 1.0's release date. That's no longer going to happen. Instead, I'm pushing it back to June 1st (yes, still 2018). This I feel is a generous amount of time that will give me longer than necessary to make sure 1.0 is everything it needs to b...

Way back in the summer of 2014 I began writing my first visual novel engine. Not VNgen, mind you, and not even Edge VN. This was a third, unreleased engine—and for good reason: it was a horrible, broken mess . You see, not only was this my first visual novel engine, but the first program I had ever written from scratch. I've come a long way in four years, leading my work to be praised by developers even with many more years of experience than I have. But while my coding practices may have changed, the goal of creating an engine with an emphasis on high presentation quality coupled with flexibility and ease of use has remained a constant. VNgen's journey is both a story of three engines and one continuous effort to achieve a single goal. And although it's hard to believe, that journey is finally coming to an end. That's right: strap on your seatbelts, because our next stop is VNgen 1.0. Normally I end these devblogs by talking about the latest update to VNgen, but th...