public enum FoliageStorageWhether a type's instances are stored or derived.
Remarks
[docs/plan/31 § D8], and it is the design decision most likely to be got wrong from a feature list. The dividing line is density × identity: something you would place ten thousand of and never name individually is derived; something you would place a hundred of and might name is stored.
⚠ The tools differ accordingly, and that is the point of the flag. The grass tools change a rule — which layer, how dense, what mesh — and the foliage tools change instances. A type that got this wrong would offer an artist a gizmo on something that is regenerated every time a cell enters range.
Fields and properties (2)
StoredPlaced instances, saved beside the scene. They have identity: moved, deleted, found again tomorrow, and a quest marker can be attached to one.
DerivedScattered from a rule and never persisted. Nothing about a blade of grass is in any file.
Used by (10)
- FoliageCollisionVixen.Foliage
- FoliageCollisionTestsVixen.Foliage.Tests
- FoliageStoreVixen.Foliage
- FoliageTypeVixen.Foliage
- GrassCostsNothingTestsVixen.Foliage.Tests
- GrassTypeVixen.Foliage
- TypeRegistrationVixen.Foliage
- Vixen_Foliage_FoliageTypeSerializerVixen.Foliage
- TerrainModuleVixen.Editor.Terrain
- TerrainSessionTestsVixen.Editor.App.Tests