Flowcharts improvements; Instances Bar fixes; New demo game & more.
Tested with a blank project. This version has errors in main.js. (TypeError: Cannot convert undefined or null to object) The result is a blank screen. Please fix ASAP, blocked and unable to revert to old version till this is fixed!
Please look into a new feature that lets us roll back a project to a previous build. Right now the only way to do this is to copy everything to a new project. These broken updates happen way too often and it is not acceptable. I have a hard time believing that any of these updates are even tested before they are published.
These are beta releases. Their purpose is for testing and they will always have issues like this coming up occasionally. If you'd prefer to avoid this, stick to stable releases.
I would if it was possible to easily switch existing projects to stable. That is the point I am trying to make. If you want to use your paid users to test your product for you, just make it easier for them to roll back when you release broken updates. Try to imagine how frustrating this is to your users that opted to use the beta and after a days worth of work to find out they cant even export.
You should expect beta releases to be occasionally broken. If you don't want to deal with that, stick to stable releases and don't use beta releases.
It's impossible to reliably allow projects saved in newer versions to be opened in older versions. What happens if you use a new feature which the older version doesn't support? There's no solution to that.
There is a solution. You could automate the process to copy all your layers, assets, layouts and events from the broken release. That way the user can paste all the dependencies to a previous release that was working. If a particular feature is not compatible, these events could be commented out, removed or disabled. At least this way the user can continue to work rather than just wait for the next release.
This solution is what I have done in the past when I can't wait for a new release. The issue is, it's very time consuming to do manually.
It's not possible to detect features that are not compatible, as the older version doesn't know they even exist.
An error is enough to know something isn't compatible and the user can troubleshoot and/or disable those events. The fact that I can manually copy one project to an older one is proof that it is possible and I have been doing that for many years.
All I am saying is, the copy process is time consuming and it needs to be copied in the correct order for it to work. If that was slightly automated it would benefit the user significantly. You are getting hung up on "This is a beta". This has usages more than just rolling back to older versions it's also very helpful when you want to copy certain things you built between projects which very often are from different versions.
It's not possible to show an error for features that are not compatible either. Doing so means using a time machine to predict what changes are made in future and ensure a useful error message is shown for them.