Unity prefab software#

I think suggestion of instead forming your properties such that you can apply multipliers already with the existing system is spot on. Should an override add a certain amount over the Prefab's value (addition) or multiply it with a value (multiplication)? How does it work for floats versus integers (not to speak of other types that are not numbers at all)? What should happen if the addition or multiplication takes the value over the allowed range for the property? And if it means it should get clamped or similar, how do we display it all in a sensible way?Īll these considerations really are quite gameplay specific, and even if we made a very complicated system that handles a lot of cases, it would still not cover everything.

Relative overrides could mean many things. I fully understand the need of having laser focus to bring this system to prime time, and the headache of getting these assets serialized and working from version to version, but if its logistically possible to expand this system in the future, this functionality would be incredibly powerful for designers across the board looking to use prefab variants to globally balance their assets against each other.

I only realized I needed this feature after getting the beta and actually making variants, and I believe it's only a matter of time before this idea gets more traction, but here's another vote in this phase of beta. This diminishes one of the primary reason of using prefab variants in the first place. To adjust values globally we would have to go in and adjust them all individually. When i think of a prefab variant, I think of a new unit or power up that is 2x stronger, of 1/2 as fast, not some hard override of 'this unit is 34985.43 speed, and this one is 9098.2 speed' and they will both remain locked in stone. Mind you, it's not a huge percentage of designers that fully understand and utilise these facilities, either.īumping this as this feature just seems like a natural progression for prefab variants.

Unity prefab software#

Programmers can understand Variants because they're about inheritance and model classic OOP hierarchical Class-like thinking.īut they can't articulate what that means to users that aren't programmers, nor how it works, or what it offers.ĭecades of 3ds Max trying to explain the benefits of the Modifier Stack are the best example of this, in design software history.įurther, it seems nobody responsible for articulating Prefab Variants to the unwashed masses has any idea how Smart Objects and Symbols work in other creative software, the only equivalent space from which the discussion can reference something slightly similar and reasonably well known. It's a case of programmers imagining the designers would thank them for surfacing OOP hierarchical 'thinking', without realising designers don't work to stipulated requirements, they're creatives, for whom the entire thing is too rigid and brittle to be much use for anything but completely preconceived and utterly specified production, if Unity were able to teach them what Variants are, and how they work.