I think C2 is great, but I would like to know how the real pros transfer their favorate set of functions from one project to another? How do the real pros get around pinning different objects in a family-like way as the op is asking. Just when do you have to "wait 0"?
ctrl+c and ctrl+v? as long as you have the same variables and objects C2 will be able to copy from a project to another the event sheets just by copy pasting... or you can do the harder way where you can import the entire project intro another project by importing the xml files i think ..i read that long time ago.. however i never needed it... since doing that wold create problems you might forget the functions how they are linked and so on.
as for the wait 0 ... what that means is that the 2nd action on a condition will only be executed after the first is completed... for example
condition"when something"
--- > action 1 do this
--- > wait 0
--- > action 2 do this other thing
that means as above after action 1 is executed only then the action 2 will happen..
that is useful when you want to delete a sprite then create another of the same type... or when you have multiple actions on the same condition and the system might skip or write a bad value or half of a value instead the real one.
C2 event sheet is read from top to bottom... but sometimes it might skip 1 action or 2 depending on the Delta-Time and Frame independence why im bringing that in?
because that is how C2 performance is measured... it cannot run faster then the current dt or the formula (60*dt) which should be equal to 1 that is 1 frame per tick which equals with 60 frames per second.
but that doesn't always equals to 1 because of the platform you run the C2 system ...
if your system is a bit outdated and has a 0.01 delay on performing some action then dt will skip or fail 1% of the time.
thats why you see problems like fast objects passing trough solid objects or physics failing...
however all this issues bringed on this topic can all be avoided just by reading the manual and test and retest until you get it the way you want it to.
no game engine or software will perform perfect, no matter if its a 10,000 dollar software piece or 1 dollar. it will always have some problems.
its a matter of understanding how you can work around those problems that makes the software usable.. and with C2 you can work around a lot of issues. but as we progress in future... since in past we cant... more plugins/behaviors/effects are developed to increase the power and usability of C2 and limit the problems some faces.
However none of the problems that are mentioned in this topic are not solvable... are actually the most easy things to do in C2 no extra special plugin or power needed just the default C2.
Its a matter of learning a bit C2 and trying to understand how C2 works thats all.