Side Projects

Published by

on

Sometimes there is a plain and simple issue of motivation. In my case, I ran into a bit of a wall when it occurred to me just how much game I still need to make. You work on algorithms, placeholder art, color palettes, and even documentation like this blog or the wiki and it occurs to you randomly how little of a whole game you’ve made so far, and end up overwhelmed by the mountain of stuff you still have to do. Maybe you realize that you need way more frames of animation than you thought, or your world generation needs a serious overhaul to build worlds that are actually fun and interesting, or perhaps that you’re going to need music and sound effects and have no idea how to make either. Standing at the base of that hill you suddenly feel you need to stop for a bit.

So everything sort of stops. You want to work on it, but when you think about doing it you come up with something else to do. Or you sit down to actually work on it and Visual Studio needs yet another update and by the time it’s done the moment is gone. I needed a distraction or five, and I needed them to at least adjacent to the goal of making a game.

First I came up with a NES emulator that runs in a browser. I’ve actually tried to make these in the past and I’ve never actually gotten far enough that it would run code. I knew I was interested in this for several reasons, but I also knew it was way too large of a distraction to work on. This inspired the idea of “I’ll make AI do it.” I will be the first to admit that hurts my feelings more than a little, but I wanted to see how AI would do. After a couple weeks of free tokens, I had a NES emulator that worked, sounded right, and was fun to play. More importantly, it had the ability to disassemble games from machine code back into 6502 assembly language, which has Fracterebus related effects that I don’t want to spoil.

Next, feeling amused by a NES emulator, I thought “maybe SNES?” So another couple weeks of free tokens and I also had a functional SNES emulator that runs in a browser. Initially this one was just a pure “see if it could” sort of project without a Fracterebus related tie-in. But then it was working and something occurred to me. Something a little screwy. I have a SNES emulator that’ll run on anything with a keyboard without anything to install, what if I demake Fracterebus?

At first my brain pushed back on that. “You can’t demake something that isn’t even a thing yet, right?” The surprise answer was “sure you can, that’s not a rule.” What if I make a reduced version of Fracterebus for the SNES as a sort of test bed and idea factory? To be clear, I don’t have a clue how to code anything useful in 65816 assembly for the SNES, so this was going to be another AI project. Something I can use to try ideas, find holes in my plans for the real game, and iron out kinks I didn’t even know I had.

With that the idea of Fracterebus Demake was born. As a game destined to live on a SNES I have lots of limitations being imposed by the hardware of yesteryear, so I have to pair it down.

These are the limitations I’ve decided on:

  • It will not include world generation (which is a LOT of the point of the full game, but there was no way I was going to do that on a SNES).
  • Which means it will not support Seed Codes or Verify Codes and will instead have only world zero.
  • It will support only the “core 6 biomes” (common, end, fire, ice, earth, air). These are the same ones in the real world zero. The core biomes and 2 opposing pairs of elements.
  • Which means the other biomes planned for the full game and its DLCs simply won’t be there.
  • I’d like to try to cram in as much of the movement tech as possible and as many weapons as possible so I can try them out and see if everything makes sense.

It’s been working too! All this thinking about Fracterebus Demake and arguing with Claude about how to do things has started to build up proper motivation to work on the actual Fracterebus. I haven’t resumed just yet, but I like where this is going and it’s making me want to and that was the whole point in the first place.

Another final side project I’ve been working on (this one without any AI assistance) is a NES disassembler. The goal is to try to come up with an algorithm to take a .nes file and turn it into a text file. It’s already a few thousand lines of code (mostly devoted to reading .nes files with all their multi-versioned complexity) and it does spit out assembly code for things that resembles parts of disassemblies I could find online. This one was for good old fashioned coding and problem solving and I’ve been enjoying it.

In conclusion, when you’re working on something huge and lose your way a bit, don’t be discouraged. It’s a normal part of the process as far as I’m concerned and it’s only temporary if you can come up with something adjacent to work on that entertains you and rebuilds your interest in the actual project in the process. Taking a break and doing other things isn’t a bad thing, it’s just a break and a way to get yourself back on track if you do it right.

Previous Post