As we get close to a stable release we usually reduce the number of changes in order to help things stabilise and try to ensure the stable release is reliable. So you can expect releases to usually get a bit smaller as we get close to a stable update!
See this thread about suggestions if you want to propose new features. Please note we get far, far more feature requests than we could possibly act on, so this system is designed to help us prioritise.
Please report any issues here following all the guidelines: github.com/Scirra/Construct-bugs
Updates are not mandatory - you can choose whichever release you want to use on the releases page. If you work in a team, your whole team need to upgrade at the same time. That's a part of project management that your team will need to handle - software can't handle that for you.
If you install the stable version, then the installed version will always update to the latest stable release, and if you install a beta version, then the installed version will always update to the latest beta release. That should always work consistently, and if it doesn't, please file an issue.
You can choose which version of Construct you use on our releases page.
Everyone on the team needs to be on the same version of Construct, because save files are not backwards compatible. So make sure if you upgrade, everyone does it at the same time. Even if something goes wrong, source control lets you roll back to a working version at any time.
FWIW I'm using GitHub with my own game project and so far it's working out great.
FWIW, all keyboard shortcuts are listed in the manual.
As noted at the top of this guide, the Chrome web store has retired support for apps, and this information is preserved for archival reasons only.
The system 'Pick nth instance' condition does that.
I believe the 3D object is a third-party addon, so not something we are responsible for supporting or documenting.
You can already use value tweens for purposes like that.
There will be multithreading - that's explained in the next blog.
Steering/flocking is a really tough problem. I'm not sure how I'll tackle it yet, but I do think it's a really important part of it, so I'll definitely spend some time to get it right and blog about the results.
We routinely deal with feedback from users with large event-based projects and make improvements based on that feedback. We did it just this week with improvements to search in r312, for example. And 80% of my time remains on that kind of work. This is just a side project focusing on the coding features of Construct. I've already addressed many other points in both this blog post and these comments.
This violent language like "punch in the guts" and "stab in the back" is unacceptable. Please see our Forum & Community guidelines. You can disagree but you don't have to use language like that. I am going to stop responding to such remarks and may take moderation action if it carries on in future. I'll be carrying on with this project, and nobody has to follow it if they don't like it.
I genuinely don't understand this - it was apparently not controversial when I opened our latest blog on JavaScript coding with "Construct's visual block system can produce amazing results without having to write a single line of code. However if you want to go even further... then you can also write JavaScript code in Construct." Here I am now demonstrating how you can go further. I think all this talk of backstabbing and kissing the ground is way over the top.
We've been advertising JavaScript support in Construct since 2019! We're aiming to build a tool that does both visual blocks and coding really well. Maybe you don't use the coding side, and that's fine! Everyone can choose which they prefer.
Currently it does an exact match on what you type, including spaces.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.