Utilizing ModInstaller for Other Games (MICOverride)

(NOTE: This applies only to an unreleased-as-of-yet version of H3VRMI. The current version, v1.0.2, can only replace the Database location.)

While H3VRMI is first and foremost designed for H3VR and is only expected to be used for H3VR, ModInstaller has enough leeway to be used for other videogames using a system called MICoverride.

MICoverride is a function in H3VRMI that is the first thing called upon startup of H3VRMI. If H3VRMI detects a MICoverride.json file in the same folder as it is located in, it will boot up the MICoverride's information.

NOTE: While H3VRMI is designed to not allow any serious damage, still, please do not download and use MICoverrides which you do not trust.

To make a MICoverride is very easy. It can override three variables: The game folder name, the ACF location, and the database location.

Here is an example of a MICoverride.json:

{
	"DatabaseInfo": "https://raw.githubusercontent.com/Frityet/H3VRModInstaller/master/src/Backend/JSON/Database/modinstallerinfo.h3vrmi",
	"RootFolderName": "H3VR",
	"ACFname": "appmanifest_450540.acf"
}

The database location is, of course, meant to provide all the available mods to a game, and the game folder and ACF location are to locate and find a game.

A database is recommended to be made using GitHub. As an example, here's the database info for H3VRMI. To understand how a database works, i recommend you read the mod file system wiki page.

The RootFolderName is the foldername of the game in the steam files. In this case, H3VR.

The ACFname is the name of the ACF file used to find data about the game, which is formatted as appmanifest_[GameID].acf . You can find the gameID using steamDB and searching up the game's name.