DocumentationBot: Publish SDK documentation

2026-08-25T05:13:11Z

Publish SDK documentation

@@ Line 1: / Line 1: @@
 {{GameNav}}
-{{Draft}}
+{{Notice|title=Current publishing boundary|Grimwar Workshop publishing accepts non-empty, map-only Release packages. A package containing VMods or another addon content kind cannot be published through this workflow.}}
-Maps and server mods use one addon package, catalogue, enable state, conflict-resolution model, and distribution pipeline. An addon can contain maps, server mods, or both.
+Steam Workshop is one source in Grimwar's addon catalog. The same package can be tested locally, published, subscribed to, selected, validated, and loaded without a separate Workshop format.
-== Author workflow ==
+== Prepare the map package ==
-# Produce a release export with the Vellocet SDK.
+# Finish local testing with a Development package.
-# Resolve every validation error before publication.
+# Open '''Tools > Vellocet > SDK > Map Exporter'''.
-# Supply a title, description, preview image, content tags, and visibility.
+# Select '''Release'''. Release builds Windows client, macOS client, and Linux dedicated-server artifacts and requires complete lighting and spatial bakes.
-# Create or update the Workshop item through the supported publishing tools.
+# Assign '''Map Image (in-game)''' for the map browser.
-# Accept the Steam Workshop legal agreement when Steam requests it.
+# Assign separate '''Addon Thumbnail (Workshop)''' artwork. It must be a decodable 1920 x 1080 PNG or JPEG.
-# Test subscribe, update, disable, unsubscribe, and clean-account installation paths.
+# Build the Release package and resolve every validator error.
-== Multiplayer delivery ==
+The exporter places the Workshop image at the addon root and records it as <code>addonThumbnail</code>. A map's <code>map.thumbnail</code> is separate and does not satisfy the Workshop requirement.
-Servers advertise the required addon identity and exact build. Clients must install and validate the matching package before completing the join flow. Server-only addon content is not delivered to clients unless the package also contains content required by the active session.
+Do not modify a Release folder after export. Grimwar validates the manifest, schema, compilation receipt, build ID, file paths, sizes, SHA-256 hashes, and platform payload before upload and again before mounting.
 [[Category:Grimwar]] [[Category:Steam Workshop]]

WikiAdmin: Initialize Vellocet Developer Community

2026-08-25T00:33:10Z

Initialize Vellocet Developer Community

New page

{{GameNav}}
{{Draft}}

Maps and server mods use one addon package, catalogue, enable state, conflict-resolution model, and distribution pipeline. An addon can contain maps, server mods, or both.

== Author workflow ==

# Produce a release export with the Vellocet SDK.
# Resolve every validation error before publication.
# Supply a title, description, preview image, content tags, and visibility.
# Create or update the Workshop item through the supported publishing tools.
# Accept the Steam Workshop legal agreement when Steam requests it.
# Test subscribe, update, disable, unsubscribe, and clean-account installation paths.

== Multiplayer delivery ==

Servers advertise the required addon identity and exact build. Clients must install and validate the matching package before completing the join flow. Server-only addon content is not delivered to clients unless the package also contains content required by the active session.

[[Category:Grimwar]] [[Category:Steam Workshop]]

Grimwar/Steam Workshop addons - Revision history

DocumentationBot: Publish SDK documentation

WikiAdmin: Initialize Vellocet Developer Community