Jamjardavies (talk | contribs) No edit summary |
Jamjardavies (talk | contribs) No edit summary |
||
Line 3: | Line 3: | ||
# [https://marketplace.visualstudio.com/items?itemName=devCAT.lua-debug Lua Debugger] VSCode extension. | # [https://marketplace.visualstudio.com/items?itemName=devCAT.lua-debug Lua Debugger] VSCode extension. | ||
# Following files downloaded from [https://github.com/devcat-studio] devcat and placed where the Desynced Binary is (normally in: | # Following files downloaded from [https://github.com/devcat-studio] devcat and placed where the Desynced Binary is (normally in: <code>C:\Program Files (x86)\Steam\steamapps\common\Desynced\Desynced\Binaries\Win64</code>) | ||
## [https://github.com/devcat-studio/VSCodeLuaDebug/blob/master/debuggee/dkjson.lua] dkjson.lua | ## [https://github.com/devcat-studio/VSCodeLuaDebug/blob/master/debuggee/dkjson.lua] dkjson.lua | ||
## [https://github.com/devcat-studio/VSCodeLuaDebug/blob/master/debuggee/vscode-debuggee.lua] vscode-debuggee.lua | ## [https://github.com/devcat-studio/VSCodeLuaDebug/blob/master/debuggee/vscode-debuggee.lua] vscode-debuggee.lua | ||
# [https://github.com/StageGames/VSCodeLuaDebugger/blob/main/mobdebug.lua] mobdebug.lua downloaded to the root of the Mods folder (normally in: <code>C:\Program Files (x86)\Steam\steamapps\common\Desynced\Desynced\Content\mods</code> | |||
# [http://steamcommunity.com/sharedfiles/filedetails/?id=3024638463] VSCode-Debugging from Workshop | # [http://steamcommunity.com/sharedfiles/filedetails/?id=3024638463] VSCode-Debugging from Workshop | ||
Revision as of 02:15, 24 August 2023
Visual Studio Code
In order to debug using Visual Studio code, a few steps first need to be completed:
- Lua Debugger VSCode extension.
- Following files downloaded from [1] devcat and placed where the Desynced Binary is (normally in:
C:\Program Files (x86)\Steam\steamapps\common\Desynced\Desynced\Binaries\Win64
) - [4] mobdebug.lua downloaded to the root of the Mods folder (normally in:
C:\Program Files (x86)\Steam\steamapps\common\Desynced\Desynced\Content\mods
- [5] VSCode-Debugging from Workshop
With the above ready, start the game with -moddev
(optionally -log
too for better logging output). Once the game has started, enable the VSCode Debugging
from the Mod list.
Now in Visual Studio Code, create a folder called .vscode
and add a file called launch.json
and paste the following content into this file:
{
"version": "0.2.0",
"configurations": [
{
"name": "Desynced Debugger",
"type": "lua",
"request": "attach",
"workingDirectory": "${workspaceRoot}",
"sourceBasePath": "${workspaceRoot}",
"listenPublicly": false,
"listenPort": 56789,
"encoding": "UTF-8"
}
]
}
This will create the ability to launch the debugger using Visal Studio Code, using CTRL + SHIFT + D
. Once this has been pressed, you will now see Desynced Debugger
with a green Play button. Upon pressing the Play button, the debugger will be launched, listening for the game.
Now, in game, either start a new game (or load a save game), or hit Hot Reload (F7
) to cause the game to connect. Once connected, you'll have full access to stepping through code, as well as accessing the local and watch windows, etc.