Known issues and limits
What doesn't exist yet, what hasn't been tested and the known limits of the editor and the runtime in version 0.1.0.
This page lists, plainly, what version 0.1.0 doesn’t do or hasn’t proven yet.
Doesn’t exist yet
- A debugger with breakpoints.
- Prefabs.
- Rigid body physics (pymunk). Collision today is box based.
- 2D particles and lights.
- Live inspection of the object tree while the game runs.
- Plugins and a profiler.
- Browser export on phones, and mobile export.
See the roadmap for what is planned, with no dates.
Not tested
- Windows, Linux and Intel Mac. The installers were built but have never been run on those systems. Only Apple Silicon macOS went through the full test.
- A real gamepad. The input map accepts gamepads, but tests used simulated events.
- Audible sound. Tests used a dummy audio driver.
- Two monitors. Detaching a panel window onto another monitor hasn’t been re-checked.
- Automatic updates. They have never run against a published release. On macOS they only install if the app is signed, and the app isn’t yet.
Unsigned installers
macOS and Windows show a warning the first time you open the app. The download page explains how to open it anyway.
Runtime limits
- Rotation is ignored by collision and by TileMap.
- There is no rigid body physics.
- The input map’s
axis()is digital: it gives -1, 0 or +1, with no analog in-between values. - Hot reload reloads the whole script module (module-level globals start over) and doesn’t reload modules imported by it.
Export
- The program is only built for the system the editor is running on.
- Browser export is experimental, needs internet to build and to play, and audio and gamepad in it haven’t been tested.
Editor polish still missing
- A visual 9-slice editor and several UI resolutions at once.
- An animation state machine, autotile and multiple layers in one TileMap.
- Choosing a custom icon in the export dialog is available for every system, but only macOS was verified.