Plugin Package
Runtime supports a plugin-based architecture combined with automatic downloading driven by a configuration file (manifest.json). This is the key architectural design that enables Runtime to support multiple engines, multiple platforms, and dynamic loading. It delivers on-demand loading and keeps package size to a minimum.
Plugin-based: each engine / module is an independent plugin that can be loaded dynamically.
Configuration-driven: a game package declares which plugins it needs through its manifest configuration file.
Automatic download: when Runtime starts a game, it parses the manifest configuration file, compares it against the plugins already available locally, and automatically downloads and loads any missing plugins from the remote server.
Supported Engine Plugins
COCOS
Unity
LayaAir/Egret
