Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I should've hard coded my prototype

Lesson learned!

That's right, I made a robust skill system full of abstractions which allowed the expansion of the skills. But guess what happened?

Apparently I forgot that I didn't think much about progression system and when I looked at the skill system again, it's hard to accommodate the expansion of the system itself.

Well it's my false for being unwared until now, you could say it's skill issue.

I'll have to plan my game systems again to properly cover the entire project. Though it's not that much because I only wanted to add something which will make the game not a boring one trick pony.

As a matter of fact, I could extend the system by having superficial progression system which only take the numbers into account. But I don't want that. So I should make a prototype exclusively for this progression system to see the landscape before I design the game system again.

I mean it's hard to just write on the planning board and think of something I barely see the picture right?

Well good news though, despite having a problem with the systems I implemented, I improve my blender skills enough to make some nice models. Here is a short video I published a few days ago.

Well nevertheless I'm slowly progressing toward a complete game. I need to figure out the next prototype and then I could fill stuffs up and finally make the vertical slice.

My goal is just a casual action game with linear progression. So the progression system is just there to add the vibe for my game. You could say to make my game slightly more unique than just a generic game with weird models.

BTW the artstyle is already decided, so the short video above should tell you what to expect from the final game.

Support this post

Did you like this post? Tell us

Leave a comment

Log in with your itch.io account to leave a comment.