I’m developing a map data system that generates grass/water graphics automatically for nearby objects. I’m working on studio tools and it’s really frustrating for the dynamic visualization to be affected by undo/redo. It also adds extra data to my save file. It’s important to be able to visualize grass decoration and water while developing the world in studio and this behavior seems like a reasonable change.
I would expect setting Terrain.Archivable to false would make it not interact with undo, as well as not serialize its properties when saving. Right now it’s just locked.
Also I’m not entirely sure if this is the case, but I don’t think non-Archivable instances should replicate in team create either. The replication from terrain changes (or other plugin-instances) would get out of hand.
An alternative for my use-case would be to introduce axis-aligned water parts, or grass/shader decoration surfaces.