Update with changes from Dev

.github/workflows/push.yml

@@ -122,7 +122,7 @@ jobs:
             BUILD=build:ci
 
   notify:
-    name: Notify
+    name: Build Failure Notifications
     runs-on: ubuntu-latest
     needs:
       - build

antora.yml

@@ -9,4 +9,8 @@ asciidoc:
   # https://github.com/asciidoctor/asciidoctor/blob/917d3800a08a8f283a8d05beb08bb75af1673de5/lib/asciidoctor.rb#L391
   attributes:
     # Uses zero-width joiner (U+200D) to avoid being split across lines
-    cpp: C‍+‍+
+    cpp: C‍+‍+
+    # Use backslash without it escaping things in other situations
+    literal-backslash: \
+    # To keep paths from breaking across lines
+    NoBreakBackslash: ‍\‍

modules/ROOT/attachments/BeginnersGuide/dependencies/SML.vsconfig

@@ -35,7 +35,7 @@
     "Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
     "Microsoft.VisualStudio.Component.Graphics.Tools",
     "Microsoft.VisualStudio.Component.VC.DiagnosticTools",
-    "Microsoft.VisualStudio.Component.Windows11SDK.22000",
+    "Microsoft.VisualStudio.Component.Windows11SDK.26100",
     "Microsoft.VisualStudio.Component.ManagedDesktop.Prerequisites",
     "Microsoft.VisualStudio.Component.DotNetModelBuilder",
     "Microsoft.ComponentGroup.Blend",

modules/ROOT/nav.adoc

@@ -55,12 +55,11 @@
         *** xref:Development/Modeling/MainMaterials.adoc[Main Materials]
         *** xref:Development/Modeling/style.adoc[Style Guide]
     ** xref:Development/UnrealEngine/index.adoc[Unreal Engine]
-        *** xref:Development/UnrealEngine/Code.adoc[Code]
-        *** xref:Development/UnrealEngine/BluePrints.adoc[Blueprints]
-        *** xref:Development/UnrealEngine/Editor/index.adoc[Unreal Editor]
-            **** xref:Development/UnrealEngine/Editor/MainWindow.adoc[Main Window]
+        *** xref:Development/UnrealEngine/UnrealLearningResources.adoc[Unreal Learning Resources]
         *** xref:Development/UnrealEngine/CoreRedirect.adoc[Core Redirects]
         *** xref:Development/UnrealEngine/StringClasses.adoc[String Classes]
+        *** xref:Development/UnrealEngine/Code.adoc[Code]
+        *** xref:Development/UnrealEngine/BluePrints.adoc[Blueprints]
     ** xref:Development/Satisfactory/index.adoc[Satisfactory]
         *** xref:Development/Satisfactory/Multiplayer.adoc[Multiplayer]
         *** Game Features
@@ -128,6 +127,7 @@
     ** xref:Development/ReuseGameFiles.adoc[Reusing Base Game Files]
     ** xref:Development/ExtractGameFiles.adoc[Extracting Game Files]
     ** xref:Development/TestingResources.adoc[Testing/Multiplayer Testing]
+// TODO ** xref:Development/OptionalModDependencies.adoc[Optional Mod Dependencies]
     ** xref:Development/OpenSourceExamples.adoc[Learning from Open Source Mods]
     ** xref:UploadToSMR.adoc[Uploading your Mod to SMR]
 
@@ -144,6 +144,8 @@
 // * Translating Mods
 //     ** xref:Translation/GetStartedTranslating.adoc[Get Started Translating]
 //     ** xref:Translation/UsingTolgee.adoc[Using Tolgee]
+//     ** For Users
+//         *** TODO
 //     ** For Mod Developers
 //         *** xref:Translation/Developers/RequestTolgeeProject.adoc[Using Tolgee]
 //         *** xref:Development/Localization.adoc[Localizing Mods]

modules/ROOT/pages/CommunityResources/AssetToolkit.adoc

@@ -1,15 +1,5 @@
 = Unreal Engine Asset Toolkit
 
-[WARNING]
-====
-The Asset Toolkit has not yet been fully tested on UE5 or the 1.0 release.
-====
-
-[NOTE]
-====
-This article is a work-in-progress. Please contact us on the Discord if you run into any issues here.
-====
-
 Community member Archengius has created a set of two plugins
 useful for dumping content from a compiled Unreal Engine game and importing it into the Unreal Engine Editor.
 
@@ -26,10 +16,10 @@ making working with base-game content much more convenient.
 [WARNING]
 ====
 If you decide to generate a complete copy of the project,
-make sure that your Content folder is not publicly available on Github or similar.
+make sure that your Content folder is not publicly available on GitHub or similar.
 
-If you only have a plugin-level repo, this is not a problem,
-but if you have a project-level repo as well, you should watch out for this.
+If you only have a plugin-level repo (root folder has a `.uplugin` file), this is not a problem,
+but if you have a project-level repo as well (root folder has a `.uproject` file), you should watch out for this.
 
 Because the assets are already tracked (shipped with the starter project),
 simply adding them to your `.gitignore` will not ensure they are excluded.
@@ -44,16 +34,19 @@ for more info.
 The Asset Toolkit repository consists of two plugins,
 a dumper, to be installed in the game,
 and an asset generator, to be installed in the editor.
-Both are contained in the https://github.com/mircearoata/UEAssetToolkit/tree/dev[Asset Toolkit repository].
+Both are contained in the https://github.com/satisfactorymodding/UEAssetToolkit/tree/dev[Asset Toolkit repository].
 Download a zip of the repository and extract somewhere,
 or clone it if desired.
 Regardless, make sure the copy you obtain is of the **`dev` branch** as it will have the latest fixes.
 
 [NOTE]
 ====
-Note that the link above points to the *dev branch of Mircea's fork* of the https://github.com/Archengius/UEAssetToolkit[original project].
+Note that the link above points to the *dev branch of the Satisfactory Modding Org's fork* of the https://github.com/Archengius/UEAssetToolkit[original project].
 Said fork is the one that the https://github.com/satisfactorymodding/UnrealProjectUpdater/blob/master/.github/workflows/updateSML.yml#L176[CI scripts]
 use to semi-automatically generate the starter project, and as such is usually kept more up to date.
+
+Community changes to the Asset Toolkit are often slow to merge,
+so it's best to ask on the Discord to see if there is a more recent fork or branch available.
 ====
 
 Once you have downloaded the files,
@@ -90,7 +83,8 @@ It takes files produced by the dumper and generates the uasset files your editor
 #include "MaterialEditingLibrary.h"
 ----
 - If you get errors about unresolved external modules, try deleting the project's `Intermediates` folder, regenerating project files, and building again.
-- Ask for help on the discord.
+- Ask on the Discord if there is a community fork that is more up to date.
+- Ask for help on the Discord.
 
 === Packaging the Asset Dumper as a Mod
 
@@ -110,22 +104,29 @@ If you don't, you could get ambiguous errors while dumping and generating.
 ====
 
 A user interface exists for using the dumper,
-but there are some crashing problems with it,
+but there are many crash problems with it,
 so these directions will cover using the command line version instead.
 
-To dump assets, navigate to your game install directory in Powershell.
-For example, `C:\EpicGamesGames\SatisfactoryEarlyAccess`
+First, navigate to your game install directory in Powershell.
+Open Powershell and use the `cd` command to change directories.
+For example, if your game is installed at `C:{NoBreakBackslash}EpicGamesGames{NoBreakBackslash}SatisfactoryEarlyAccess`,
+you would run:
+
+`cd C:\EpicGamesGames\SatisfactoryEarlyAccess`
 
 Next, from that directory, edit the following Powershell command to point to your game executable, then run it:
 
