zooming out of event sheets
its really often i find myself annoyed having to scroll around looking for things when i could just zoom out and pinpoint something right away, i waste alot of time just moving up and down through large groups that i need open alot. groups are handy but zooming out would be quite nice. (ctrl+wheel)
a rotatepoint"X/Y/Z"(yaw,pitch,roll,originx,originy) system expression, would be nice, to make adding minimal 3d faster computationally and event wise, and also a lot more accessible to users, actually this could probably be easily added right now.
a "expression shorthand" mode, which would make writing expressions faster and easier for experienced users, supplementing things like .angle with .a, .zelevation with .z, sin and cos and tan with s,c,t, making writing pv's consist of putting [bla] or {bla}, or something similar instead of ('bla'), replacing system expressions like angle and distance with AN and D, a whole bunch of things of that sort. Thats a feature id like to see in construct really bad, i always find myself naming sprites things like P or A2, so that i can write them faster and have smaller expressions length wise, extending that to things i use in almost every expression but cant choose like .angle, .zelevation, distance, sin cos etc would really be nice imo, maybe even an option to set these to whatever you wish for any object, so that you can be familiar with your own work environment, and adjust things for any plugin or anything that extends into the expression editor somehow like behaviours, effects, you get the point.
also a setting to enable coloring the contents of different brackets different colours like (10+(agfa)*(blah)*ag) to oraganise expressions and see bracket errors better
ability to add custom system expressions
ability to build "behaviours" which you can save and reuse, using events that can be applied to objects/groups of objects.
ie you make a block of code that uses sprite1 and sprite2 and MOUSEKEYB1 and canvas1 in it, and then you can add that in as an event block, when added in it prompts you which objects to use, and youll need to give it 2 sprites, 1 mouseandkeyboard and 1 canvas for it to work, but they dont have to be sprite1, sprite2, MOUSEKEYB1 or canvas1, they can be whatever object of wtv plugin is required, even extending the ability so that you can use custom plugins in your event block (behaviours, effects etc referenced as being needed on certain plugin objects in the block will also need to be applied to there said partner in the block, if not applied, prompted to add them, aaaand another optional request prompt asking if youd like the settings saved with the original event blocks objects for any and everything to be added/changed to what they were for the original on that object), with some form of commenting and grouping saved into the eventblock file so that you can tip on how its used and if original properties are required, so that people who use it can know what to do.
these event blocks would be saved as some file-type and then you could share them as reusable code for anyone to use here online "mode7.evb" "IK.evb" "platformwithtriplejump.evb" "customspriteparticles.evb" "Spritetext.evb" etc. THIS would make construct and the forums an even more super awesome tool with so much extendability, and speed up work a really big amount for everyone, without necessarily needing to know C++. a new forum for sharing and a database for everyones .evb files could be created, making the community behind construct a driving force in its accessibility and feature set. oh yea, container and family properties would need to be attached as well, pretty much everything would for it to work perfectly, but it'd be so great and really worth the work IMO.
well those are all the good ideas i can think of off the bat at least