@mikeviolette
Ok, spaghetti, being the criteria makes more sense, than just “clean and commented”. Still is there going to be exceptions for crossed wires for nodes, concerning a failed cast, or the usage of datatables? OR, will placing those nodes inside of Macros, such that the Success and Failure exec pins can be moved around (Success staying at the top of the node, and Failure going to the bottom, with the output pin being in the middle), thus allowing access to the output pin the Success exec pin, without crossing the wire from the Failure Exec pin? Casts and Datatables both have this set up for the exec and output pins. I don’t wish to waste time on this, after submission, much prefer to know up front and just do it that way and be done with this. The idea of having to resubmit, etc. is not one I relish. If Casts and Datatables are exceptions to the “no wires being crossed”, that’s fine, so long as macros can be used to work around it.
As to “Static” and “Pluginname” prefix: are those required to be in the macro name as well. I.e. all my macros out of a macro library and function library are prefixed with “IW - XXXXXXXx”, as well as using a Green color for the “titlebar of the node”. Is something like this acceptable?
I won’t argue about “event1” being a “good/bad” naming convention (in that if dealing with a large enough Finite state machine, just numbering very well may be the best way to go, assuming the state machine has 50+ states)
Thank you for your time,