Vertex/Content - Revision history

DocumentationBot: Clarify custom content navigation and standardize asset examples

2026-10-04T16:30:13Z

Clarify custom content navigation and standardize asset examples

← Older revision		Revision as of 12:30, 4 October 2026
Line 2:		Line 2:

	'''Content''' manages files owned by a map or SDK resource and references to assets from other packages. The connected game decides which file types it supports and how those files become usable in the game.		'''Content''' manages files owned by a map or SDK resource and references to assets from other packages. The connected game decides which file types it supports and how those files become usable in the game.

			For Grimwar, start with the asset you want to add:

			{\| class="wikitable"
			! Asset !! Guide
			\|-
			\| Sounds and music \|\| [[Grimwar/Custom content#Sounds and music\|Import audio, choose its playback type, and play it in a map]].
			\|-
			\| Textures and materials \|\| [[Grimwar/Custom content/Materials and models#3. Create a wall material\|Create a Unity material]].
			\|-
			\| Models and prefabs \|\| [[Grimwar/Custom content/Materials and models#4. Import a model and save a prefab\|Import a model and save a prefab]].
			\|-
			\| Shared libraries and supported formats \|\| [[Grimwar/Custom content\|Browse all custom content workflows]].
			\|}

	== Import your files ==		== Import your files ==
Line 12:		Line 26:
	Vertex keeps imported source under <code>Content/</code> and records it in <code>content.json</code>. Keep both beside the map or resource manifest. Importing a file makes it available; you still need to place it or reference it.		Vertex keeps imported source under <code>Content/</code> and records it in <code>content.json</code>. Keep both beside the map or resource manifest. Importing a file makes it available; you still need to place it or reference it.

	An asset key identifies the package and asset, for example <code>asset:shared_sounds/~~wind_loop~~</code>. Display names can change without changing that key. Use '''Replace media''' to replace a file while retaining its references. Reimporting it as a new asset creates a different entry.		An asset key identifies the package and asset, for example <code>asset:shared_sounds/my_wind_loop_01</code>. Display names can change without changing that key. Use '''Replace media''' to replace a file while retaining its references. Reimporting it as a new asset creates a different entry.

	Models may have companion materials and textures. Keep those files together when importing. '''Rebuild model previews''' refreshes the editor preview after external changes; the game compiler still builds the runtime model.		Models may have companion materials and textures. Keep those files together when importing. '''Rebuild model previews''' refreshes the editor preview after external changes; the game compiler still builds the runtime model.

			== Sounds and music ==

			Grimwar's '''Sound''' import type accepts WAV, Ogg Vorbis, and MP3. Use it for effects, ambience, announcements, or music. The [[Grimwar/Custom content#Sounds and music\|sound walkthrough]] covers playback settings, volume, and selecting a sound on an <code>env_ambient</code> entity. To keep reusable audio outside map folders, [[Grimwar/Custom content#Make a reusable media pack\|create a shared media pack]] and use its sound from each map.

	== Materials and prefabs authored in Unity ==		== Materials and prefabs authored in Unity ==

	For a general selection of custom assets across Grimwar maps, follow [[Grimwar/~~Unity custom~~ content\|Unity materials and models for Vertex]]. Keep one personal SDK copy in a shared library folder outside your map projects, create assets beneath its <code>Compiler/Assets/CustomContent/</code>, and export its catalog. Connect each map to that same library to select its assets in the Materials and Models browsers. The guide covers each folder and setting with a wall material and a crate prefab. Dropping files into a Unity folder alone does not add them to Vertex, and Content's file importer does not accept <code>.mat</code> or <code>.prefab</code> files.		For a general selection of custom assets across Grimwar maps, follow [[Grimwar/Custom content/Materials and models\|Unity materials and models for Vertex]]. Keep one personal SDK copy in a shared library folder outside your map projects, create assets beneath its <code>Compiler/Assets/CustomContent/</code>, and export its catalog. Connect each map to that same library to select its assets in the Materials and Models browsers. The guide covers each folder and setting with a wall material and a crate prefab. Dropping files into a Unity folder alone does not add them to Vertex, and Content's file importer does not accept <code>.mat</code> or <code>.prefab</code> files.

	== Use an installed package ==		== Use an installed package ==

DocumentationBot: Keep custom assets in one library shared across maps

2026-10-04T16:11:48Z

Keep custom assets in one library shared across maps

← Older revision		Revision as of 12:11, 4 October 2026
Line 18:		Line 18:
	== Materials and prefabs authored in Unity ==		== Materials and prefabs authored in Unity ==

	For Grimwar, follow [[Grimwar/Unity custom content\|Unity materials and models for Vertex]]. ~~Create the Unity~~ assets beneath <code>Compiler/Assets/CustomContent/</code> ~~in a personal SDK copy~~, export a catalog~~, and connect Vertex~~ to that ~~copy~~. The guide covers each folder and setting with a wall material and a crate prefab. Dropping files into a Unity folder alone does not add them to Vertex, and Content's file importer does not accept <code>.mat</code> or <code>.prefab</code> files.		For a general selection of custom assets across Grimwar maps, follow [[Grimwar/Unity custom content\|Unity materials and models for Vertex]]. Keep one personal SDK copy in a shared library folder outside your map projects, create assets beneath its <code>Compiler/Assets/CustomContent/</code>, and export its catalog. Connect each map to that same library to select its assets in the Materials and Models browsers. The guide covers each folder and setting with a wall material and a crate prefab. Dropping files into a Unity folder alone does not add them to Vertex, and Content's file importer does not accept <code>.mat</code> or <code>.prefab</code> files.

	== Use an installed package ==		== Use an installed package ==

DocumentationBot: Guide custom Unity materials and models into Vertex

2026-10-04T15:55:09Z

Guide custom Unity materials and models into Vertex

← Older revision		Revision as of 11:55, 4 October 2026
Line 5:		Line 5:
	== Import your files ==		== Import your files ==

	# Save the map, then open '''Map → Content…'''. For a standalone resource, open its '''Content…''' controls in VSDK.		# Save the map, then open '''Settings → Map details → Content…'''. For a standalone resource, open its '''Content…''' controls in VSDK.
	# Choose a content type and select '''Import files'''.		# Choose a content type and select '''Import files'''.
	# Review the imported names and settings. The SDK may offer controls such as audio playback type or volume.		# Review the imported names and settings. The SDK may offer controls such as audio playback type or volume.
Line 15:		Line 15:

	Models may have companion materials and textures. Keep those files together when importing. '''Rebuild model previews''' refreshes the editor preview after external changes; the game compiler still builds the runtime model.		Models may have companion materials and textures. Keep those files together when importing. '''Rebuild model previews''' refreshes the editor preview after external changes; the game compiler still builds the runtime model.

			== Materials and prefabs authored in Unity ==

			For Grimwar, follow [[Grimwar/Unity custom content\|Unity materials and models for Vertex]]. Create the Unity assets beneath <code>Compiler/Assets/CustomContent/</code> in a personal SDK copy, export a catalog, and connect Vertex to that copy. The guide covers each folder and setting with a wall material and a crate prefab. Dropping files into a Unity folder alone does not add them to Vertex, and Content's file importer does not accept <code>.mat</code> or <code>.prefab</code> files.

	== Use an installed package ==		== Use an installed package ==

DocumentationBot: Version 1

2026-10-01T04:13:05Z

Version 1

New page

{{VertexNav}}

'''Content''' manages files owned by a map or SDK resource and references to assets from other packages. The connected game decides which file types it supports and how those files become usable in the game.

== Import your files ==

# Save the map, then open '''Map → Content…'''. For a standalone resource, open its '''Content…''' controls in VSDK.
# Choose a content type and select '''Import files'''.
# Review the imported names and settings. The SDK may offer controls such as audio playback type or volume.
# Select the new asset in the appropriate material, model, entity, or script field.

Vertex keeps imported source under <code>Content/</code> and records it in <code>content.json</code>. Keep both beside the map or resource manifest. Importing a file makes it available; you still need to place it or reference it.

An asset key identifies the package and asset, for example <code>asset:shared_sounds/wind_loop</code>. Display names can change without changing that key. Use '''Replace media''' to replace a file while retaining its references. Reimporting it as a new asset creates a different entry.

Models may have companion materials and textures. Keep those files together when importing. '''Rebuild model previews''' refreshes the editor preview after external changes; the game compiler still builds the runtime model.

== Use an installed package ==

Select an installed asset in Content and choose '''Use this package'''. Vertex records the provider's add-on ID and references the asset by key. The resulting build depends on that package and does not include another copy of its files.

The provider must be installed and enabled in the game. Publish and distribute the provider as well as the map or mod that uses it. A different display title or Workshop item number does not replace the stable package ID.

'''Copy files into this package''' creates an owned copy when you want to distribute and maintain the files yourself. References to other packages that you keep using remain dependencies. Check that the asset's terms permit redistribution.

== Check what ships ==

'''Check build contents''' lists selected files, sizes, and the references or inclusion settings that bring them into the build. Use it before publishing a large package.

Enable '''Include in build''' for files used only through dynamically constructed script references. An unchecked asset is still included when the map or another included asset needs it.

Missing providers, cycles, unsupported formats, or changed source files can stop a build. Fix the reported source or dependency and rebuild. Avoid editing the generated package manifest to bypass an error.

For supported formats, a complete sound example, and reusable media packs, see [[Grimwar/Custom content]]. For another game's support, use that game's SDK documentation.

[[Category:Vertex]]