Skip to main content

Self-Motivation is hard!

Ok, so it's been a while since my last update. I've been grinding away at this game so hard, and made very little progress as you can see here. 

I've been grinding away at this game for a while now and I've learned a lot.

The number one thing I've learned so far is that I should have spent a few weeks learning a really good game engine and then just used that. 

I've spent so much time just writing boilerplate and infrastructure, that I've yet to build a decent game. 

I remember complaining so much about the lack of game engine choices and how hard they are to learn - but, it's even harder writing everything from scratch. And when I say "everything", I mean EVERYTHING! 

I've created resource loading classes, scene management, view trees, sound management, audio queues, playlists, rendering pipelines, camera classes, starfields, parallax scrolling, state management. 

Everything, painstakingly written from scratch. 

For one redeeming moment I can at least say that I've learned an incredible amount of things - how to do things, as well as how not to do things. 

But if I may pass on some knowledge to you, it will definitely be this: If your goals to learn, then do what I did, learn and create from scratch. 

Just don't expect to write a complete game this way. 

If your goal is simply to create a good game, then use a decent engine, somethig that has most of what you need. 

You'll get most of the way to your vision without the infrastructure getting in the way. 

Iff you have lots of time and you're a masochist, then join me, I'm in room 11 tearing my hair out.

Comments

Popular posts from this blog

Writing a home-monitoring system using python + internet...

Hmmm, what's that, you say? A Python home monitoring system? Why would anyone want to subject themselves to that kind of abuse? Well, I , for one, amd lazy ... it shows in my work, it shows in my lifestyle, it shows in my weight .. and it shows in the way I write code. I'm the guy that will spend 2 days writing an app (which is available for purchase on the Google App Store) because I'm too lazy to get up and get myself a credit card ... because I'm too lazy to get up and scratch in the drawer for my old credit card so I can purchase stuff from Google Play ... Before you go ranting that I expend time and effort to write an app which costs $3 ... you must remember that I am a programmer .. code it like water to me - extremely bitter, and mostly salty water, but water nonetheless ... I eat code, I think code, I dream code and I can churn out code if I want to because it has become second nature to me. So it's simpler for me to just write it myself than it is to

Finding a Game Engine is Hard

Well, if you're new here - congratulations on finding the most useless blog on the planet. If you're not new here, thanks for coming back to another installment of "And he just keeps moaning!", this weeks episode deals with how hard it is to select a Game Engine for your development needs. As I've mentioned in the past, there are many things to consider when developing a game: Storyboarding Specification document Game Engine Resources (art / sound / levels) Time constraints Return on Investment Since I've preached about the Specification Document all throughout my last post , I'll save you a little bit of reading by saying it's nearly the most important part of the entire process - nevermind having a compelling game - without the specification document, nothing gets built. Storyboarding is kind of like the specification document, but it allows you to draw little screens of the game as you imagine it to be, without too much detail.