Component based vs interface/abstract class base hierarchy?
Hi, I'm new to game programming and I come from a more traditional programming background. As such, I am used to more traditional methods of OOP, mostly using interfaces and inheritance. From what I have done so far, it seems like interfaces aren't first class citizens in Unity land.
I'm just wondering what kind of workflow everyone uses to make modular game components, and what the advantages/disadvantages are of each of the above methods of doing so. Thanks a lot!
Posted Apr 28, 2015, 2:45 PM UTC
Anytime you start a new engine, code language, etc, you should rely on your own experience and perform a "basic run".
For a game engine, a basic run is to familiarize yourself with the core benefits of that engine (as you have already done), and then just jump in and make the three "core" games: Pong, Breakout/Arkanoid, Mario-Style Platformer.
I really wouldn't bother worrying about what "workflow" everyone else uses: You'll just get arguments akin to whether or not opening curly brackets should be on a new line or not ^^[they ^^shouldn't, ^^snarf]. Rather, start with those three games. There is a Pong tutorial in the sidebar, and if your code is up to par you should be able to do Breakout/Mario without the need for a full blown tutorial.
Pong teaches:
Breakout/Arkanoid is mainly for level progression and heavier component usage, and a platformer really exposes the scope of making games to fledgling game devs.