All Classes, Interfaces and Objects

There is one MuggleDefinition per class of MuggleObject.
A MuggleDefinition is created by MuggleManager.RegisterClass
When a MuggleObject is first created, it's Initialization routine is called.
This allows objects to use no memory until they are created, so there could be many possible objects for the world, not using resources until created.
This behavior can be called ahead of time, to preload during startup.
The user does not need to worry about MuggleDefinitions. They are maintained by the engine. However they can be useful to store one-time class Data (such as the MasterObject FreeForm for ProxyObjects), and class-wide information.

Every game object is a MuggleObject. The MuggleManager stores and manages all of these objects: creation, deletion, etc.
The Create and Destroy methods should never be used for Game-related stuff.
This is because the engine will create "dummy" copies of the objects.
There are OnBirth and OnDelete methods for Game-related code.
The BuildVisuals and ReleaseVisuals are for introducing GLScene visuals.
The UpdateVisuals method is for updating your GLScene visuals.
The Initialize method is for one-time class-wide code such as building the FreeForm for a proxy object.
The OnCollide and OnDamage methods are game event functions.