Diving deeper into 2D

-

 Next course was about 2D and generic gameplay programming, using C# and XNA, which was a thing at the time.

For this course we didn't have any strict requirements for the game, only use everything that we learnt during the course.

We decided with my friend to make a 2.5 beat 'em up prototype to put our knowledge to the test.

Here's what we had learned during the course:

  • Simple dialog system that showed/hid sprites during it's execution.
  • Sprite animations with sheets.
  • Scrolling.
  • LERPing (manually, no tools, I realize now we implemented our own tweener)
  • UI
  • Sounds
  • Probably some other things that I can't remember now

And so we started looking for some nice assets, and found some cool Wolverine spritesheets, which weren't nicely packaged, so I had to manually cut them and paste them, and use a special tool for sprite animations to set the times and preview the animation. Spent so much time fixing the positions and offsets of each frame, until it kinda looked good.

We couldn't achieve a fully working game, but it was good enough to test the mechanics. Used a state machine to control the character's movement, jumping, hit and damaged states, added shadows, sprint movement, sorting for the characters to render correctly.

We also created a simple combo system for attacking and doing some more powerful hits. The enemies are pretty dumb, they just go towards the player and randomly attack, also implemented with a state machine.

The menus also looked nice, transition between options felt good with the sound effect and the alpha and scale tweening. The intro is a piece of art.

Just take a look at the result:


It would have been awesome to finish the game, but when things start getting complicated, and with no assets, it was too much of a challenge to achieve a fully working game.

But it felt and looked nice, really proud of this one too.

Comments

Post a Comment

Popular posts from this blog

Semantic versioned Unity package template

-
As software developers, reusability is very important to speed up future development, continuously improve existing modules, promote decoupling. We had some manual process for reusing and importing existing packages we developed, but Unity is going towards a Node oriented package management system, and we decided to adopt this new way of packaging our modules in Unity. Not only did we want to create Unity packages quickly with a template, but also be able to do automatic semantic versioning, and force commit message format. That's why I put up this Unity package template with semantic versioning and commit lint integrated into it. Now we can just create a new repo using this one as a template (or forking it), and we have a nice quick start for our new packages. https://github.com/tuttocodes/Package-template Because I used Github, I created a Github Actions workflow in order to execute the semantic versioning when pushing to develop branch, but this is something that needs to be upd...
Read more

My beginnings!

-
Image
I started studying software engineering in 2008, having grown up playing some really awesome NES and PC titles. I'm from a small city in Uruguay and it was very hard and expensive to get a SNES or N64, so I just dreamt with those. Super Mario, Commandos, Age of empires, Half life, Half life 2, Half life 3, oh no, wait... "How was all of this possible? I need to know how this is made..."  And there I was, learning how to code the very basics. After 3 years of learning I had the opportunity to take on my first videogame development course, I was SO excited, that was why I was there after all. We used C# and Blitz3D. C# because we were very familiar with it, and Blitz3D, well, I guess because it was something that we could use with C#. We learnt the basics of writing a game loop and updating and rendering our game. Made a small game in 2D and then jumped into 3D. These games were developed in teams of 2 people, but I was so motivated that I'm sure I knew all the code inv...
Read more