AOMC1 DevLog 261114

Voice recording for the minor characters is done, and only the two leads are still in progress. They have a fair number of lines, so the actors are recording them over several days.

As reports from alpha testers keep coming in, I’ve been fixing things here and there. Data from the later parts of the game is harder to come by, though. I found and fixed several bugs that honestly made me wince. I also found a number of unintended shortcuts I never saw coming, along with spots that needed more polish. I paused work on the endgame content, and it’s been a whirlwind of fixes ever since. Just when things start to settle down, another report comes in and something else turns up. Even so, I’m enjoying every bit of it.

Published
Categorized as 미분류

AOMC1 DevLog 261107

The voice recording is moving along quickly. It’s my first time using voices.com and it’s been great. One of the actors already sent in their recording and I’ve got it in the build. It’s a completely different world from how this used to work. Apart from the final detailed editing — tightening the gaps between lines, that sort of thing — I handled everything through scripts, so it went fast. Compared to the old recording process, the change is enormous. I’m looking forward to the version with all the voices replaced.

(And right after saying that, I found a missing line and had to pay extra for an additional recording. These mistakes… sigh.)

Getting gameplay video is difficult, and it’s a hassle for the players who record it too, especially the uploading. So I set it up to save player coordinates every 10 seconds and send them to Discord via webhook every 10 minutes. Then I pulled that data back and plotted it in the engine, and it was a shock. (The coordinates are anonymous, and this is disclosed at the start of every build.)

I’d heard complaints before about not being able to find the way early on, and I never quite understood it. The first 30 minutes might look complicated, but the progression is purely linear. Now that abilities come a bit earlier there’s more area to move around in, but the logical structure of the first 30 minutes is still a straight line, however winding it looks. So “I can’t find the way” made no sense to me — until today.

The game opens with you breaking through a glass wall. I assumed that established, obviously, that glass walls can be broken. Then there’s a long corridor, and since just running down it seemed dull, I put a breakable glass wall in it. But the paths turned back at that point. From there they showed players searching all over other areas. Maybe they were just looking around, but it means that without that glass wall they could have kept going straight through. It never occurred to me that the glass wall would act as a barrier.

This is how I’ve been fixing the early game, one piece at a time. Some of the important skills that used to sit at the 15, 30, and 45-minute marks were moved to the start, 5 minutes, and 15 minutes, so players can range more widely from the beginning — I thought that would make it more fun, but there’s no feedback on the revised version yet so I don’t really know. That’s why I’ve been handing out alpha keys as much as I can.

Still, finding something I never would have imagined and fixing it feels genuinely rewarding. (No idea if it’s the right direction.) Rewarding and hard at the same time.

Published
Categorized as 미분류

AOMC1 DevLog 261102

The trailer I’ll use once the playtest build gets approved is finished too. For voice actors, I considered building a recruitment page, but ended up posting six listings on voices.com instead. It’s going to cost a fair bit, but I hope the quality comes through. Now it’s time for the end content. Doing the work itself isn’t hard — what’s hard is running out of steam this close to the finish.

I’m planning to use the trailer in the “alpha build complete + looking for testers” posts on community sites and social media once the playtest build is approved. This time I didn’t build it around the music. I properly put together the opening cutscene in Sequencer for the first time, assembled the footage, and layered the music on top of that. It feels different from the previous ones — maybe better, I’m not sure. There’s nowhere for me to get a second opinion. Family opinions always land at “scary,” “pretty,” “cool” — not much to work with.

Next up is the end content. I have three pieces of end content prepared and just need to hook them up, but starting something new again has my body going slack and I can’t get moving. Part of it is probably that I thought the trailer would take a week and pushed through it in two days instead. But honestly, I want to wrap up the voice work and end content, get testing stabilized, and start preparing the next one. I have so many ideas lined up.

Published
Categorized as 미분류

AOMC1 Devlog 261029

I wrapped up testing, got yesterday’s build uploaded, submitted the playtest build for review — and then, as always, found a massive bug, spent today fixing a pile of them, and only just got the update out. It’s hard. If I get a chance to remake P0 or build C2, I think I’ll be able to put everything I learned this time to real use. There was so much I couldn’t prepare for from the start, purely from inexperience. I barely patched my way through, but it looks like it’ll ship.

