Update template.

Content.Packaging/Content.Packaging.csproj

@@ -3,6 +3,7 @@
     <OutputType>Exe</OutputType>
     <ImplicitUsings>enable</ImplicitUsings>
     <Nullable>enable</Nullable>
+    <ServerGarbageCollection>True</ServerGarbageCollection>
   </PropertyGroup>
 
   <ItemGroup>
@@ -10,4 +11,4 @@
   </ItemGroup>
 
   <Import Project="..\RobustToolbox\MSBuild\Robust.Properties.targets" />
-</Project>
+</Project>

Content.Packaging/ContentPackaging.cs

@@ -3,6 +3,7 @@ using Robust.Packaging.AssetProcessing;
 
 namespace Content.Packaging;
 
+// Used both for manual packaging, and server-provided automatic packaging.
 public static class ContentPackaging
 {
     public static async Task WriteResources(
@@ -18,12 +19,12 @@ public static class ContentPackaging
 
         var inputPass = graph.Input;
 
-        await RobustClientPackaging.WriteContentAssemblies(
+        await RobustSharedPackaging.WriteContentAssemblies(
             inputPass,
             contentDir,
             "Content.Client",
             new[] { "Content.Client", "Content.Shared" },
-            cancel);
+            cancel: cancel);
 
         await RobustClientPackaging.WriteClientResources(contentDir, inputPass, cancel);
 

Content.Packaging/README

@@ -0,0 +1,10 @@
+Relatively barebones packaging script. Does not contain a server packaging script.
+Packaging a (sandboxed) client is generally very easy, but the server is a bit more complex due to likely depending on assets unique to your project.
+Here's a few notes to help:
+- It's recommended to build specific to your target OS, especially if depending on natives (i.e. sqlite).
+- If using hybrid ACZ, you will need to include a client package in the server package's root directory for it to use.
+- RobustServerPackaging is your friend, but be aware it will specifically omit texture resources.
+- Familiarize yourself with AssetGraph and RobustServerAssetGraph, it allows for asset preprocessing, postprocessing of the final build, etc.
+- The default asset passes will automatically compute metadata for audio without actually including the audio files in the server build. This allows your server to know how long sound clips are.
+
+It is additionally recommended to properly configure StatusHost to use a custom provider. The default works, but cannot handle complex cases.