I have kinda wished for a while there was a way to edit the code of things like the platform behavior per project. Or if we could alter the plugins per project, I could just add collision tags to the jump-thru instead of having waited I think 3 years now.
Yes, this is only possible solution for current case, with official guidelines for it.
Not to mention waiting 3 years. Who in right mind will start to develop something, hoping maybe it gets added in 3 years, even 1 year would be to much in this case.
Baseline C3 plugin is just more complicated than a simple, baseline component for other engines, so it's a bit of an apples/oranges comparison. But the bottom line is there's a lot of friction with getting started writing C3 plugins. Having some built-in software to help manage complexity in C3
I always though their sdk manual is more for themselfs, place they can look up correct code.
Besides, lots of Construct users are not very experienced programmers.
Saying this is pretty much counterproductive to everything. In such case, you won't get it in 10 years or 20. As it goes, if idea is somewhat possible or it simplifies 3 step to 1 or helps a bit with performance, then in MOST cases such idea will never be developed. Only possibility is: you do it or someone else, but currently nobody can, past scirra.
This is the case that makes your 'array noSave' never to come existance. Why would new, passing though or not very experienced devs want it? Only way this benefits someone, if they make or do some sort of community and then force feed ideas to be voted. Overall it still benefits 1-2 guys.
This would also make C3 pretty much a 3-5 month toy. Problems that new users face are voted and developed, while users who been here longer, would never get their specific stuff, because nobody cares. Or when new users does very specific thing and sees engine flaw, noone else would vote for it.
Example: if some old C2 plugins would never been developed by modifing official code, thous plugins or features would not even be in C3. Currently users only demand them, because they saw that case was good. Because based on just idea, nobody or 'passing though devs' would never vote for.
reset of the suggestions platform every 6 months
Suggestion platform also consists 'almost bugged behaviors' ie flaws in C3 that are labeled as ideas. They are not gonna change. This just would remove or hides them.
Over the years, from forum to every other place, if user found or faced massive flaws/shortcoming, then user went to suggestion platform, as place to write them down. Thous flaws n shortcomings are still there. Most cases are even like 'I want to do X' -> Official statement 'do this' -> but 'do this' has massive problems -> post it on suggestion platform -> baam never get it.
In C3 development cycle, the 6 month is very short. A much better idea in such extreme case would be: if idea does not get X votes, it will be removed in 2 weeks. This would least make forum more active with specific topics, on a daily basis.