In short, when running on NodeJS, Phaser starts the system scene and the first scene set in global config before initialising any of the plugins specified in the game config. This seems to be caused by the texture manager finishing unexpectedly early and starting the main game loop, before the game's boot event is even fired - the plugin manager is listening on that for booting.
Any idea how to debug this? I find Phaser's boot sequence events rather confusing.
Description
This is a duplicate of https://github.com/geckosio/phaser-on-nodejs/issues/13, but I'm hoping that somebody on this project might have some hints on the problem.
In short, when running on NodeJS, Phaser starts the system scene and the first scene set in global config before initialising any of the plugins specified in the game config. This seems to be caused by the texture manager finishing unexpectedly early and starting the main game loop, before the game's boot event is even fired - the plugin manager is listening on that for booting.
Any idea how to debug this? I find Phaser's boot sequence events rather confusing.