Construct 3 suggestions & ideas

Suggest and vote on ideas for Construct 3! Please note this is only one aspect of planning. We do not guarantee any features here will be implemented, even if they are top-voted ideas. The aim is just to collect feedback. Remember to search for existing submissions before adding an idea, describe your ideas as comprehensively as possible, and vote for plausible ideas that are well thought out. Please see our full guidelines on suggesting features.

Admin Response

This is a good idea and we'll probably make an official behavior later down the line. However we'd like to focus on completing the Construct 3 runtime first. In the mean time we will work on the SDK and help third-party developers port their addons to C3.

Tweening / easing or whatever we will call it would be the best built in the editor itself. So you could tween everything. For example you can't tween easily "scrollX" you have to create an object add tween behavior to it and then patch that tweening into a "scrollX" value. But what if you could to it in events? something like ScrollX set to tween(start, end, duration, tween type....etc)

The current LiteTween behavior is very good. If Lunnaray is willing to build a C3 version I'd say this is a low priority. I do feel that tweens are very much a must in game development. There's only so much you can do with lerp.

This is a fair request for a useful behavior. Of course it can be done with events - all of Constructs behaviors can be remade with events. It is something that is commonly needed though: moving an object from point a to point b over a certain duration of time.

The structure can be similar to the pathfinding behavior without the pathfinding.

The lack of tweening was something that irritated me when I first tried out C2. Both other engines that I use have built in tweening with a few/lot of these easing variants http://easings.net and I'm constantly using that. E.g. for moving Ui elements fluidly or to tween the score variable up to make it more interesting than just increasing it. There are tons of things that I need easing for in my games.

4. A key frame can contain sprite properties (e.g. position or opacity of sprite)

5. A timeline have action like: Play, Pause, Rewind, Goto(seconds) and so on.

6. When a timeline is playing it will change the properties of all attached sprites, according to key-frames value. It will calculate values between key-frames according to an easing (http://easings.net/en).