Mod Browser

[joshuaskelly]

Summary

Support in-game browsing and installing of mod content.

Children

• ModSource Design #223 ModSource Design

[joshuaskelly]

Notes

I'm thinking that the ModManager should have a list of ModSources from which it can find content. The ModSources are responsible for listing available mods and acquiring them. It might be useful for a source to provide it's own UI for the browser.

LocalFileSystemModSource

This is a basic mod source that looks at a specified directory. The functionality would largely be similar to the existing behavior. It lists all mods in the directory and allows you to enable/disable them.

GithubRepoModSource

This mod source references a url that point to a GitHub repo. It will list all available mods in the repo and will download mods to the local filesystem.

[PythooonUser]

And as you mentioned this could be easily configured using a modsources.dat file with the following example content:

[
    {
        "class": "com.fqn.modsources.LocalFileSystem",
        "root": "C:\\Some\\path"
    },
    {
        "class": "com.fqn.modsources.GitHub",
        "uri": "https:\\\\www.github.com\\delver-community-mods"
    }
]

[PythooonUser]

I feel like the decision of enabling/disabling a specific mod should be the responsibility not of the mod source but the mod manager. What do you think?

[joshuaskelly]

That is an interesting thought.

Also we are already serializing the modmanager to disk, so it doesn't need to be a separate.dat file.

[PythooonUser]

The next step would be to copy over the existing functionality into the LocalFileSystemModSource class.