When to use 'ES3 Reference Manager', and when is not.
Posted: Fri Oct 15, 2021 4:05 am
Hi.
We are using ES3 for developing our top-down 2D RPG.
I would like to have some questions about "ES3 Reference Manager" when saving GameObjects(or prefabs)
Background
- Loads many scenes as additive mode
- Want to save GameObjects in scenes like NPC, Spawned Props.
Problem
- Seems like 'ES3 Reference Manager' is collect references of only one scenes that Manager is actually in.
- Seems like Reference manager collects literally whole references in the scene. But I only need few GameObjects.
Question
- Using ES3 Reference Manager is really a best solution for save GameObject or Prefab instances?
I think It could be better if I create my own manager to save the GameObjects that I need, in multiple scenes.
We are using ES3 for developing our top-down 2D RPG.
I would like to have some questions about "ES3 Reference Manager" when saving GameObjects(or prefabs)
Background
- Loads many scenes as additive mode
- Want to save GameObjects in scenes like NPC, Spawned Props.
Problem
- Seems like 'ES3 Reference Manager' is collect references of only one scenes that Manager is actually in.
- Seems like Reference manager collects literally whole references in the scene. But I only need few GameObjects.
Question
- Using ES3 Reference Manager is really a best solution for save GameObject or Prefab instances?
I think It could be better if I create my own manager to save the GameObjects that I need, in multiple scenes.