-
Notifications
You must be signed in to change notification settings - Fork 0
Quick Start
Edit > Bootstrap Wizard, modify the settings to your liking, and click Run Setup.
This creates a bootstrap scene wired into your build settings, a default environment already set as both your Default Play Mode Environment and Default Build Environment (see Bootstrap Settings), and an Edit Mode Services list. See Editor Windows for what each of its options does.
The default environment the wizard created doesn't come with a Service List assigned yet. Create one (Assets > Create > Bootstrap > ServiceList) and assign it to the environment's Service List field.
From there, add a service to the list the same way described in Service Lists. See Writing Services if you don't have one to add yet.
That's it. Hit Play from whatever scene you're working in. Bootstrap runs the flow described in Bootstrap Flow: it boots through the bootstrap scene, initializes your service, and drops you back into the scene you were editing.
- Services: how Service Lists work, and how to write and access a service
- Environments: what an environment is, and how one gets chosen for play mode or a build
- Bootstrap Settings: edit mode services, default environments, and the Project/User override system
- Bootstrap Flow: exactly what happens between pressing Play and your game running
-
Source Generation: cutting down boilerplate with
[GenerateSingleton]and[GenerateLogger] - App and AppInstance: the static entry point and the object behind a running session
- Editor Windows: the Bootstrap Wizard, Settings window, main toolbar dropdown, and Status window