V6 Release
Real-Time Error Handling
Typically, handling an error means your entire game crashes - it's a huge pain. However, our goal is real-time development similar to Inception. That means you could be building a game with tens or eventually hundreds of people at once - so can you let one rogue script crash the entire game?
No way.
With V6, we're adding real-time error handling: Even if a script runs into an error, all the other scripts will continue to run fine. Mirror Engine simply pauses execution of that script.
Even better, Mirror Engine will still try to run the rest of the script, so code will still execute up to that line. Take a look below.
Intellisense
We're rolling out basic intellisense, for example, so you can see that your main class has access to this.entity, even though it's not visible since its inherited from MirrorScript.
Site Polish
You'll enjoy numerous minor fixes and improvements, such as the full How-To section being available without needing to login, password recovery flows, and more.
Versioning Questions
Our aim is to release often, so some releases will be smaller and some larger. This follows the convention of large projects like Google Chrome, which is on version 138 at this time of writing.
Our intention is convenience and clarity: you'll know that if you're on V6 and you last checked out the engine on V3, you'll have a good number of improvements to enjoy.
Other game engines may follow different conventions, such as rare major versions (e.g. Unity 6, Unreal 5, Godot 4, etc.). Since Mirror Engine runs in an abstracted runtime above low-level code by nature of TypeScript/JavaScript, there's much less risk of breaking changes.
Further, since Mirror Engine is multiplayer-by-default, it's wise to assume that games will need to stay up to date instead of providing long-term support for old versions - in the same way that you regularly update your browser for the latest fixes, security patches, and new features.
Major Version Does Not Mean Breaking
We aim to keep scripts as backward-compatible as possible. If/when we deprecate a feature, we'll give plenty of heads-up and will maintain the old implementation as long as is feasible. In-editor, we will add strikethrough code hints for deprecated methods so you'll be well-informed.
The one exception here may be security updates, but nevertheless we'll aim to be as clear as possible in what to expect.
We're open to feedback as always!
Watch the Full Video on YouTube
For more visuals, watch the full video here.
Did You Apply for the Alpha?
We're regularly onboarding new devs: sign up here and join our Discord.
Feel free to reach out to me on YouTube, Instagram, TikTok, and X. Cheers!
