
You will need to make a default item build for every weapon you add in the Mod Kit (and similarly for certain other types of items). You will need to go outside the Mod Kit to do this. You need to save a special .kit file in the same place as the item the default item build is for, using the same leaf name (that is, the same file name, minus the path).
After you create or update a default item build .kit file, you must manually save the associated item BP in the editor. This causes the default item build file to be parsed and added to the BP. |
To easily get to a particular asset folder in Windows Explorer, right-click an asset in that folder and select Show in Explorer
:
The default item build file tells GROUND BRANCH what accessories should be spawned with your item by default. In the case of weapons, this will always include a default magazine type. Some weapons also add default sights and maybe grips, and so on. It is up to you to ensure that the included extra attachments are validly selected and placed.
An example of a default item build can be found in the sample Mk23 mod in the Workshop by BlackFoot Studios. Here (within the operating system folder viewer we can see that a BP_Mk23.kit
file exists in the same place as the related BP_Mk23.uasset
asset. This file is not visible in the editor.
You will not see any .kit files within the editor, because they are non-asset types. Just because you do not see them does not mean that they are not there. |
The .kit
file itself is a JSON formatted file including a definition of the necessary attachments. In this case (as is commonly the case), just a magazine is specified. This means that if you click on the generic Mk23 icon in the character editor, you will be assigned the weapon with the specified magazine. If you click to edit a default item, the magazine will be inserted automatically as per the default item build.
The magazine can later be manually removed and/or replaced in the weapon editor by the user, if that is a thing that the user wants to do…
The default item build looks like this in a text editor:
{ "Ver": 12, "BuildName": "MK23", "Item": "Sidearm:BP_Mk23", "Children": [ { "Item": "Magazine:BP_Mk23_Magazine", "Well": "MagWell" } ] }
The version number (in this case 12) may increase in later releases of the Mod Kit and GROUND BRANCH game. We would suggest checking a recent saved item build or loadout to determine the latest version number. The game will usually just silently fail to load or display any apparently outdated item builds or loadouts. |
Rather than list all possible permutations of item types and syntax here, we would suggest that you build more complicated default weapon configurations in the in-game character editor, save the build to disk, and copy over the relevant part of the created item build in a text editor.
It is usually easiest to manually edit an existing default item build .kit file, but you may want to validate the JSON before saving with a JSON validator. Many different JSON validators exist, and this is just one example: https://codebeautify.org/jsonvalidator
|
Item builds that you create in-game can be found in your personal documents folder (e.g. "My Documents") under GroundBranch/ItemBuilds
|
If a default item build fails to spawn, there may be no error given in-game, but you may find an explanation of any fault in the game log. If a default item build fails to load, very often it may be an issue with a missing (or extra) comma, or bracket of any appropriate type. |