Build.json
Build.json is an optional file that tells the ADK which folders’ assets get an asset identifier. Packs that depend on yours can use those assets, so they don’t need to carry their own copies. The file is read only when you build; it isn’t included in the built pack and the game never reads it.
It sits in the root of the pack’s source folder, next to Info.json:
my-great-mod Info.json Build.json Definitions.json Props MaterialsQuick Example
Section titled “Quick Example”{ "assets": { "folders": [ "Materials", "Props/**" ] }}Fields
Section titled “Fields”assets.folders (optional)
Section titled “assets.folders (optional)”A list of folders, relative to the pack root, using forward slashes. The prefabs, materials, textures, audio clips and shaders in each folder get an identifier, so definitions in your pack and in packs that depend on yours can reference them. Model files (.fbx, .obj and similar) never get one; reference the prefab instead.
A plain entry such as "Materials" covers the files directly in that folder. Add a trailing /** to include its subfolders too. "." is the pack root and "./**" is the whole pack. Entries can’t overlap, can’t use other glob characters, and must name an existing folder that holds at least one of those assets.
Assets in a listed folder are referenced by file name, so two assets of the same type across the listed folders can’t share a file name.
Using Another Pack’s Assets
Section titled “Using Another Pack’s Assets”Your prefabs and materials can reference an asset in a folder that another pack lists in its Build.json, as long as that pack is in your Info.json dependencies.required list. The built bundle then links to the other pack’s bundle instead of copying the asset. The build warns about any reference that can’t link and copies that asset into your bundle. This happens for an asset in a folder the other pack doesn’t list, a model file, or a pack that is only an optional dependency. A prefab nested from another pack is always copied into your bundle, though the materials and textures it uses still link.
Without a Build.json
Section titled “Without a Build.json”Without the file, or without assets.folders, only the assets at the root of the pack get an identifier. This is the behavior Asset Packs describes.
© 2026 Giraffe Lab LLC. All rights reserved.