Use comments starting with # character, to remember reasons for writing tricky stuff.
Vanilla uses 1 tab for indentation rather than spaces. Indent properly to easily spot unclosed braces.Use UTF-8-BOM for localisation files (.yml).Consider using a source control system like Git and a collaborative forge like GitHub to manage team collaboration, or just make a copy of the file somewhere else. Backup your work to avoid losing everything.Use a proper merge tool (like WinMerge), to merge between folders, and update modified vanilla files to a new vanilla patch.So choose a name, no one else will ever use, like the name of your mod. (Your files can have any name, all files in the folder will be loaded by the game. Minimize overwrites of vanilla files by adding separate files and loading from folders whenever possible, to improve mod compatibility and maintenance.
If you want to toggle comments in Sublime, you also need to add this file to the same "User" folder. It adds colored highlighting for effects and triggers. There is an extension for it released by the developers of Imperator which could be used with HOI4 but use at your own risk: Sublime Tools. (Note: validation rules are incomplete and will show many false errors in gui and localization files).
#Hearts of iron iv workshop install#
To install it, go to Extensions on the left panel of VS and search for CWTools. Has a fan-made CWTools extension with Paradox syntax highlighting, validation and tooltips for triggers and effects. To set it as default, go to Settings, Style Configurator, find Perl in the list on the left and add "gui txt" (without quotes) to the "User ext." field at the bottom. Choose Perl as your language, as it will provide good highlighting and allow to fold blocks of code and comments.
0 kommentar(er)
