.cwt config files for Victoria II
To use these copy the contents of this repository and place it in a folder called .cwtools in the folder you open in vscode. E.g. if your mod is located at Victoria 2\mod\my_mod, you would extract this folder into Victoria 2\mod\my_mod\.cwtools.
See https://github.com/simsulla/cwtools/wiki/.cwt-config-file-guidance for guidance on the file format
If you'd like to contribute, press the pen icon on any file, then press "Create a new branch for this commit and start a pull request". You can then make further changes as a "pull request". When done, mention it in the pull request and your changes will be included.
For development and running use VS Code. Clone or fork github.com tboby/cwtools into one folder. Clone tboby/cwtools-vscode into another.
-
Open cwtools folder
-
Open a new terminal in VS Code
-
cd ./CWTools
-
dotnet build (for the core library project, that single command should be enough to restore all dependencies and build)
-
correct any compile errors and dotnet build again.
-
cd ../CWToolsTests
-
dotnet run
-
Open the cwtools-vscode folder (usually in another window)
-
Edit packet.json and packet.dependencies setting git url to your fork and git file to your local cwtools folder.
-
Open a new terminal in VS Code
-
./.paket/paket.exe update -g git (This tells it to pull the latest core library commit from the other repo locally)
-
In the debug panel on the left, run the launch profile "Quick Build and Launch Extension"
-
VS Code will build the language server, build the extension, then launch the extension in a new window (with the title "Extension host" or something)
-
Open the game folder you are testing