That would be a good alternative, though I’d say I found myself in cases where the level designer would very much like to play with groups/models in editor.
The pipeline usually is:
- A list of disabled “template” entities with batch group IDs defined on their model component
- On runtime those entities are cloned and procedurally placed in the level.
- As soon as any of these cloned instances is enabled the batcher automatically kicks in.
Here it would be very helpful to have a manual mode for the batcher, have it run manually [this.app.batcher.generate()] after everything is positioned and enabled and not when just a single entity with a batch group is enabled.
Agreed, it can work if everything is done in code (batch group creation and assignment) but that means script components and attributes, which adds an overhead.