-`FactoryGameEGS.exe -EpicPortal -NoSteamClient -DumpAllGameAssets -RootAssetPath=/Game -ExcludePackagePaths=/Game/WwiseAudio -ExcludePackageNames=/Game/Geometry/Meshes/1M_Cube_Chamfer -PackagesPerTick=32 -ExitOnFinish -log -NewConsole`
+// cspell:ignore norhithread
+// Prevent break on dash and its argument
+`FactoryGameEGS.exe -EpicPortal -NoSteamClient -DumpAllGameAssets -{wj}RootAssetPath=/Game -ExcludePackagePaths=/Game/WwiseAudio -ExcludePackageNames=/Game/Geometry/Meshes/1M_Cube_Chamfer -PackagesPerTick=32 -ExitOnFinish -log -NewConsole -nullrhi -norhithread`
 
 [WARNING]
 ====
 The above command assumes you are using an Epic Games copy `FactoryGameEGS`.
 If you are using a Steam copy of the game:
 
-1. Use the xref:Development/TestingResources.adoc#LaunchScript[Launch Script] at least once before running the command to create the files required for the Steam game to launch correctly from the command line.
+1. Use the xref:Development/TestingResources.adoc#LaunchScript[Launch Script] at least once before running the command
+   to create the files required for the Steam game to launch correctly from the command line.
 2. Adjust the command to use `FactoryGameSteam` instead of `FactoryGameEGS`.
 ====
 
