ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
RTTIType: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m TS does not contain "NavyType"... |
||
| Line 9: | Line 9: | ||
!ID | !ID | ||
!Class | !Class | ||
|- | |||
|colspan="3"|'''TS, RA2 and YR:''' | |||
|- | |- | ||
|0x00||<Abstract> (can be considered an error value) | |0x00||<Abstract> (can be considered an error value) | ||
| Line 138: | Line 140: | ||
|0x3F||[[VeinholeMonsterClass]] | |0x3F||[[VeinholeMonsterClass]] | ||
|- | |- | ||
| | |colspan="3"|'''RA2 only:''' | ||
|- | |- | ||
| | |0x40||[[NavyType]] | ||
|- | |- | ||
|0x41||[[SpawnManagerClass]] | |0x41||[[SpawnManagerClass]] | ||
Revision as of 22:12, 26 January 2010
An AbstractDerivationID is what identifies every "dead-end" class (i.e. non-abstract classes) deriving from the AbstractClass uniquely.
In the game, it is often useful - for commonality's sake - to have a function or similar pass a FootClass, which is the base class of the [[UnitClass], the InfantryClass and the AircraftClass. This way, operations for moving units can be handled using one part of code.
However, sometimes one needs to know what exactly this FootClass is (one of the three possibilities named above). For this, you use the AbstractDerivationID.
AbstractDerivationID List
This list is equivalent to the one on the Factory page.
Since this is a different context, here they are listed again: