personally i not see sca so cool .
more over what i hate of it is that in ALL CASES are really “BLOKED” !!
for other 500 years sca still what is now!
at the same time i tried to make some visual node on the paper, and … seem all except easy, more over, increase the complexity a lot in the moment that you manage different output from a “bolean”.
(how and when an imput should be counted as trigger? of the other node…)
something of sca is to keep anyway, for example some kind of sensors have to run only once and in all case, (not “on call” that risk to be confusing and absolutely not performant)
i guess the tread suggest more over organization.
each script can be a property of the object rather than “used” from an object.
this mean that each object has a list of scripts (exactly as the list of bricks)
to find a script of that object you have to select the object, not select the right script in the HUGE(dirty) list of global scripts.
this concept will be extremely useful for each thing that a object use,
changing from “user that add mess in the global list” from the OWNER.
tremendly useful for:
material
mesh
textures
images
animations
sounds
that isa a problem of BLENDER , hugly organization , not object oriented.
should be 2 path explicitely and clearly separated-> GLOBAL(stuff of blend), LOCAL(stuff of the OBJECT ONLY)
the data saved as local should be completely unaccessible for other object.
for the code, shopuld be the same except for the fact that python is not an internal language of bge .
so, is better limitate the amount of code .
for all other stuff , have this very normal ability of save data as property of the object should be very normal.
this avoid a lot of work useless, conflict with names completely useless , UI much more clean,
and maybe(due to the UI much more better organized) the ability to make a game normal (not AAA) in a single blend.
without miracles of ingegnery.