@@ -142,11 +143,13 @@ which will provide info regarding the dumping process (since `-log -NewConsole`
 You can safely close the Powershell window once you see the console log window,
 although you may wish to keep it open to restart it if it crashes.
 
-Normally the dumper would be run with the `-nullrhi` flag to avoid wasting processing power on rendering the game's menu
-but this argument seems to be broken as of Satisfactory 1.0,
-so it has been excluded from the command.
-The game window will appear and will be exceedingly low FPS and behind in playing sound effects.
-Keep it minimized as the asset dumper operates and focus on the console window.
+The game user interface will never open since we used the `-nullrhi -norhithread` arguments,
+leaving only the console window visible.
+// Normally the dumper would be run with the `-nullrhi` flag to avoid wasting processing power on rendering the game's menu
+// but this argument seems to be broken as of Satisfactory 1.0,
+// so it has been excluded from the command.
+// The game window will appear and will be exceedingly low FPS and behind in playing sound effects.
+// Keep it minimized as the asset dumper operates and focus on the console window.
 
 // The game window itself will never open since the `-nullrhi` argument was used.
 After the game's loading process, you should see a sequence of `LogAssetDumper` messages.
@@ -346,6 +349,9 @@ because they are stored raw in the pak file (not the utoc/ucas) and the automati
 
 [TIP]
 ====
+There may be some files in the CustomAssets list that you don't have in your backup copy of the Starter Project.
+They were probably removed from the game and the CustomAssets list has not been updated to reflect this.
+
 Check the https://github.com/satisfactorymodding/UnrealProjectUpdater/pulls?q=sort%3Aupdated-desc+is%3Apr+is%3Aopen[open pull requests]
 for the UnrealProjectUpdater repository to see if there are any additional CustomAssets that haven't been merged into the project's list yet.
 ====

modules/ROOT/pages/Development/BeginnersGuide/CreateGitRepo.adoc

@@ -144,7 +144,7 @@ https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-d
 
 The custom engine version used in the Satisfactory Modding community has been modified to allow Unreal Engine's Git integration to recognize and work with multiple git repos in a single project.
 
-To enable, navigate to "Tools" > (Source Control heading) > "Connect to Source Control...".
+To enable, navigate to "Tools" > (Revision Control heading) > "Connect to Revision Control...".
 Select Git from the dropdown, then click "Accept Settings".
 
 You can now right click on assets in the Content Browser to view their change history, diff assets, and more.

modules/ROOT/pages/Development/BeginnersGuide/SimpleMod/NextSteps.adoc

@@ -5,17 +5,15 @@ You've reached the end of the getting started guide - congratulations!
 If you're still looking to learn about a specific concept,
 check and see if we have a page on it in the other sections of the documentation.
 
-Once you have a mod you're ready to upload, follow the
-xref:Development/BeginnersGuide/ReleaseMod.adoc[Releasing Your Mod]
-directions to export and upload it for other people to use.
-
-You can also ask questions on the https://discord.ficsit.app[Discord Server].
-
-You may also be interested in {cpp} modding,
-which allows modifying and creating much more advanced game behaviors.
-More info can be found on that xref:Development/Cpp/index.adoc[here].
-
-Consider checking out what mods on ficsit.app have their source code available and
-xref:Development/BeginnersGuide/ImportingAnotherMod.adoc[checking them out in your editor]
-to learn from their code.
-A curated list of open source examples can be found xref:Development/OpenSourceExamples.adoc[here].
+* Once you have a mod you're ready to upload, follow the
+    xref:Development/BeginnersGuide/ReleaseMod.adoc[Releasing Your Mod]
+    directions to export and upload it for other people to use.
+* You can also ask questions on the https://discord.ficsit.app[Discord Server].
+* You may also be interested in {cpp} modding,
+    which allows modifying and creating much more advanced game behaviors.
+    More info can be found on that xref:Development/Cpp/index.adoc[here].
+* Consider checking out what mods on ficsit.app have their source code available and
+    xref:Development/BeginnersGuide/ImportingAnotherMod.adoc[checking them out in your editor]
+    to learn from their code.
+    A curated list of open source examples can be found xref:Development/OpenSourceExamples.adoc[here].
+* Check out resources linked on the xref:Development/UnrealEngine/UnrealLearningResources.adoc[Unreal Learning Resources page]

modules/ROOT/pages/Development/BeginnersGuide/SimpleMod/buildable.adoc

@@ -35,11 +35,19 @@ You can learn more about how holograms work on the xref:Development/Satisfactory
 ====
 
 As you can see in the `Components` pane in the top left, the actor already contains a few components.
-But not any visuals, so, now add a new FGColoredInstancedMeshProxy component in the center of the viewport.
-The build gun uses the origin when targeting the mesh to be built or snapped.
-You can use link:{attachmentsdir}/BeginnersGuide/simpleMod/Mesh_DocBuild.fbx[this example Mesh], the Plantpot of Knowledge, for your buildable.
+These are inherited from the parent class `FGBuildable`.
+
+Note that the building does not currently have any visuals.
+To fix this, add a new `FGColoredInstancedMeshProxy` component in the center of the viewport.
+This component is an optimized version of the base Unreal static mesh component that supports Satisfactory's Customizer painting system.
+To tell it what mesh to display, assign one in the "Static Mesh" field of the component's Details panel.
+Import link:{attachmentsdir}/BeginnersGuide/simpleMod/Mesh_DocBuild.fbx[this example Mesh], the Plantpot of Knowledge,
+which we'll use for this building.
+Use the default import settings when prompted.
 
-This Actor is also where you can define the snapping area and the clearance area, but we won't do that for now. Look to other machines and examples for inspiration as there are several relevant settings to make those behaviors work correctly.
+The build gun uses the origin when targeting the mesh to be built or snapped.
+This Actor is also where you can define the snapping area and the clearance area (mClearanceData), but we won't do that for now.
+Look to other machines and examples for inspiration as there are several relevant settings to make those behaviors work correctly.
 
 == Make it Paintable
 
@@ -116,7 +124,8 @@ That's it! You don't need to register anything else. When the recipe gets loaded
 
 == Trying it Out
 
-If you load up the game now, you should be able to build the Doc Build in game, but it is purely an object that sits there and exists. You should be able to paint it with the paint tool, and it should look roughly like it does in the icon image.
+If you load up the game now, you should be able to build the Doc Build in game.
+You should be able to paint it with the paint tool, and it should look roughly like it does in the icon image.
 
 == Troubleshooting
 

modules/ROOT/pages/Development/BeginnersGuide/SimpleMod/gameworldmodule.adoc

@@ -195,25 +195,28 @@ By giving it a name that includes the mod reference,
 it becomes easier to identify in crash logs
 and helps you tell the modules of different mods apart in the editor.
 
-You will be able to register recipes and other content using this module.
-
 Next, double click on the module to open up its blueprint settings.
 
 To make sure that SML automatically detects and loads our module,
-we must be sure to mark that it is the Root Module via the `Root Module` details field.
+mark it as the Root Module via the `Root Module` checkbox in the Details pane.
 
 image:BeginnersGuide/simpleMod/MakeRootModule.png[Make Root Module]
 
 [WARNING]
 ====
-Make sure that you mark your new Module as the Root via the blueprint details field!
-There can be one Root module per type (Instance, GameWorld, MenuWorld).
-If you don't do this, the module will be silently ignored,
-and the content you create later won't be loaded.
-This mistake won't be apparent until you have some content to test later.
+Make sure to mark your new Module as the Root Module!
+Most content not referenced by a module (or the Content Registration API)
+will be inaccessible and silently ignored by the game.
+
+To assist with catching this mistake,
+the editor performs data validation when you save Mod Modules.
+If you exceed more than one Root module per type (Instance, GameWorld, MenuWorld),
+or have modules of a type but none are marked as Root,
+the module will **fail data validation** and cause an error in the editor
+informing you of what you need to change.
 ====
 
-If you'd like to learn more about root modules, you can read about it on the
+If you'd like to learn more about root modules, you can read about them on the
 xref:Development/ModLoader/ModModules.adoc[Mod Modules] system page.
 
 == Compile and Save

modules/ROOT/pages/Development/BeginnersGuide/SimpleMod/machines/SimpleInteraction.adoc

@@ -3,6 +3,14 @@
 Let's create a simple interaction GUI for our xref:Development/BeginnersGuide/SimpleMod/machines/SimpleMachine.adoc[Item Counter Machine].
 We'll use it to read the current data and to reset the counters.
 
+[WARNING]
+====
+This tutorial assumes you have a basic understanding of Unreal Engine's Blueprint editor interface and Blueprint scripting system.
+
+If you are unfamiliar with this system, please check out the resources linked in the
+xref:Development/UnrealEngine/UnrealLearningResources.adoc#UnrealBlueprint[Unreal Learning Resources section: "Blueprint Scripting"]
+====
+
 [TIP]
 =====
 A completed version of this interaction GUI is included in the ExampleMod in the starter project.
@@ -26,7 +34,7 @@ This guide focuses on the Satisfactory Modding specific portions of creating a w
 
 Check out the following documentation from Unreal as a starting point for learning how to design widgets.
 
-* https://dev.epicgames.com/documentation/en-us/unreal-engine/umg-ui-designer-quick-start-guide-in-unreal-engine#2-displayinghealth,energy&ammo[UMG UI Designer Quick Start Guide: 2 - Displaying Health, Energy & Ammo]
+* https://dev.epicgames.com/documentation/en-us/unreal-engine/umg-ui-designer-quick-start-guide-in-unreal-engine?application_version=5.3#2-displayinghealth,energy&ammo[UMG UI Designer Quick Start Guide: 2 - Displaying Health, Energy & Ammo]
 * https://dev.epicgames.com/documentation/en-us/unreal-engine/umg-editor-reference-for-unreal-engine?application_version=5.3[UMG Editor Reference]
 
 == Retrieving Information from our Machine

modules/ROOT/pages/Development/BeginnersGuide/SimpleMod/machines/SimpleMachine.adoc

@@ -2,6 +2,14 @@
 
 In this chapter we'll create a machine which simply counts the items and types of items that pass through it, outputting them again on the other side. 
 
+[WARNING]
+====
+This tutorial assumes you have a basic understanding of Unreal Engine's Blueprint editor interface and Blueprint scripting system.
+
+If you are unfamiliar with this system, please check out the resources linked in the
+xref:Development/UnrealEngine/UnrealLearningResources.adoc#UnrealBlueprint[Unreal Learning Resources section: "Blueprint Scripting"]
+====
+
 [TIP]
 =====
 A completed version of this machine is included in the ExampleMod in the starter project.
@@ -53,9 +61,8 @@ There is not that much we need to do here.
 The only thing we need to do is to set the PowerInfo on the PowerConnection and configure the target consumption of the `FGPowerInfo` to something like 1.0.
 This controls how much power in MW the building will use to operate.
 
-image:BeginnersGuide/simpleMod/machines/SimpleMachine_Init.jpg[image]
-
-(Logic in the Event Graph)
+.Logic in the Event Graph
+image::BeginnersGuide/simpleMod/machines/SimpleMachine_Init.jpg[image]
 
 == Grab Logic