Optional editor version switching

Suggestions & Feedback
1

The PlayCanvas _Editor_ is currently delivered as a rolling release. This is convenient for beginners, but not ideal for long-term projects that can take months or even years to develop and maintain.

The PlayCanvas team is actively improving the engine, but no system is perfect - the editor often has issues (there are 607 active issues on GitHub right now). Some of these problems even affect core features.

It’s also hard to maintain custom editor extensions. There’s no official API for loading or managing extensions, so any changes to the editor can break entire workflows.

One possible solution is to follow the example of another browser-based game engine, Construct, which lets users pick specific editor versions via the URL:

https://editor.construct.net/     - Latest release
https://editor.construct.net/r449 - Version r449 (yes, Construct 3 has 449 diffrerent versions)

PlayCanvas could use a similar approach:

https://playcanvas.com/editor        - Latest release
https://playcanvas.com/editor/v2.2.0 - Version v2.2.0

This would let the PlayCanvas team experiment more freely (nightly/beta releases), and deliver new features without the risk of breaking production projects, so no one would need to wake up at 2 A.M.

I can imagine that the PlayCanvas team envisions everyone using the same base, but when it comes to expensive game production, stability must come first.

1 Like