7,987
edits
Difference between revisions of "HOWTO-Engines"
Jump to navigation
Jump to search
adding information of file names for saves and other files from the discussion on scummvm-devel
(→Steps: Fix the engine inclusion part, now engines/plugins_table.h needs to be adapted instead of base/plugins.cpp, this step looks like it has been removed by accident) |
(adding information of file names for saves and other files from the discussion on scummvm-devel) |
||
| Line 50: | Line 50: | ||
|} | |} | ||
=== Subclassing MetaEngine === | Additionally, the files saved by each engine should be consistent. | ||
* '''Saves''': These should be named <targetid>.### (where ### is the slot id) or <gameid>.###. The latter should be used when the saves can be shared across all game variants. | |||
* '''Other files''': These should be named <targetid>-<filename> or <gameid>-<filename>. Again the latter when the files can be shared acress all variants of the game (an example for these type of files would be when a minigame saves a high score record). | |||
=== Subclassing MetaEngine === | |||
Let's implement the plugin interface:<br> | 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. | 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. | ||