Technique:Identifying HTML5 game engines
Appearance
| On this wiki | Facts · Code · Notes · Topics |
|---|
How to tell which engine an HTML5 or NW.js game uses from file names and strings: RPG Maker MV (rpg_*.js), GDevelop (gdjs.projectData), PixiJS, Phaser, PlayCanvas, Construct.
Games built on web tech ship as JavaScript plus assets, sometimes in a desktop shell (Library:NW.js, Library:Electron). A first pass:
| Engine | Tell-tale | Source |
|---|---|---|
| Library:RPG Maker MV | js/rpg_core.js, rpg_managers.js, rpg_objects.js, rpg_scenes.js, rpg_sprites.js, rpg_windows.js, plugins.js, main.js; data/System.json; Utils.RPGMAKER_NAME = 'MV' | corescript |
| Library:GDevelop | gdjs.projectData, gdjs.runtimeGameOptions, code0.js | GDevelop repo |
| Library:Phaser | global Phaser, Phaser.VERSION, new Phaser.Game( | phaser repo |
| Library:PixiJS | www.pixijs.com banner | pixijs repo |
| Library:PlayCanvas | build/playcanvas.js, namespace pc | engine repo |
| Library:Construct | c2runtime.js/data.js or c3runtime.js/data.json | unverified |
Steps: (1) check the shell: package.json plus nw.exe or package.nw means NW.js, resources/app.asar means Electron. (2) List the JS files and grep for the strings above. (3) Read version strings: they decide which public source to compare against. (4) Game data is usually plain JSON (RPG Maker data/*.json, GDevelop data.js); only assets may be obfuscated. See Technique:Reversing bundled JavaScript for bundlers and minified code.