IndieDoroid wroteIs there a reason it's not part of the default runtime scripts? 🙂
The main border between example components and default runtime components is that you could use the existing runtime API yourself to achive the same goal as the example component, and that it's not necessarily the only, best or most flexible way to achive this goal. In other words, the example components provide a good solution for most cases but you might find a combination of components where they both work well in isolation, but not in combination. One example would be material management, e.g. each component holding references to two switchable materials. The required solution would need to switch between 2*2 materials and thus either know about the other component, or perform additional queries and tests at runtime, adding lots of unnecessary complexity or overhead.
So in short: When the perfect solution is unnecessary complex, we still want to supply you with a solution that covers 95% of the use cases as an example component. At these example components you should feel free to modify them according to your needs.
IndieDoroid wrote
Everything works great for the most part. But I seem to have a weird bug where I can't control the "ghostingEnabled" bool via argument.
public void Ghost(bool _ghostEnable)
Does not work for me
Which method do you mean, I see no public method of this name?
Apart from that, you should be able to directly change the public bool SkeletonGhost.ghostingEnabled here. An alternative would be to disable the SkeletonGhost component, it also leads to the same end result.
