In another thread the subject of Alcscript quickscripts came up in a somewhat negative way. Now I know quickscripts are not perfect and they will always be limited compared to full Alcscripts. They are intended though to make things easier for those who are confused by the large chunks of Alcscript required to make even simple actions happen.
Lately I seem to be the only one who has been programming quickscripts. Quickscripts are tedious to program and they do not cover any new territory, which is most likely why the regular PyPRP devs are currently not working in that area. And that is a good thing because as long as there are new features to add I would prefer them doing that.
Now I am willing to add more quickscripts, but only if there is a need for them. I was planning for example to turn the Alcscript for the two way animation with saved state from the wiki into a quickscript.
In the quickscript you would only have to list your objects and variables (some of which optional) and then it generates the full alcscript from that. That should be about 18 lines for you to code instead of the 145 lines of logic scripting you can see in that wiki article.
So I wonder if people will be using a quickscript like that. Because if there is no need for it I could probably save myself a lot of work.