Hi everyone, We want to update you on the state of the Visual Studio Code for Unity package. This plugin was a result of one of our hackweek experiments by a few of our former employees. Unfortunately, it’s never been fully functional and hasn’t received any updates for almost two years, bringing you an unstable coding experience. We want to be open with you about its state so that you know what to expect. The scripting team has huge projects in the works with a significant impact for a majority of our users (like modernization of .NET and iteration time) and we believe that being clear on what’s on the to-do list and what isn’t will help us focus on them. That’s why we’ll be removing the Visual Studio Code for Unity package from the list of packages that will be enabled for new projects by default. If you’re using VSCode, and you’ve experienced quality issues, we recommend that you switch to using an IDE that Microsoft is helping us provide support for, such as from Visual Studio Community. There are also multiple other alternatives, such as JetBrains Rider. Please notice that we’re not preventing anyone from using VS Code in their projects if they prefer it, the existing plugin will continue to work. Also the plugin is available under the very permissive MIT license that allows to fork the project and create derivative works, so an open source alternative could emerge from the community. We will post updates here as we progress with the plan to officially end support for the Visual Studio Code plugin.