create-eigen-game 0.7.1 → 0.7.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-eigen-game",
-  "version": "0.7.1",
+  "version": "0.7.3",
   "license": "MIT",
   "description": "Scaffold an EigenInteractive game Worker and Flutter app without cloning the engine repositories.",
   "type": "module",
@@ -25,9 +25,9 @@
     "vitest": "^4.1.10",
     "wrangler": "^4.110.0",
     "zod": "^4.4.3",
-    "@eigeninteractive/server": "0.2.2",
-    "@eigeninteractive/rules": "0.2.2",
-    "@eigeninteractive/testkit": "0.2.2"
+    "@eigeninteractive/rules": "0.2.4",
+    "@eigeninteractive/server": "0.2.4",
+    "@eigeninteractive/testkit": "0.2.4"
   },
   "engines": {
     "node": ">=22"

package/templates/app-overlay/lib/main.dart.template

@@ -1,7 +1,6 @@
 import 'package:eigen_flutter/eigen_flutter.dart';
 import 'package:firebase_core/firebase_core.dart';
 import 'package:firebase_messaging/firebase_messaging.dart';
-import 'package:flutter/material.dart';
 
 import 'firebase_options.dart';
 import 'game/module.dart';
@@ -15,9 +14,15 @@ Future<void> main() async {
   await runEngineApp(
     module: const ExampleGameModule(),
     config: AppConfig(
+      // `seedColor` is left at its default, the EigenInteractive teal that the
+      // placeholder icon and the worker's own pages are drawn in. To make the
+      // app yours, import 'package:flutter/material.dart' and add
+      // `seedColor: Colors.deepPurple` (or any Color) — Material 3 rebuilds the
+      // whole light and dark scheme from it. Do it alongside the launcher-icon
+      // and splash colours in pubspec.yaml, which cannot read Dart:
+      // https://eigeninteractive.com/docs/ship-it/branding
       branding: const Branding(
         appName: 'Example Game',
-        seedColor: Colors.indigo,
       ),
       engine: EngineConfig(
         apiBaseUrl: _apiBaseUrl,

package/templates/project/README.md

@@ -99,6 +99,16 @@ Then `firebase login`. Nothing before this point needs either tool — rules,
 fixtures and `wrangler dev` all run without them — but the app itself throws
 `Firebase is not configured` on launch until this has run once.
 
+The first run asks which Firebase project to use, and can create one. Name it
+up front to skip the prompts, which is also how CI runs this:
+
+```sh
+{{PACKAGE_MANAGER}} run firebase:configure -- --project my-project-id
+```
+
+Later runs reuse the project recorded in `app/firebase.json`, so there is
+nothing to pass again. Add `--help` for the rest.
+
 The command uses FlutterFire's selected Web app to generate both
 `lib/firebase_options.dart` and `web/firebase-config.js`; do not copy Firebase
 identifiers by hand. Put the public VAPID key in `app-config.json` separately —

package/templates/worker/src/index.ts

@@ -14,4 +14,23 @@ export default createEngine({
   appName: "Example Game",
   d1: (env: Env) => env.GAME_DB,
   gameDO: (env: Env) => env.GAME_DO,
+
+  // Uncomment to turn on the game's public website: the download page grows a
+  // tagline, screenshots and structured data, and /terms, /privacy and
+  // /delete-account start serving the engine's default documents with your
+  // details in them. The app stores require all three, so this is not optional
+  // for long — but read what they say before you publish, because you are the
+  // one on the hook for it. https://eigeninteractive.com/docs/ship-it/branding
+  //
+  // site: {
+  //   tagline: "Race an opponent to the target.",
+  //   primaryColor: "#006a60",
+  //   screenshots: ["1.png", "2.png"], // under public/screenshots/
+  //   operator: {
+  //     name: "Your Company Ltd",
+  //     jurisdiction: "India",
+  //     contactEmail: "hello@example.com",
+  //     effectiveDate: "1 July 2026",
+  //   },
+  // },
 });