flutter3d_screens #

The screens a game has that are not the game: settings, volumes, rebinding, credits, and where a save goes on each platform.

SettingsOverlay(
  settings: settingsCubit,
  mixer: audio.mixer,
  bindings: devices.bindings,
  config: config,
  padConnected: pad.isConnected,
  actions: myRebindableActions,
  defaultBindings: myKeys,
  opening: letGoOfTheGame,
)

Extracted when the second game wanted it, and what triggered it was accessibility: rebinding a control is the accommodation that matters most, one game had grown a panel for it, and the alternative was four hundred lines copied into the next one.

What is deliberately not here is anything a particular game says. The credits are a widget the caller hands in, the list of rebindable actions is the caller's, and the panel has never known what a coin or a monster is.

Storage #

A save and a settings document are two small JSON files, kept where each platform keeps such things — and on two of the four platforms the first version was silently losing them, which looks exactly like a player who changed no settings. Storage is where that is now decided once, per platform, in the open.

Part of flutter3d, an independent implementation of a 3D engine for Flutter — not a fork or a binding of another engine, and not affiliated with the Flutter team. Three switchable rendering backends: Impeller via Flutter GPU, WebGL2, and a software rasteriser. glTF, OBJ and .f3d loading, six lighting models, shadows, bloom, skinning, animation, BVH culling and picking; a deterministic fixed-step game layer with collision, navigation, positional audio, and gamepad and touch input. Three example games — shooter, platformer, racing — each built on its genre package: flutter3d_game_shooter, flutter3d_game_platformer, flutter3d_game_racing. A new game starts from the editor's scaffold, which writes one from a template: https://flutter3d.pleion.dev/first-project/. Documentation: https://flutter3d.pleion.dev.