> 
XHXIAIEIN Tips like this are super valuable. I think people really need something like a Construct Cookbook or CheatSheet that shows the best practices for doing things the right way.
Maybe this is something the community would be good at putting together rather than Scirra?
Since the community are the ones trying to squeeze out the performance in real projects, whereas Scirra is just making the tool and is probably not use to the same challenges that we are use to facing.
Yeah that's kinda the point also I wanted to mention is that Scirra perspective is probably pretty different, as creators of C3, from the people who are actually using C3 as a tool everyday in real life projects. And what I often felt while reading the forum is that Ashley just doesn't have a same perspective as people talking with him, and that's why there is often a lot of misunderstanding. And like, boths sides are right but in their respective realms
And that's why maybe like you said there should be a community effort, but in cooperation with C3 devs, to make a, yeah, some kind of Cookbook with best practices and maybe additional insights on how things work internally from the devs that will help to actually understand stuff on a deeper level and use it more effectievly
There was a similar thing my friend done (its in russian though), with some insights he managed to dig from a lot of testing and digging the internals. Though he made a ton of bug reports from it and a lot of things might be fixed/changed already, but you get the point
We talked a lot about such stuff and yea, there is a lot of things. Yes, all this probably doesn't matter for most projects, but it does matter a lot for people who actually make something cool and big (not saying its me, but I've seen many other people like this). I think it very much worth it to consider them, because they are much more likely to make things that you will say "wow it was done in C3??? so cool!" about :)