By abstracting most properties and calculations away from the underlying library, the developer should be able to press a key in game and go into the developer mode.
Developer mode will feel much like an integrated editor in a fully-fledged game engine. This might pave the road to an actual editor some time in the future.
This mode should allow developers to:
Freely fly around with a virtual "developer" camera, controlling it with WASD / touch
Have the game continue to run as if nothing happened, but view the game through the virtual "developer" camera / block input events
See a node tree, being able to click and select / zoom to specific nodes
See node details
See message queue
See performance metrics (FPS, tick time, system times)
Send debug commands to the nodes (open their debug console and input commands that are processed by something like an optional onDebugCommand override)
Send input events or enable specific input interactions temporarily
By abstracting most properties and calculations away from the underlying library, the developer should be able to press a key in game and go into the developer mode.
Developer mode will feel much like an integrated editor in a fully-fledged game engine. This might pave the road to an actual editor some time in the future.
This mode should allow developers to:
onDebugCommandoverride)