2.0.8

Changed

• Changed the build path to avoid conflicts with the Defold Editor build.

2.0.7

Fixed

• Fixed the soft migration of the workspace launch configuration.

2.0.6

Changed

• Renamed the category of tasks and commands from Defold to Defold Kit to avoid conflicts.
• Renamed all the settings keys from defold. to defoldKit. to avoid conflicts.
• Renamed launch configuration to Defold Kit to avoid conflicts.

Added

• Soft migration of user settings from defold. to defoldKit. keys.
• Soft migration of the workspace launch configuration from Defold to Defold Kit name.

2.0.5

Removed

• Removed everything related the Launch (without debugger) and Build to Launch commands to avoid confusing.
• Now the only way to launch the game is using the Run ang Debug panel.

2.0.4

Fixed

• Fixed the launch command for a project with spaces in the path.

2.0.3

Added

• Added an additional annotations source to the settings — d954mas/defold-api-emmylua.

2.0.2

Fixed

• Fixed dmengine selection bug for macOS with Intel during preparing for launch. Thanks @wesleyfr 🙏.

2.0.1

Fixed

• #28 Unwrapped require('debugger.debugger’) calls in the docs and in the debugger.script file to avoid problems with Defold code analyser before build.

2.0.0

🎉 This happened.

👏 Yes, now this is an extension for Visual Studio Code.

🥂 Named Defold Kit.

🔥 Yes, it can do everything that was described in the original guide. Automatically, with user-friendly installation and configuration.

You can install it from Visual Studio Marketplace or manually by using the attached .vsix archive.

And start to ✨ develop, build, launch, debug, bundle and deploy ✨ your game made with Defold.

P.S. Old guide is still availabe on the 📝 old-guide branch.

1.0.9

• Updated Defold API up to 1.5.0