flutter3d_editor_play 1.0.0-rc.2

Outside the 1.0 semver promise. Play from a level editor: the game a level belongs to run with `flutter run --machine`, reloaded, stopped, and handed a saved level.

1.0.0-rc.2

Since the 2026-10-14 upload, the Play panel can be tested. ScriptedPlayedGame is a run a test drives. A run's dispose is close, and the results that were records are final classes, which dart fix and migrate rewrite. The entry below says why this package stays outside the 1.0 promise.

• ScriptedPlayedGame, a run for testing the Play panel. It starts through PlayStarting to PlayRunning, or stops at -1 saying why, answers a hot reload only while running, numbers its events across runs and caps its console as FlutterRun and AttachedRun do.

• Breaking: PlayedGame.dispose, AttachedRun.dispose and FlutterRun.dispose are close. dispose() is synchronous, as Flutter's is, and an end that has to be waited for is Future<void> close(): a Future from dispose was left unawaited by every caller that wrote it in a widget's own dispose. dart fix renames the calls and the overrides.

• The engine's number, outside the 1.0 promise. Its signatures carry types of a package before 1.0 or of one that takes a major a year, so a release of that package may break this API in a minor, and the break is labelled here. SUPPORT.md names the four packages outside the promise; the number says which engine release this one goes with, and every pin the engine writes on it is the engine's own.

• Breaking: results that were records are final classes. callGameExtension, eventsSince and fakeFlutterRun answered or held a record, which can never gain a field. Each answers a final class now, with the record's field names (a positional $1 has a name of its own), == and hashCode. A field read compiles as before; a destructuring pattern names the class, and flutter3d_build:migrate rewrites the $1 reads.

• Breaking: GameEventLog is made by a run, which fills it from the game it attached to.

• FakeGame.posts takes data: and time: by name, so an event can gain a field without a third position.

• PlayState is abstract final rather than sealed, so a phase a later minor adds breaks no switch over it.

• A device id is checked before it reaches flutter run -d. isFlutterDeviceId (new) holds an id to letters, digits, ., _, : and -; FlutterRun.start refuses another, since on Windows flutter runs through cmd.exe, and parseFlutterDevices leaves such an entry out.

• Breaking: GameEventLog.take is record. PlayedGame.stop stays beside dispose: it is a state transition (start may follow), and its doc now says so.

• 1.0.0 is a promise: strict semver from there. This release candidate already keeps it. A patch fixes bugs and breaks nothing, a minor adds, and a break waits for a major. The whole public API is stable, with no experimental exceptions, and is held to the snapshot in api/. A deprecated name stays until the next major and for at least six months, and says what replaces it. CONTRIBUTING.md has the rules, and SUPPORT.md says which releases get fixes and on which platforms.

• **Breaking: PlayedGame can no longer be implemented outside their own library: it is an abstract base mixin class now, so a game or a test mixes it in (with) and its class is final or base. A member added to it in a 1.x release arrives with a body, which an implements could not have taken without breaking somebody.

• The first publication. The 0.8.0 the pubspec carried was a number inside the workspace and never reached pub.dev. The package goes out on the shelf's number, so ^1.0.0 on it resolves against every other flutter3d_* package.

• The events a game posts, beside its console. PlayedGame.events keeps what the game posted with flutter3d_game's postToolEvent — a level loaded, the player died — each a PostedEvent with a sequence number, its kind without the flutter3d. prefix, a time and its data, capped at 2000 like the console. AttachedRun listens to the VM service's Extension stream on the socket it already has; FlutterRun opens one at the address app.debugPort reports, since the daemon carries prints and not posts, and drops it when the game exits. eventsSince reads the list by cursor, with the next cursor, how many the cap dropped unread, and a restart from the first for a cursor past the end.

• FakeGame.posts is the game posting an event, and fakeFlutterRun takes the FakeGame its run finds at the reported address.

• callGameExtension asks a running game for one of its extensions. It finds the isolate that registered it and returns the game's own answer or the reason it refused.

• A save goes to the running game as a patch. pushLevel(base:) sends the patch from base to the saved document when the game has ext.flutter3d.level.patch and the patch is shorter, and the whole document when the game answers that the patch is stale; the answer then carries fellBack, which describeLevelApplied puts at the end of its line. levelPatchArguments builds the parameters.

• AttachedRun plays a game somebody else started, by its VM service address: the console (with what the game printed before the attach, which DDS replays), hot reload and restart through the services the flutter tool registers on the game, and stop as a detach that leaves the game running. It is the only Play a browser has, and the editor's attach button on a desktop uses it too. PlayedGame is what it and FlutterRun both are, so one panel shows either; PlayState moves to src/play_state.dart, and PlayStopped takes a reason for an end with no exit code.

• package:flutter3d_editor_play/attach.dart: everything here that starts no process — AttachedRun, pushLevel, connectVmService, PlayState, Watched — with no dart:io anywhere under it, which a test walks the imports to check.

• connectVmService instead of vmServiceConnectUri, over web_socket_channel, so a level is sent from a browser as well; vmServiceWebSocket reads the http:// address a game prints as well as the ws://…/ws one. pushLevel takes a connect for tests.

• FakeGame and fakeAttachedRun in testing.dart: a VM service with a flutter tool on it, or without one, that a test controls.

• A stop on Windows ends the tool, not only its shell. flutter there starts through cmd.exe, and Process.kill left the Dart process behind it building; a stop before the game has started now runs taskkill /t. FlutterRun takes the kill as a parameter, and treeKillCommand says which command a platform needs.

• Play leaves the editor application. FlutterRun, projectRootFor and pushLevel move here from apps/flutter3d_editor/lib/src/play, with Watched in place of Flutter's ValueNotifier, so the editor's MCP server runs the same Play. FlutterRun.device is settable between runs, and hotSwap/hotRestart return what the tool said.

• flutterDevices lists what flutter run -d can be given, from flutter devices --machine, reading past whatever the tool prints first and leaving out devices it marks unsupported.

• package:flutter3d_editor_play/testing.dart: FakeFlutterTool and fakeFlutterRun, a flutter run --machine a test controls.

Its flutter3d_* dependencies ask for ^1.0.0.