khallaandClaude Opus 5.5
5df7efc198
README explains --game-dir and the stored GameDir; the VS Code launch uses the stored path and builds through build.ps1. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
29 lines
1.2 KiB
JSON
29 lines
1.2 KiB
JSON
{
|
|
"version": "0.2.0",
|
|
"configurations": [
|
|
{
|
|
// Builds, then starts the game through the launcher (no debugger in the game).
|
|
// The game folder comes from build/x86-debug/sacredK.ini: run the
|
|
// launcher once with --game-dir "<Sacred Gold folder>" (README.md).
|
|
"name": "Run Sacred (sacredK)",
|
|
"type": "cppvsdbg",
|
|
"request": "launch",
|
|
"program": "${workspaceFolder}/build/x86-debug/sacredK.exe",
|
|
"args": ["log"],
|
|
"cwd": "${workspaceFolder}/build/x86-debug",
|
|
"preLaunchTask": "Build x86-debug",
|
|
"console": "internalConsole"
|
|
},
|
|
{
|
|
// Debug our DLL inside the game: set [debug] WaitForDebugger=1 in
|
|
// build/<preset>/sacredK.ini, start "Run Sacred", then run this and
|
|
// pick sacred.exe. The DLL waits (up to 60 s) before installing hooks.
|
|
"name": "Attach to sacred.exe",
|
|
"type": "cppvsdbg",
|
|
"request": "attach",
|
|
"processId": "${command:pickProcess}",
|
|
"symbolSearchPath": "${workspaceFolder}/build/x86-debug"
|
|
}
|
|
]
|
|
}
|