Understanding TDCore

As far as we, the developers, know TDCore has an unique architecture. This can make it quite hard to understand TDCore, but it's actually quite easy if you have the time to read all of this;).

TDCore was designed to be very flexible with the ability to replace core functionality with own code if required or desired. This is achieved with the classic "interface as superclass"-idiom.

TDCore is using a "implement, register, start"-structure. This means that you pretty much just have to do just that: implement the interfaces, register your new classes and then start the entire game.

The packages in TDCore are highly coupled, especially with the generic arguments used which we will look at later. This effectively binds together almost all of the packages, producing a very solid foundation.