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
location_volume_auhoring

location_volumes
2: setup some volume sets for your subscenes
volume_sets
3: add a relevant authoring script to some gameObject (it will follow the MainCamera).
relevantAuthoring
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).
ZoneContainer
5: Import the AdditiveLoading prefab in your scene from the samples
system-prefab

Samples
6: setup your & organize scriptable objects:
scriptable_objects

so_scenarios

so_zone

so_region

region_data
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)
sapwn_points
------------------------------------------------------------------------------------------------------ Collisions on props (guide for 3D artists): Why this is needed: When a prop is placed inside a SUBSCENE, Unity converts it to entities and DELETES its collider components. The mesh still renders, but the player walks straight through it. Chairs, tables, crates — anything solid — needs the step below or it will not be solid in game. (Props placed in a normal additively-loaded scene are unaffected: their colliders already work, and following this guide there does no harm.) How to make a prop solid: 1: Add your collider(s) to the prop prefab as usual. Supported: Box Collider, Sphere Collider, Capsule Collider. Use as many as you need. NOT supported: Mesh Collider — it will be ignored and the prop stays non-solid. Approximate the shape with boxes/capsules instead. 2: Add the "Static Collider Authoring" component to the prop prefab. It can go on ANY object in the prefab — root or a child, it does not matter. Leave "Include Children" ON so it picks up colliders anywhere under it. 3: Put the colliders on a layer that collides with the Player layer (Project Settings > Physics > Layer Collision Matrix). A collider on a layer that collides with nothing will spawn correctly and still block nobody. 4: Save the prefab. Moving, rotating or scaling the prop later needs NO extra work — the collision follows the prop automatically. There is no separate invisible collider object to maintain. How to check your work: - Run "Tools > SceneManagement > Validate Static Colliders". It scans every prefab and reports props with no usable collider, unsupported Mesh Colliders, and unusable layers. - Warnings also appear in the Console when a subscene is baked. One-time setup (programmer, once per project): - A "Static Collider Bridge" component must exist on an always-loaded object in the main scene. Without it NO baked prop is solid, no matter how well the prefabs are set up. Entering play mode logs a warning if it is missing. Good to know: - Only props near the player get real colliders (default: within 30 m, up to 128 props at once). Both values are adjustable on the Static Collider Bridge if a dense room needs more. - Trigger colliders are skipped by default — this system is for blocking the player. ------------------------------------------------------------------------------------------------------ Acknowledgment: - Inspired by EntityComponentSystemSamples project https://github.com/Unity-Technologies/EntityComponentSystemSamples - Thanks to CodeMonkey for his advices. [https://github.com/Unity-Technologies/EntityComponentSystemSamples](https://unitycodemonkey.com/) ------------------------------------------------------------------------------------------------------ Compatibility: - URP - HDRP - Unity 6000.0.24f1 and above. ------------------------------------------------------------------------------------------------------ How to install the package: - add new scopedRegisteries in ProjectSettings/Package manager - name: jeanf - url: https://registry.npmjs.com - scope fr.jeanf ------------------------------------------------------------------------------------------------------ Depedencies: - Make sure to install UniTask as well: https://github.com/Cysharp/UniTask?tab=readme-ov-file#install-via-git-url ------------------------------------------------------------------------------------------------------ LICENCE: