TrustedUser
574
edits
Difference between revisions of "HOWTO-Engines"
Jump to navigation
Jump to search
→Subclassing MetaEngine: Fixed to recommend AdvancedDetector
(Removed Reference To SVN) |
(→Subclassing MetaEngine: Fixed to recommend AdvancedDetector) |
||
| Line 51: | Line 51: | ||
=== Subclassing MetaEngine === | === Subclassing MetaEngine === | ||
Let's implement the plugin interface: You'll have to create a custom MetaEngine subclass | Let's implement the plugin interface:<br> | ||
You'll have to create a custom MetaEngine subclass. This provides the information and functionality related to the engine that can be used by the launcher without loading and running the game engine, which includes detecting games, listing savegames and instancing the engine. | |||
The following example illustrates this, '''but''':<br> It is recommended that most engines should instead subclass AdvancedMetaEngine.<br> | |||
This can be found in <tt>engines/advancedDetector.*</tt> and provides a standard framework for filename and MD5 based game detection. To use this, all you will have to provide is a standard data table of ADGameDescription entries describing each game variant, which is usually placed in a separate detection_tables.h header.<br> | |||
Finally, in either case, you will then have to specify your MetaEngine class to the REGISTER_PLUGIN_* macros. | |||
=== Subclassing Engine === | === Subclassing Engine === | ||