C2 is great as-is but here are two main things I'm missing that I'd love to see in C3: Better asset/object management and more control over project settings in general.
Better asset/object management:
I'm sure some of these have been asked for before by others but I'll mention them again just in case. On deleting objects or variables, have an option to keep the events associated with them with some kind of placeholder object. Ability to duplicate objects/sprites so we don't have to build similar objects from scratch. And PLEASE allow us to manipulate sprite atlases from within the editor; it's absolute hell to tweak sprite frames one-by-one when you have a lot of them and batch-processing external images doesn't cut it in some cases, like doing palette tweaks (AFAIK).
Allow users to set things like sprite atlas resolution themselves, control is always nice! Also, some things can only be controlled from the editor project settings right now, like point/linear sampling and WebGL on/off. It would be great if we could toggle these from the runtime to allow settings to be saved to and loaded from an external config file on runtime startup instead of needing separate builds(!) for different settings.
[quote:2mprls82]The idea here being that C2 files can be opened in C3 (possibly with a once-off conversion or the like), which would encourage existing users to migrate to C3 when the time is right for them
[quote:2mprls82]I totally agree. C2 is still have field to improve. It's a great (and probably necessary) step from Scirra to start planning C3, but don't just hype it yet.
I agree too but the question is, with the way C2 works under the hood, how many new features can be included? Ashley has already mentioned that some things aren't easily doable without a major re-write, like modularity.