Fr.jeanf.scenemanagement NPM

Scene Management

The main goal of this system is to be able to start the game from anywhere in the world and be able to load all the required visuals & scene logic you might have in this world. All the static meshes are stored in subscenes leveraging the Entitty Component System to load the world as fast as possible. This part of the system uses "Volumes" & "relevant" entities do decide which volume-set to load (containing references to a bunch of scenes related to that set). By checking the position of the relevant entities, we can then define which volumes are to be loaded.

In parallel I also build a Additive-Loading system that loads content depending on the region or zone (using colliders to detect the player's position) to be able to use MonoBehavior scripts without having to recode the whole codebase. Each region or scenario can have dependency that will remain loaded until either a region or a scenario became irrelevant. The additive system loads scene additively depending on zone & region and upon scenario load/unload requests.

Key elements:

Loading scenes additively
Concept of Region & Zones
Concept of Scenario
Loading scene dynamically depending on position

How to use: 1: setup some volumes to load subscenes dynamically 2: setup some volume sets for your subscenes 3: add a relevant authoring script to some gameObject (it will follow the MainCamera). 4: Create and place zones & zoneContainers to detect the player's current position (in the future this step will be removed to as volumes should be enough to retreive this information). 5: Import the AdditiveLoading prefab in your scene from the samples 6: setup your & organize scriptable objects: 7 OPTIONAL: setup your spawn points per region, note that you can create a different initial spawn point, only one region should have the initial spawn point (later will be overriten by last player position when last playing the game)

Acknowledgment: