Posted August 10, 2020 by Cosmo Myzrail Gorynych
So, what's next?
Ct.js has walked an eventful journey during this year or two. It got a much more performant graphics engine, more modules, more input methods, code editor with powerful typing capabilities, smooth UI, and became an all-round engine for prototyping, learning, and making hobby games. It is now time to become the best engine. At least for 2D games π
Ct.js once again enters its Next phase — a phase of exploration, new possibilities, removal of the old stuff, and building new spaceships. The phase of prereleases. πΈβ¨π
These prereleases will heavily remake the basis of ct.js. We promise no backward (or even forward) compatibility as the changes are really game-changing and already workload-heavy. In particular, we plan to make at least three prereleases that all will focus on a specific issue:
β¬ This is our current vision of a room editor and tabbed interface.
Each prerelease will be publicly available and ready for fiddling. We can say that releases will be self-sufficient so you will be able to make a complete game in it, but again, we also don't promise your projects will be easily transferable to subsequent versions. We may release bug fixes, QoL updates, and such to prereleases depending on their popularity, compatibility, and your requests.
After these three steps, we will need some more time to polish ct.js and add less significant, but still relevant features: starter templates, configurable splash screens, further customizations for your projects, etc. Only then ct.js will return to its more stable release cycle. π
Of course, this is a helluva work, and without support, the development will… be… stretched… a lot. There are numerous ways to support ct.js:
Currently, ct.js is programmed mainly by me (CoMiGo) with regular contributions from @naturecodevoid from Github. And this is bad. Such big OSS projects don't usually survive at all at such a team scale. If you want to make the future of ct.js more sturdy and take an active part in its development, join our Discord server, say "hi", coordinate with us at the #engine-development channel, and start solving issues from our git repo.
Nope, we would like to provide a couple more nifty things to you and v1.4 and provide bug fixes. And if you send a PR with a feature request fulfilled, we will surely release it as a new version. π
Here: