One thing that I would LOVE to see in more tutorials is "behind the scenes" of how all the events and actions work in C2.
For instance, I originally thought that "For Each" worked on iteration every TICK. So, for a For Each (1, 10), it would take ten ticks for it to complete, one tick per iteration. I later learned this wasn't true...rather, it would simply work "instantly", often running multiple iterations in a single tick.
Had I had that understanding sooner - LOL - I probably could have saved myself a whole lot of troubles when I was first starting out. But it's hard to ask these questions about the various events and actions because I DON'T see what's going on behind the scenes. I don't see HOW the computer/editor is thinking and how it interprets its instructions compared to my understanding. Without being able to observe the differences between interpretations - mine versus the computer - I don't know what questions to ask to gain that understanding that I would OTHERWISE obviously need.
Does that makes sense?
A fellow C2izen recently helped me with a post I made earlier today regarding an infinite runner I'm trying to make. My error was simple enough once he pointed out to me. But it's those other things that even the debugger doesn't list that makes it hard to know what I'm doing wrong. On one hand, the Event sheet line seems to be in place! LOL But I'm still stumped because what I want to happen isn't working, and I don't know where to look after I've tried everything that comes to mind.
I guess what I would just love to see is an intimate breakdown of how an event or an action "thinks" when it's put into motion. What are their parameters? When do other events/actions need to be added, removed, rearranged? When do those parameters start and stop? THAT is what I'd love to learn.