Yes, certain things like SSF and other events could be an automatic function of a component that shouldn't need any scripting (similar to how some things in FP didn't need to be scripted compared to VP, etc).
Having as many things handled this way as possible in the GUI is a GREAT thing. However, it's also very important to have options for complete control or have the equivalent of a "Hit", "UnHit", changes in RGB lighting values, light "states" (on, off, blink) etc that can be used in the table script for additional control or features,etc. "Options" are always best for future proofing.
While I'm not completely familiar with Unity's lighting engine / limitations, etc... working with a real mesh / model for inserts would be ideal wherever possible (as has been done by the likes of flupper, bord, G5K,etc) and using a "real" light (that affects everything, not just the ball like in VPX). I know most everyone in the VPX community is used to mostly static lighting (and I'm now used to FP-BAM's newer lighting), but Unity should change almost every aspect of table design and lighting choices.
The future is looking bright...and it benefits from all the hard work of devs in the past and present of VP, FP, BAM and now the current VPE devs and testers. We can't thank you guys enough.
Edited by TerryRed, 02 August 2020 - 08:52 PM.