A module base is an abstract class from MoonstormSharedUtils, as their name implies, they're a type of class that acts as a Module for handling ContentBase classes, The module base system works with static methods for handling the respective content classes fed into them, however, for adding new ContentBase classes, one requires to inherit from the ModuleBase itself. (Which is why they're abstract in the first place)

For simplicity and less work, MSU also comes with two SubClasses of ModuleBase.

A ContentModule is a type of ModuleBase which's purpose is to add UnityEngine.Object inheriting assets to your mod's SerializableContentPack, most if not all ModuleBases provided by MSU inherit from ContentModule.

public abstract class ContentModule<T> : ModuleBase<T> where T : ContentBase
{
    public abstract R2APISerializableContentPack SerializableContentPack { get; }

    protected bool AddSafely<TAsset>(ref TAsset[] contentPackArray, TAsset content, string correspondingArrayName = null) where TAsset : UnityEngine.Object
    {
        if (contentPackArray.Contains(content)) //Content already in the contentPack for whatever reason? return true;
        {
            MSULog.Warning($"Content {content} was already in {SerializableContentPack}'s {correspondingArrayName ?? content.GetType().Name} array!\n" +
                $"MSU automatically adds the content piece to its corresponding array in initialization, do not add it beforehand.");
            return true;
        }

        HG.ArrayUtils.ArrayAppend(ref contentPackArray, content);
        return true;
    }
}

Unlike ContentModule, the BundleModule is a subclass of ModuleBase which's main work is to handle specific assets that are not related to ContentPack assets, unlike the ModuleBase and the ContentBase, a BundleModule by definition does NOT handle a ContentBase class by definition.

public abstract class BundleModule : ModuleBase<ContentBase>
{
    public abstract AssetBundle MainBundle { get; }

    protected sealed override void InitializeContent(ContentBase contentClass)
    {
        throw new System.NotSupportedException($"A BundleModule does not have a ContentBase by definition.");
    }

    protected IEnumerable<T> GetContentClasses<T>(Type excludedType = null) where T : ContentBase
    {
        throw new System.NotSupportedException($"A BundleModule does not have a ContentBase by definition.");
    }

    public TObject Load<TObject>(string name) where TObject : UObject
    {
        return MainBundle.LoadAsset<TObject>(name);
    }

    public TObject[] LoadAll<TObject>() where TObject : UObject
    {
        return MainBundle.LoadAllAssets<TObject>();
    }
}

MSU comes bundled with a total of 14 ModuleBases, 13 of which inherit from ContentModule and one which inherits from BundleModule

The provided module bases by MSU will usually contain the following properties and utilities:

• an abstract property of either R2APISerializableContentPack or Assetbundle, depending if the class is a Bundle or Content module
• The following only apply to ContentModules
  • A ReadOnly collection that's used to access the initialized pieces, this only apppplies to ContentModules
  • An action that gets invoked when the ReadOnly collection of a ContentModule gets initialized.
  • A method for obtaining all the ContentBases the ContentModule handles from your assembly, this method will also create instances of them using the Activator class.
  • A method for adding and initializing the content base.