v0.106.0 Plays Your Levels

A level a player downloads can live with the player's own files and load from there. A browser game keeps its mouse when it lets go of the pointer, a picture taken with camera.capture has the scene's real sky, and an exported game no longer carries the editor tools that came with its packages.

Levels from the player's files

scene.load now loads a scene saved under user://, the player's own files:

assets.writeBytes("user://stages/" .. id .. ".ron", sceneBytes)
assets.writeBytes("user://maps/" .. id .. ".map.ron", mapBytes)
scene.load("user://stages/" .. id)

{ additive = true } works the same way. The scene's models, materials and scripts still come from the game. Its map is read from user://maps/, laid out the way a project lays out its own maps/ folder, so a downloaded arena never picks up the map of the game's own arena. Community levels no longer have to be written into the game's install folder, which an installed game may not be allowed to write and which the next version replaces.

In a session, a server that loads a user:// scene names it to every client, and each client loads its own copy. Send the scene to each player first with net.send and have them save it to the same path. A client that does not have it says which scene it could not find.

The mouse keeps working in a browser after the game lets go

In a browser build, a game that released the pointer (input.unlockMouse(), or opening a menu) was treated as if the player had pressed Escape. Every mouse button, the wheel and mouse movement then stopped reaching the game until the player left-clicked. A hold-the-right-button camera worked once and then went dead. Now only the player's own Escape takes the pointer back, and any mouse button, not just the left one, gives it to the game again.

Captures have the scene's sky

A picture taken with camera.capture early in a game, or during floptle shot --after, showed the skybox's plain base colour where the sky shader should be, and without the fog that reaches into the sky. A capture now draws the same sky the game shows.

Editor tools stay out of your builds

• An export leaves out each package's editor folders. A package that is only an editor tool is left out of the build altogether, and the export report names it.
• floptle run and floptle shot load packages the way an exported game does, so a package's editor tools no longer run there and stop asking for permissions in a headless test.
• The warning about references that point outside the project only counts strings that name a kind of file the engine loads, and says which file each was found in. An HTTP route or a field name in a request body is no longer reported as a missing file.

Upgrading

Export your game again to leave editor tools out of the build and to get the browser mouse fix.