I considered opening the playtest to the public, but I’ll keep it to key distribution instead. The review apparently takes three to five days. The bugs seem mostly handled, so I wanted to work on the trailer while waiting for playtest approval — but my body suddenly went slack and nothing comes to mind about what to make. This is pretty much the last trailer, and I want to do it properly this time, but I have no ideas. Up to now I’ve just been stitching together whatever B-roll I’d captured by that point.

Some moments I think “this isn’t bad, actually,” and other moments I think “what am I going to do.” It’s less heaven and hell than going back and forth between purgatory and hell. I’ll just take it as it is and fix what I can. I tested a lot, but bugs will pour in regardless. Then again, I’d be grateful if enough players show up to test it at all.

Anyway, I need to get started on the trailer and screenshot updates, but my head won’t turn — maybe I’m just worn out. Still, I keep going.

Published
Categorized as 미분류

AOMC1 DevLog 261024

Attaching the bug report feature seems to have wrapped everything up. With just a single web address, I can log reports straight into Discord. Very convenient. One more round of testing and fixing whatever comes out of it should be the end of it. I’ll start testing first and handle the end content and voice recording after that.

Maybe because it was so grueling, playing straight through and reaching the end of the test run was genuinely moving.

User testing starts next week at the earliest, first week of November at the latest. A flood of bugs I never considered is surely coming. Too hard, unpleasant, awkward, boring, too easy — all of it worries me. The game also seems fairly long, so I’m not sure anyone will have the time to test it. Everything is on my mind.

I worked as hard and as fast as I could and it still ended up taking nearly three years. In a world moving the way it does now, it may have been a foolish thing to do. I’m not spending three years on a game again. The difficulty of it was beyond words. Not that what comes next looks any easier.

Published
Categorized as 미분류

AOMC1 DevLog 261018

I thought I could wrap it up soon, so I pushed hard — no weekends, nothing but eating and sleeping in between. But while testing the last part, I realized it can’t ship as it is. It feels like pulling all-nighters to finally beat the final boss, only to watch it transform into its next phase. Like the finish line was in sight, and then a helicopter hooked it and flew away. I really thought this was the week. I’m dead tired, ugh. Anyway, I’m now making some fairly big gameplay changes to the late part of Reality and the threshold section. I don’t think the level design itself will change drastically, but I won’t know until I get into it. This is genuinely hard. For the first half, I tore down and rebuilt the world about ten times — starting from when I had no direction at all — to arrive at the current level design, and I used to think that was just inexperience. But after playing through this last part, I don’t think that’s the whole story. Some things just have to be fixed through testing, a lot of them. It really is hard.

Published
Categorized as 미분류

AOMC1 DevLog 261012

A fluffy white dog lying on its back on a white bed, with its paws in the air.

The ambient audio and music pass is done, the text pass is done, and I’ve worked through most of the smaller fix list. All the existing music went into the threshold, but every track had to be re-arranged into a softer version. Apart from achievements and the end content that unlocks after clearing the game, everything is genuinely finished. The credit roll is filled in too, except for the voice actors. I’ll update it as players who help out during testing get added.

A little over two and a half years. It feels strange. None of the numbers or circumstances are good, but the game is finished, and after some twenty years I’ve made something I’m happy with. That feeling will probably get dismantled during testing, but I’ll enjoy it while it lasts.

Next I’ll test it myself on a dev build, pull together another round of fixes, and work through those along with the end content. Probably about a week to get there. Handling achievements means I’ll need to register a build on Steam somewhere in the middle. After that I should be able to start testing and put out a call for voice actors before the end of October.

Published
Categorized as 미분류

AOMC1 DevLog 261010

I’ve been organizing the ambient audio and music while refining and fixing events along the way. The reality side stays dry, mostly environmental sound, with music coming in only occasionally. The threshold side runs music throughout. Taking things that only existed as isolated features, consolidating them and building atmosphere out of them — the results come back in proportion to the time I put in, so it’s rewarding and genuinely fun. My stamina is the problem. Right now all I can think about is hoping players like it.

