Brainwave! (To Spring: Dev Blog #10)

Afternoon all!

Hope you’re all keeping well and safe and not having to ride fucking buses or tubes to work if you’re still in lockdown. I hope those of you who are no longer in lockdown… Erm… Just don’t rub it in.

So my plate’s been too full for To Spring lately. I know, I’m so changeable. I’ve actually been preparing Franjo: Slumberland for the last few weeks which has eaten up a fair amount of time, then I had a breakup which left me feeling quite unproductive for a while and then Player Power released, so I’ve been trying to keep on top of fixing bugs and adding little things based on feedback. It’s insane how even in a time when we’re indoors 24/7 I don’t have time to do all the indoor shit I want to do, but oh well.

Player Power’s release has got me thinking about To Spring though. PP’s a small game but I’m comfortable in the knowledge that it’s a complete game. I might add different game modes further down the line, but for now it’s a perfectly functional little arcade game. It’s been niggling me that I haven’t been able to say the same about my vision for To Spring. Currently, technically, you could complete a run in about 2 minutes by just running from left to right, hiding from the bear for 30 seconds and then running some more. Uploading a game to Steam costs £100 and as much work as I’ve put into To Spring, I just can’t talk myself into it being worth that to me in it’s current state. Luckily, this morning I had a brainwave and I want to run it past you.

I’ve Made A Third Of A Game

To Spring, in it’s current format, follows a fox running across the tundra and diving under the snow to find lemmings while evading bears. What if the game starts out with the player as the lemming! You come out from your little hidey hole to eat the frozen plants that already litter the tundra while avoiding bears and foxes. It’s the same deal though, you can find as much or as little food as you like and this will determine how many of you and your young will make it to Spring. Then you play as the fox, hunting the lemmings that you’ve hopefully grown relatively attached to and then you play as the bear, hunting both but having both try to evade you. This way there are 3 acts, you make your way up the food chain and the final “Spring Room” that I’ve still not got around to designing can just pan across and allow you to see which creatures (if any) survived, along with their young. This feels like a more complete game to me and is one that would be easily worth releasing on Steam.

So, What Still Needs To Be Done?

Right. So we’ve still got to build the Spring Room for the ending, but now we’ve got to add the following things:

  • Lemming sprites and animations
  • Lemming holes
  • Lemming mechanics, including walk, run and dive under the snow to evade predators.
  • Make foxes able to roam, similarly to how bears do at the minute.
  • Make bears controllable.
  • Bear cave.

On the face of it this looks like a hell of a lot of extra work, but I don’t really think it will be. The first 2 points I will have to make from scratch, obviously, but the last 4 I think will be just copying and pasting from objects already present in the game. The lemming and bear controlability (WordPress says that that’s not a word, but WordPress can shh) can be copy/pasted from the existing player object or even worked into the existing player object, which is probably the smarter, but more fiddly way to go as I’ll have to cordon different sections off into the different animals.

I’m still splitting my attention at the minute but I’ll have a go at implementing some of this and let you know how I get on.

Stay safe, wash your hands and Merry Christmas, you filthy animal.

Cheers,

Dave

Advertisement

Welcome Home (To Spring: Dev Blog #8)

Evening all! I hope the moats that you’ve all surely built around your front doors by now are keeping the infected at bay. And if you haven’t already, erect a portcullis. Belt and braces, eh?

It’s been a funny sort of few days for me and my devving. Every day I’ve thought “Well I’ve only done this little thing today, there’s no point blogging about that.” But before you know it, here we are and I’ve got quite a backlog of shit to show you. To business then, gentlemen.

A Second (And First) Tileset

Not that I’ve come to write about my second tileset, I’m not even sure I ever mentioned my first. I made it at some point last week to replace the huge block of brown featureless dirt at the bottom of the screen and it looks a little something like this:

For those unfamiliar, a tileset is a group of sprites that you want to use for different sections of terrain: Flat bits and corners and ceilings and what have you. You can then use what’s called an autotiler in GMS2 to paint the entire area of terrain and the autotiler will put the correct part of the sprite in each tile. It’s probably easier if I just show you:

See how it’s using the different sections of my tileset depending on what the shape of the terrain is? I like it. So yes, that’s the first tileset, used for the ground, and here’s the second, used for the snow:

You may notice that I cheated slightly and used the exact same tileset, just painted grey with blue and white flecks, but as far as I’m aware there is no “Tileset Police”, so I imagine I’ll get off scot free with that one. Besides, Nintendo used a palette swap of their clouds as their bushes in the old Mario games and they’re Nintendo. They make some bizarre decisions at times, including the ongoing cloud storage saga, but they do make fucking good Mario games.

Jump Cursor

This has been a niggly little problem for me for a while and was satisfyingly quick and easy to solve. Although I’m quite happy now with how I’ve refined the jumping and diving process, I don’t think it was inherently intuitive as it was. So I added a jump cursor, which makes it obvious that your jump direction is based on your mouse cursor’s position and also makes it a bit clearer which way you’re going. As you can only jump upwards, having the cursor above the player has never had any impact on your jumping direction, but now I’ve added the option to cancel your jump by having your cursor up there.

Home

This is a big old section and this is where the bulk of my time has gone since the last post. I won’t go into agonising detail, but I’ve added a sort of cave at the end of the map which is the player’s home. This has included:

  • New text lines telling the player that they’re nearly home
  • New ending text lines, which scold or praise the player accordingly depending on how much food they’ve brought back tooooo….
  • THE PUPS! Small replicas of the player sprite that are colour blended with different shades of brown. They walk around randomly until the player lies down to sleep (end the level), at which point they gather round the player and also lie down to sleep.
  • Sloped walls and tiles + diagonal movement. This was quite the pain in my arse.
  • Fading terrain. The front wall of the cave fades as the player enters so you can still see yourself.

Do you have any idea what all of this means?!? It means the game has an ending! At long last, you can actually do well or do badly in it! We’re in the home fucking straight, people!

I’m not quite finished of course. There’s still some tweaks to be made here and there and after the player falls to sleep I want you to spawn in a second room where the snow has melted and it’s springtime, where you can run and frolic with your pups (As long as you fed them). This feels necessary due to the game’s title and I think could be quite a nice little ending. Maybe I’ll stick the credits up at the top of the screen while you run about. This does mean though that I’ve got a lot more art to do. 3 more tilesets at least – One for the cave, one for the ground in springtime and one for the grass in springtime. Plus new sprites and animations for the plants and rocks, maybe I’ll make some blossom that can drift through the air replacing the snow and some birdsong to replace the howling wind. There’s still lots to do.

But yeah, I don’t think it quite hit me until I wrote this all out just how close I am to finishing this. I’m quite excited. Demo below:

And that’s me til next time. Take care of you and yours, may your supermarket queues be ever short and your hands ever squeaky clean.

Cheers,

Dave

Scenery, Effects & Excruciating Bugs (To Spring: Dev Blog #4)

Old Franjo posting 2 days in a row?! Is the sky about to fall in on our heads?? Are the compasses all about to give up on magnetic directions and point down instead? Nope. Just call me hot, crispy bacon drenched in brown sauce and no butter, because I’m on a roll. Eaten by someone else of course, cause I’m a pesky pescatarian these days. I miss bacon. I’ve already veered wildly off topic.

I just can’t stop tweaking this bloody game this weekend. Yesterday I did a lot of character sprite work and today I’ve done quite a lot of scenery sprite work and functionality. I added some parallax backgrounds in the forms of different sized rocks and mounds of snow, implemented cloud and plant spawners so that the clouds and plants could be randomly scattered across the map and 3 extremely time-consuming little touches, that I’m going to get good and steamed up about if that’s alright.

The Mother Fucking Sun/Moon cycle

“How hard can it be to put in a sun and moon that rise and set with the already established day/night cycle?” I thought stupidly. Cut to 3 hours later and I’ve rigged up a circular path for them to follow and I’m smashing my head against my desk trying to work out a way of finding the length of an arc of a circle when all you know is it’s radius. For the record, it’s fucking impossible, but that didn’t stop me from trying until my brain begged me to stop. The reason I needed to find the length of an arc is that I needed to time the sun and moon’s rising and falling with the day/night cycle and for that I needed to know how far they were travelling over the course of the day or night. If they’d been on a straight line, this would be a piece of piss, but as they weren’t, it almost ruined me. The worst part is that this was the 2nd most difficult problem that I’ve had today.

In the end, I decided to scrap the fancy-shmancy arc for a more basic system, where the sun rises to the top of the screen at sunrise, travels in a straight line across the top of the screen and then lowers back down at sunset. Vice versa for the moon. This still took the horrendous maths below that took me a little while longer. I’ve managed to fudge it so that the X coordinate of the sun and Moon will start at the right hand side of my camera (I did this in the camera object so that they’d stay on screen instead of disappearing when I walked away) and then shift across to the left by the percentage of the day that’s passed. I hated this. I’m alright at maths but percentages are my kryptonite.

The lovely Straightforward Particle Effects

To be honest, this part was still time consuming and was lovely and straightforward only because I nicked most of it. There’s a Gamemaker Studio 2 youtuber that I will never stop banging on about to anyone wanting to get into game design named Shaun Spalding and during a platformer tutorial I followed along with once, he brought out a versatile particle effect that he had actually nicked himself from someone else. It’s amazing once you start coding how much of your time goes into finding stuff to nick, really.

It’s a sprite containing progressively smaller sub-images that you can summon en-masse whenever you want a cloud of dust, or in my case, snow particles. I’ve tailored this in a couple of different ways; Firstly so that the fox now kicks out bits of snow behind her as she walks or runs and secondly so that snow flies up once she dives into it. It’s ridiculous how much nicer little touches like this can make your game look and I’m really happy with it.

The Footprints That Brought Me To My Fucking Knees

I hated this. I hated hated hated this. Ever since I started this game I thought that leaving footprints in the snow that disappear after a couple of seconds would be a beautiful little touch but one that’d be really overly complicated. As it turns out, it was actually really straightforward. Seriously, it was. Let me explain why it ruined my weekend. I apologise, but I’m about to get technical. I’ll try not to get too far into the weeds, but honestly this is just going to be a rant for my own benefit. Please feel free to skip to the next section.

The theory of putting these footprints in was simple: Go through my walking/running sprites and any time the fox lifts a foot off the ground, create a separate sprite with a footprint where her foot had just been. For me, in both my walking and running animations, the fox lifts her foot on frames 1, 2, 6 and 7. So I made a sprite containing 4 sub-images of the footprints for each foot and when my fox’s animation gets to frame 1, 2, 6 or 7, it’d add in a new object that puts in the corresponding footprint frame. Does that make sense? I’m horrible at explaining things like this I think, it’s why I try not to get too technical on things like this. But anyway, the object was set up so that it’s transparency would reduce over a couple of seconds, making the footprint disappear and it all worked perfectly… For about 5 seconds.

I could not for the life of me work out why but my fox would leave pristine footprints for about 5 seconds and then it wouldn’t work for another 10, at which point it would magically work once again. I had a cooldown set up so that the fox wasn’t churning out 60 footprints per second and I disabled that, but it still didn’t work. I had the command nested inside quite a lot of conditional statements (Amateur, I know), so I tried removing it from those and having it as it’s own separate block of code, but it still didn’t work. I checked all of my sprites, all of my logic, I rewrote a lot of code that I thought could be blocking it and the fucking thing kept stopping creating footprints after 5 seconds for no bloody reason!

I eventually found the problem. It was about 3 hours in and I was a broken man. In desperation, I added the values for my sprite_index, image_index and image_speed to my debug window in the game, genuinely thinking “If I don’t fix this in the next 10 minutes, the footprints are coming out.” I was done. I noticed from here that my image_index (This is the value that corresponds to the sub-image of your sprite. The first sub-image is image_index 0, the second is image_index 1, etc) had 2 decimal places. It wasn’t supposed to have 2 decimal places. Amateur that I am, I didn’t even know the sodding thing could have decimal places! I was using a switch statement to check if my image_index was precisely 1, 2, 6 or 7 so as the image_index went out of sync and into the decimals, it stopped passing the check. Then presumably it would sync back up and start making footprints for a bit again, then start failing again. I changed the switch statement to an if statement that checked if the image_index was between 1 and 2, 2 and 3 etc and my gruelling day was finally over.

There. All better.

Phew, sorry about that. That was the first really paralysingly frustrating bug that I’ve had during the creation of this game and I needed to vent. I’ve had plenty of them before, on Flight of the Bluebird especially. Usually with bugs you have some idea what the root cause is but when you have absolutely no clue it’s a draining, helpless feeling. But yeah, my fox now has fucking footprints and you’d better appreciate them. I think they look nice.

Final Thoughts For The Weekend

I’ve got conflicting feelings at the moment. I’m really really proud of what I’ve made so far. I think it looks nice, plays nice and is just a really pleasant experience. Not Animal Crossing levels of pleasant, but pleasant nonetheless. However, it strikes me as an “Experience” (Gag) more than a game at this point. All you can really do is run around jumping at targets to make the score go up. I need to liven up the gameplay and I think that should be the next thing I tackle. I originally thought of Polar Bears as a roaming threat that you’d need to run from, but I’m not sure that’s the way to go. Any ideas, send them my way. Thoughts and advice are always appreciated. I’ll leave you with an updated demo video. See if you can spot the new bug I’ve found. I’m done for the day though, I’ll get it another time.

Oh yeah, and don’t forget to scrub your sticky palms with soap and water, you dingus.

Cheers,

Dave

To Spring (To Spring: Dev Blog #2)

Ello ello ello. How are you all enjoying the apocalypse? Bit of a pisser, isn’t it? Obviously Covid-19 is having a massive effect all over the world but I’m sure you’re as exhausted as I am of hearing about the shitty things it’s doing to people’s lives, so let’s not dwell on it.. Basically what I’m trying to say is that I, like most people at the moment, have free time to burn. Some of this free time I’ve been putting towards Fox Game, or as I’ll be calling it from now on, To Spring.

I’m so fucking pleased with myself for this title. Cocky almost. Get this, right: Winter is the time when food is the most scarce for the arctic fox, which is our game’s protagonist. And as this is a food collection, 2D scroller sort of deal, it only makes sense that our game takes place over the winter, where the challenge is in finding and sniffing out food from beneath the snow. Our end goal therefore is to make it all the way through To Spring. With me? But how do we get this food? We leap into the air and dive beneath the snow to find it. Our primary gameplay loop revolves around our ability… TO SPRING!!! Right??? … Well I was impressed with myself.

The Game So Far

Since my concept post I’ve worked on a lot of basics and I’ve had a lot of fun to be honest! I’ve got a blank, minimalist looking fox protagonist who can walk and… run… ish… Fox walk and run animations are hard, OK? It’s a work in progress. As is the design of the thing. The minimalist look sort of works but I want to try and give the protagonist a bit of identity if I can, so that’s on the to-do list. I’ve implemented a blank (For now) map, a camera that tracks the player, some snow that falls and flies past you faster the quicker you’re moving and I even put in a day/night cycle that changes the lighting the longer you play. It’s a cool little touch and looks nice if I say so myself, as is the debug mode I snuck in which allows me to see different values I need for testing purposes. Also I implemented an incredibly basic tutorial system which is just text that comes up on the screen to prompt you to move, jump and dive to find food etc.

Speaking of which, let’s dive into the subject that I’ve spent the most time on, has given me the most headaches and that I am still probably the unhappiest about: Diving for food.

AAAAAAAAAARRRRRRRRRRRRRRRGGGGGGGHHH

The title about sums it up. Diving for food is the bread and butter of my game but I just can’t get it the way I like it. This mechanic has been through several iterations.

Take 1: Basic Diving

I started out by making the player able to just jump like they would in a platforming game, using the Spacebar if you’re playing with a keyboard using WASD controls, which for now is the only way to play it, although I do plan to add gamepad compatibility. Then at the height of your jump, you could press and hold S to indicate that you want to dive down to try and get food, as oppose to just landing on the ground. Once you landed, the game would look for the food, compare where you are on the map to where the food is and if you were close enough, you’d get the food. Food could spawn anywhere under the snow and it’s depth was irrelevant. It was very uncomplicated and very unsatisfying. Annoyed, I tried again.

Take 2: Charged Diving

Ok, so how about this; instead of Spacebar just making you jump the predetermined distance upwards, you could press and hold Spacebar to charge up a jump (Ticking up to a maximum of 15 jumping power, keep this in mind) and then charge your dive on the way back down by holding S (Again, to a max power of 15). This way, if food was deeper under the snow, you had to jump higher and dive down deeper as your depth was now also taken into consideration when calculating whether you’d hit the food or not. Made sense! The problem was, it felt incredibly imprecise to control and quite clunky to boot. I needed this level of complexity, but in a more simple, streamlined and precise way. So I tried again.

Take 3: Sexy Grid-Based Diving

“Alright, then how about this??” I asked my empty room, my unkempt beard and bloodshot eyes giving away my dwindling conviction in my own decisions, “A GRID-BASED SYSTEM!”

I split up the area under the ground vertically into 3 layers of depth: A surface layer, medium layer and deep layer. I also split up the entire map horizontally into 32 pixel chunks, thus creating a grid. The food would now spawn into one of these grid cells as oppose to anywhere it liked, giving me greater control. For example, I could now make sure that the first food the player had to find didn’t spawn in a 30 minute drive away, which was very handy. I suppose I could’ve done that anyway but the grid made it much simpler.

The idea was that now, when you charged your jump and then your dive (Which remember both had a max charge of 15), any dive with a lower charge value than 5 didn’t make you dive at all and just had you land normally. Between 5 and 10 meant you dived into the surface layer, between 10 and 15 meant you dived into the medium layer and a maximum strength 15 dive power meant you dived into the deep layer, hence solving the problem with precision that my freeform approach had formerly had. Once you dive to the ground, your horizontal location is rounded up or down to the nearest grid marker, depending on which you’re closest to. As a result of all this, when you dive, as long as you charged up a fair amount, you would hit a corresponding grid cell and get any food that it contained. Although this solved a lot of my problems, it also added a lot. This wasn’t simple or streamlined at all. This had gone the complete opposite way and become convoluted.

Take 4: Sexy, Charged, Grid-Based Fuck It, Use The Cursor

So what did I do with this behemoth of code that I’d built up over days, maybe weeks of tinkering? I binned it. Well, most of it. This is something that I’d highly recommend doing if you find yourself in a similar spot. Obviously save it first in case you ever need to refer back to it, but then bin it. Start completely fresh if you need to.

I kept a couple of things: Firstly, I wanted food to still spawn in a grid as it just made sense. Secondly, I kept the jump-charging meter, only this time there would be no dive button. You’d charge up your jump the same as before and once you released Spacebar, you’d fly off in the opposite direction of your mouse cursor. This way, you were sort of catapulting your fox by moving the cursor in different directions, which feels pretty cool. Then your dive depth is calculated off of your jump power as oppose to your dive power. And uh… This is how the jump/dive mechanic still works at the minute. I think it’s alright. It’s definitely sleeker and more intuitive, but it needs refining. It’s currently fairly buggy and VERY imprecise but it’s the best it’s been so far!

That’s about it. I should probably quickly mention sound before I go though. The blue circles you see in the above video are the food’s sound radii. Once you step into one, you’ll hear the chirping of rascally little lemmings get louder and louder as you approach the food, and then quieter as you walk past it. I’ve also layered a LOT of wind sound effects from Freesound, which is always an incredibly helpful tool for projects like this, on top of each other until I got the effect I wanted. The wind gets louder the faster you’re moving while the game’s opening music gets quieter as it gets drowned out by the wind. Speaking of the music, it’s a song called Heartbreaking from Incompetech, which is an equally if not even more useful website where you can find thousands of pieces of Royalty Free Music in a massive variety of genres, all written by the incomprehensibly generous Kevin MacLeod. All are usable in any project as long as you give him a credit and I’d highly recommend having a look, although you’re a braver man than I if you listen to any of the 38 tracks labelled “Erotic”.

Next up I’ll probably be looking to finish the running animation, creating a dive animation, refining the jumping mechanic some more and other bits and bobs I come across. I’ll be back when I have more progress to report and when I get around to continuing F:AJS.

Cheers,

Dave

Fox Game (To Spring: Dev Blog #1)

Hello again! It’s been a while since I’ve done anything on this site as the amount of free time I’ve had has been really quite restricted lately. Nevertheless, I’ve had an idea and I want to document my progress in bringing it to life. I’ve already outlined the tools I use for game design in my previous post here, so I’m just going to launch straight into this with no faffing about. Here’s my idea:

Concept

You are an arctic fox. Most of you will have seen the clips on nature documentaries or Youtube or your social media of choice. I was watching some such clips the other day and I realised that the thing that really intrigues me about arctic foxes are the way that they find food: They stand there on top of who knows how many feet of snow and listen. They listen and listen and listen… And BAM! They leap up, dive down headfirst and submerge half of their body in the snow, reaching down to the source of the telltale sounds of scurryings and scratchings of delicious lemmings.

I’m imagining a 2D side-scrolling game where you are a fox wandering the arctic in search of food. The primary loop of the game, or your goal from second to second, is to listen for, locate and dive for food while evading predators. You’ll accomplish this with the help of your extraordinary sense of hearing – In gameplay terms, the slower you’re moving, the more obscured the visuals of the game will become but the more you’ll be able to block out the background noise of the tundra and hone in on the sounds of your prey, which will be highlighted visually under the snow, perhaps with the help of a highlighted circle that lets you know generally where the sound is coming from. This circle will be quite large at first, meaning you may come up empty…mouthed, but it will decrease in size as you catch more and more food and hone your skills. You’ll need to search carefully however, as polar bears may wander along to ruin your day, in which case you’ll receive a visual and audible alert telling you that you’ll need to run.

The secondary loop, or your goal from minute to minute, is to find enough food to keep yourself and your pups alive. The game will end once you’ve found enough food to keep everyone well fed, whereupon you’ll find yourself back at your den feeding the pups. The feel-good story of the year.

It won’t be a long game, or a complicated game, but as I’ve said before, my goal is still to keep things simple. I’ve made a single game so far, an arcadey sort of chaotic football simulator named Player Power which took me 2 weeks to make and so far 6 sodding months to publish to Steam. But “Fox Game” (Hit me up with a better title because I just can’t think of one at the minute) will be a significant step up on that game already in terms of difficulty to program, once you factor in all of the moving pieces.

The Plan

So far I’ve done a hell of a lot of thinking. Thinking over the structure, the features I’d want etc and I feel like the above paragraphs completely sum the game up, which is a testament to just how much I’ve restricted myself. It’ll just be the fox protagonist, a bear that can appear, some food that will appear, some kids to give it to and a shit load of snow.

Programming-wise, I don’t think there’s anything there that I haven’t already done at some point. I’ve done platforming tutorials that involved the intricacies of moving sideways and jumping and got about half way through “Flight of the Bluebird” which involved several much more complicated enemy spawners that had to create enemies on the beat of whatever song happened to be playing. Ridiculous idea for a rookie to take on in hindsight. Spawning food at random locations under the snow shouldn’t be too much trouble either, although the dive mechanic will take a bit of working out I’m sure. What I’m trying to get around to is the fact that the programming should be fine given some free time and some elbow grease. The real challenge is going to be in the art. Ridiculous hypocrite that I am, I’m planning on ignoring my own advice to keep things simple and instead trying to make this game look as pretty as possible. It just seems like the right thing to do, focusing on designing an excellent protagonist who’s animated well, to liven up the bleak, plain landscape that is the frozen tundra. If I try and get away with a shit 16 x 16 pixel sprite that vaguely resembles a dog, this isn’t going to be a nice game to look at at all.

So yes, that’s the plan. I’ll create the project in GMS2 first and work out what kind of resolution I want to work with, then I’ll start trying to get my art skills up to scratch. I’ve sort of started already actually, as you can see below. That is a 256 x 256 sprite I’ve made that could someday become the titular fox. I’m not sure if I want to commit myself to drawings that detailed and might scale back down to 128 x 128 but I’ll work all that out later.

As always, thoughts and advice are welcome, because I am shit at this (But getting better 🙂 )

Cheers,

Franjo