I wouldn't worry about performance so much. You can use the free version of the engine and check out some example projects, including stress tests.

As far as what kind of games can be made with construct, the answer is pretty much any 2d game you can think up.

To master the engine is much like mastering any other tool, and that is simply using it, reading the manual, and learning from others in the community.

Learning JS would also be useful.

I love the fact that there is a monthly option now. And of course it's going to be more expensive than subscribing for an entire year. That's not a new concept.

Construct 3's subscription model gets a lot of flak, but I'm more than happy to pay it. It's affordable and it enables Scirra to maintain and add features to the engine. Plus... Scirra doesn't take any of your game's profit.

My pleasure

construct3.ideas.aha.io

This is where you can suggest any idea for construct, including SDK additions.

Ah okay. If I'm understanding correctly, what you want is to load and build sprite animations at runtime.

The addon SDK only appears to support building animations at edit time.

There is a way to do this with the behavior settings.

Instead of using the default pathfinding obstacles (All Solids), you can specify which objects are obstacles using the Custom option.

You then have to specify which objects are obstacles in the Pathfinding -> Add Obstacle action.

Ashley

Never mind about the suggestions & ideas response. Was looking on there and does in fact seem the place to ask for SDK enhancements.

What workflow gain is there from loading an image via URL, as opposed to loading the file from your pc?

You'll have to combine events and scripting. You cannot access addon sdk properties, expressions, etc... from scripting.

What you can do is create 2 local variables in your event/group.

Set those variables using events. You can use events to access your plugins expressions.

Then access those properties through localVars in your script.

Okay. There is a part in the ACEs documentation that mentions object picking as if it was intended on being a public API at some point.

ACEs - isStatic

Might want to update the verbiage on that.

There's another way that I can go about writing this addon, but not nearly as intuitive.

If addon devs need more object and methods available, how to we go about getting that on Scirras backlog? It seems overly complex to request documentation in suggestions & ideas.