Building bosses and polishing marketplace animations into events seem like similar work, but events are much less stressful, maybe because the outcome is fixed. In some ways I think they’re more fun too.

The surface-level story stays simple enough not to get in the way of exploration, but for players who read the text through Attune and pick up the chat logs, the much larger story underneath should come through. There are probably more players who just want to enjoy the exploration. Players generally seem to lose patience once dialogue runs past two lines, so I’m cutting down heavily on voiced lines that have to be skipped.

I keep saying it’s almost done and more work keeps appearing, bit by bit. Still, it’s converging on the goal rather than diverging, so I think it’ll be finished within the month. Then testing and voice recording.

Separate from finishing the game, I’m just grateful to my wife, who supports this whole adventure completely.

Published
Categorized as 미분류

AOMC1DevLog 260927

Finished the ending and the credit roll, and wrapped up the trailer for a game show submission. I’m not releasing the trailer separately — just put it up on Steam. It’s in this post too. I made it while being pulled between two thoughts: that nothing happens if you do nothing, and that making it won’t move anything anyway. So it wasn’t a particularly enjoyable process. No new footage went in; I just built the context out of what was already there.

Making games is about two billion times more fun than making trailers. Thinking about the next game is another five billion times more fun than that.

While pulling a shipping build to capture B-roll for the trailer, I kept spotting things that need fixing. I’ll deal with them while working on the dialogue. And the music all needs another pass too. Is the work actually shrinking, though…

Published
Categorized as 미분류

AOMC1 DevLog 260920

Phew. The boss entrance scene is nearly wrapped. A couple more fixes and I move on to the ending. I went back and forth a lot on whether to destroy that palace, since I figured it would eat a lot of time, but somehow it came together in three days. Keeping the palace meant it had to break for the boss to appear, but giving it up meant losing that feeling entirely. I had to dig out tools I couldn’t even remember the last time I used, which was daunting, but they held up well and it went fine.

That palace (Injeongjeon) was bought during the last project, and its texture sizes were a mess — it was eating video memory at a terrifying rate. Because of that, things kept slowing down mid-scene and I went looking for the cause everywhere else first, which meant I ended up doing every other optimization before finally fixing the texture sizes. Now it runs okay. The video is from a standalone build; a shipping build should be smoother.

So now it’s really the ending. For the ending I’m planning to move the levels I’ll use as backdrops into new levels, set up static poses with a bit of camera movement, capture that, and handle it as video. The music will be carrying a lot of weight here. I bought a model for the ending but couldn’t find one at decent quality. It only appears in two ending shots in a fixed pose, so I can’t bring myself to install new tools and dig through it. The model quality is rough, but I’ll try to cover for it with camera work.

As I get closer to finishing, the things I want to improve and apply next time are stirring hard. Right now game progression is handled by an in-house script closer to assembly, with no arithmetic or logic in it at all — the one exception is a basic if-then. I decided that once a game script starts carrying logic, debugging becomes unmanageable later, so the script should do nothing beyond running things sequentially and making it easy to wait on something mid-sequence. That’s how it’s built.

Next time I want to stack a BASIC on top of that assembly (I’ve loosely named it a-asm, short for aom asm; the BASIC would be a-basic). Instead of wiring commands by hand across the code like I do now, I’d add an action, have the action describe itself, and let that propagate all the way up to the BASIC layer. I’m thinking of handling the a-basic to a-asm translation in VS Code. The a-basic layer would of course keep logic at the same if-then level. Two reasons for this: easier editing and readability, and because I want to make a game in the BASIC I used as a kid. The second one I consider an excellent reason.

Beyond that, I want to fix all the mistakes I made back when my understanding of the engine was weaker. I spent 2.5 years on this project, and if I improve the things I have in mind, I wonder whether the same scope could come down to a year and a half. I went down so many wrong paths on this one.

Circumstances aren’t easy, but things like this get my heart racing, and sometimes I wonder what that says about me. It’s also what makes me feel that building things the way I do now makes me happy.

Published
Categorized as 미분류