I have this quirk as a game maker that I can't shake off, I tend to make games in the order the player sees them, using final assets whenever I can. Usually - I think - as a game designer, I should go all in and figure out core mechanics, systems and other gameplay loops to see if they're fun before doing anything else, but that's not how I proceed. I go with making the game in order; First, there's the title screen, then you get the main menu, then a few cutscenes or other story elements, THEN the gameplay happens. As I write this, I realize that it's not such a big deal, I'm not doing the entirety of the game's art before doing any mechanic; I just love to see what the game will look and feel like when working on it. After all, I'm not just the designer, I'm also the programmer and the artist, so I have to make sure that everything fits together before I can design around technical limitations.
Yesterday evening, I have started looking into my asset pipeline, it's not going to be super easy but I guess I can manage it. I had to download a bunch of new software and mess around with it to see how this is going to work and I coded a bit of the intro screen this morning. I think that today I'll try and think about the various interfaces I'll need.
- Time spent on the project so far: 3 hours
- Currently working on: Intro screen, interfaces
- Screenshot after the jump: Capcom logo parody in the intro