— Thanks for the Fake3D example project! It was a really great showcase of what Chowdren can do.

(also it's a really neat idea and I hope you do something with it)

Cryptwalker

Right now, my focus is on Construct 2, since the people I have spoken to haven't migrated to Construct 3 yet. I've heard that semantically, Construct 3 is very close to Construct 2, so it should be possible to make Chowdren work with C3.

ultrafop

To be honest, in almost all cases, I am asked to do complete ports of games. Publishers/developers are usually looking for a quick solution to get their game on another platform, and I can do that with comparatively less time/cost than others.

That also means it's only been necessary to license Chowdren to very few developers. Every game is different, so I feel the cost is something that can be discussed on a project-to-project basis.

In terms of features, it's difficult to show you what's working/not working without going open-source

Chowdren was originally open-source in 2012, but in the end, that was simply not worth it.

However, if you check the list of supported plugins/behaviors/ACEs in the original post, that should give you a good idea of what is supported. That list only shows the Construct 2-specific features that are supported.

mOOnpunk

Chowdren only implements a subset of the Construct 2 runtime, and has the luxury of not having to support ALL of the games made for Construct 2. Doing this for the entire Construct 2 runtime and maintaining compatibility with existing games would take a long time for Scirra, and wouldn't be a good investment.

The current Construct 2 runtime is great, fulfills the needs of a typical user, and is simple to extend because of Javascript. Chowdren is a great solution for advanced users, but is probably not well-suited for your typical user.

newt The "Fake 3D" example that was posted earlier uses "For each", so it is supported in Chowdren You can check the list in the original post for what plugins/behaviors/ACEs are supported.

Just to emphasize a few things: Chowdren can run events especially fast, but with the move to native code, there may also be performance improvements in other areas (less overhead when interfacing with OpenGL/D3D/etc, less runtime overhead, and so on). However, most users will find Chowdren valuable because

• It is very portable, and can be used with pretty much all console/desktop platforms
• Game-specific changes and optimizations can be added to the runtime, yielding a great deal of control
• It is significantly faster, since everything is native code

I'd like to underline points 1 and 2, since a lot of focus has been on point 3 so far!

newt: On Android, Chowdren uses JNI / SDL.

We released NOT A HERO using this Android backend, so you can check it out for yourself on e.g. NVIDIA SHIELD

For HTML5, Chowdren has an Emscripten backend, which I assume is still faster than the standard C2 runtime, especially when WebAssembly is used. For Chowdren, the emphasis is on console/desktop platforms, i.e. mostly Switch/PS4/XB1 and Windows/Mac/Linux.

(reserving for future use)