1. You are able to use the [RequiredField] attribute above BBParameters or even normal fields. When this is done, the value will be checked and if it’s null it will throw an error in runtime and halt the task. Furthermore, you are able in your custom tasks to override the ‘virtual protected string OnInit()’ method. This is called only once in initialization, thus you can do your checks there and return a string with the error if there is one, or return null if everything is fine.
2. Right now there is no such feature, but I can take a look at this and see if it’s possible to somehow implement in the future 🙂
3. Parameter changes should be handled correctly, but the renaming of the method itself will lose the “reference” to that method since because it’s done through reflection the only thing that CAN be referenced is it’s name. So, it’s simply not possible to somehow “relink” the script control task to point at the now renamed method, thus the only way would be to go into the tasks that show in red (as for missing method) and replace it with another one-by-one. I really wish there was a way to avoid this and if you have some suggestion by all means do let me know..
Thanks!
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.