Modot is a mod loader for applications made using Godot, inspired heavily by RimWorld's mod loading process.

Its API is aimed at allowing creators to easily modularise their Godot applications, create and deploy patches and DLCs, and let users expand the functionality of their applications.

• Load mods with resource packs, XML or JSON data, and C# assemblies or GDScript scripts at runtime
• Sort mods using load orders defined partially by each mod to prevent conflicts
• Patch XML data of other loaded mods without executing mod code
• Optionally execute mod code upon loading
• Load mods individually, bypassing load order restrictions

A more detailed explanation of all features, instructions on usage, and Modot's C# and GDScript API differences can be found on the wiki.

• C#

  Modot is available as a NuGet package.

  Simply include the following lines in a Godot project's .csproj file (either by editing the file manually or letting an IDE install the package):

  <ItemGroup>
      <PackageReference Include="Modot" Version="2.0.3"/>
  </ItemGroup>

  Due to a bug in Godot, the following lines will also need to be included in the .csproj file to properly compile along with NuGet packages:

  <PropertyGroup>
      <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
  </PropertyGroup>

• GDScript

  Currently, GDScript lacks a proper package management system, making it difficult to distribute Modot via a package manager.

  As such, the easiest way to install Modot for GDScript is to simply copy all files and directories under the GDScript directory and add them to the desired Godot project.

A complete walkthrough on making a simple game using Modot is available on GitHub.

Modot includes the ability to execute code from C# assemblies (.dll files) and GDScript scripts (.gd files) at runtime.
While this feature is immensely useful and opens up a plethora of possibilities for modding, it also comes with the risk of executing potentially malicious code.

This is unfortunately an issue that has no easy solution, as it is fairly difficult to accurately detect whether an assembly or script contains harmful code.

As such, it is important to note that Modot does not bear the responsibility of checking for potentially malicious code in a mod.

However, it does provide the option to ignore a mod's assemblies or scripts, preventing any code from being executed.
Along with the ability to load mods individually, this can be used to ensure that only trusted mods can execute their code.

Another way to prevent executing malicious code is by restricting the source of mods to websites that thoroughly scan and verify uploaded user content. As mentioned earlier though, it is not Modot's responsibility to implement such checks.