Wednesday, August 10, 2011

Switching from hierarchical to component based game object design.

Hi everyone,

I read some interesting articles about component based game objects the last few weeks and after testing and playing with this kind of game object architecture, I decided to throw away my existing hierachical game object architecture and stick with the component based instead.

I know it's unthankful work and I really try to not think about it too much, but while I was playing around with this kind of architecture, I defenitly saw the advantages compared to the hierarchical one.

As you can see on the left, I already created an UML diagramm for better understanding.

I don't know if I will stick with this implementation, as I threw it together in just no time, but I think it's defenitly going into the right direction.

Enough on that topic, now I want to say a little bit about my private stuff.

As some of you might now, I just finished my apprenticeship about 5 weeks ago. I currently still work in the company I made my apprenticeship in, but I really want to get into this gaming stuff so I applied for a place in a german college of computer science - specialisation game development (FH Heidelberg).

After some really, REALLY annoying bureaucrazy I finally got the answer from the college that I can matriculate. So from the 1st October 2011, I'm officaly a student :)