⚠️ DEPRECATION NOTICE ⚠️

This template has been deprecated, we recommend you check out the getting started page of the OWML docs as that guides you through how to use the new template.

Outer Wilds Mod Template

Use this project as a base for new Outer Wilds mods.

• Prerequisites
• How to use this template
• Editing manifest.json
  • fileName
  • author
  • name
  • uniqueName
  • version
  • owmlVersion
• Editing ModTemplate.csproj.user
• Updating OWML
• Building the mod
• Releasing the mod
  • Increasing the version
  • Pushing the code to GitHub
  • Creating a file for the release
  • Uploading the release to GitHub
  • Adding your mod to the database
• Troubleshooting

Prerequisites

• An IDE that supports .NET, like Visual Studio (download Visual Studio Community here);
• Outer Wilds Mod Manager (get it from the Outer Wilds Mods website);
• OWML installed in the Mod Manager;
• A GitHub account (required for forking the repo and for releasing your mod to the public);

How to use this template

1. Generate your repository from this template;
2. Clone your new repository to your machine;
3. Edit ModTemplate/manifest.json (see Editing manifest.json for more info);
4. Edit ModTemplate/ModTemplate.csproj.user (see Editing ModTemplate.csproj.user for more info);
5. Open ModTemplate.sln in Visual Studio (double clicking the .sln file should do the trick);
6. Start writing your mod code in ModTemplate/ModTemplate.cs (Read OWML's docs to learn what you can do).
7. Build the mod;
8. Release the mod;

Editing manifest.json

Use any text editor for editing this file (Notepad or whatever). The file ModTemplate/manifest.json should look like this:

{
  "filename": "ModTemplate.dll",
  "author": "AUTHOR",
  "name": "MOD_NAME",
  "uniqueName": "MOD_UNIQUE_NAME",
  "version": "0.1.0",
  "owmlVersion": "0.7.3"
}

Edit each entry with the correct information for your mod:

fileName

Visual Studio will use the project's name for the dll, so this will usually be [ProjectName].dll. Since this template's project name is ModTemplate, fileName will be ModTemplate.dll. Remember that if you change your project's name, you'll have to change this entry too.

author

Your beautiful name.

name

The human-readable name of your mod, which will show in the Mod Manager.

uniqueName

The unique ID of your mod. It's recommened to write it in the form YourName.ModName, i.e., Raicuparta.ModTemplate for the ModTemplate mod created by Raicuparta. Can be anything really, as long as it isn't already taken by another mod, so it is best to use namespacing to reduce the liklihood that anyone else has used the same name. You can search for your uniqueName in the mod database if you wanna make sure it isn't already in use.

version

The version number of the mod. It's important that this version number is consistent with the versions used in GitHub releases. (see Releasing the mod for more info);

owmlVersion

OWML version used for your mod. Only used to show a warning to users using an OWML version different than this. Just make sure that the version here is the one installed in the NuGet packages (see Updating OWML for more info);

Editing ModTemplate.csproj.user

Use any text editor for editing this file (Notepad or whatever). The file ModTemplate/ModTemplate.csproj.user should look like this:

<Project>
  <PropertyGroup>
    <OutputPath>OUTPUT_PATH</OutputPath>
  </PropertyGroup>
</Project>

Here you can replace OUTPUT_PATH with the path where your mod files will live.

Example: $(AppData)\OuterWildsModManager\OWML\Mods\Raicuparta.ModTemplate.

To make your mod automatically show up in the Outer Wilds Mod Manager every time you build it, follow the format {MODS_DIRECTORY}/{MOD_UNIQUE_NAME}.

To get your {MODS_DIRECTORY}, open the Outer Wilds Mod Manager and click the "Mods Directory" button on the top right of the "Mods" tab. The {MOD_UNIQUE_NAME} part of the path is just the uniqueName that you defined in your mod's manifest.json.

Editing LICENSE

You can also use any text editor to edit this file. Change the copyright date and name on line 3 to your own (you can also use your online username instead of your real name).

Updating OWML

It's important to keep OWML up to date in your project. In Visual Studio's Solution Explorer, right click "References" and select "Manage NuGet Packages...". In the "Installed" tab, find OWML and press the update button, if it's available (blue circle with a white arrow pointing up). After updating, make note of the new OWML version number. Update your manifest.json file with the latest OWML version (see Editing manifest.json for more info).

Building the mod

Before attempting to build the mod, make sure you've edited ModTemplate.csproj.user, and manifest.json with the correct info. After that's done, go to Visual Studio, open the "Build" menu at the top, and select "Build Solution". If all goes well, your mod should immediately show up the the Mod Manager. You can now press "Start Game" in the manager, and the game should start with your mod enabled (as long as your mod has the checkbox set to enabled).

Releasing the mod

After you've written the code for your mod, you can release it and make it available for download.

Increasing the version

Always increase your mod's version in manifest.json every time you publish a new release. For instance, change it from "0.1.0" to "0.2.0".

Pushing the code to GitHub

If you forked the ow-mod-template repository as per the initial instructions, you now have your own version of this repository in your GitHub account. Your GitHub username will displayed as the mod's author, and the description for the mod will be fetched from the repository description on Github. The README.md file will be your mod's readme, so update it with instructions on how to use your mod. There's a button in the Mod Manager that will point to your mod's readme once you publish it.

Creating a file for the release

In the Mod Manager, find your mod, click the three dots menu button, and select "Show in explorer". You should see the directory to where your mod was built. Create a zip that includes all these files. This will be your release. Has to be zip specifically.

Uploading the release to GitHub

1. Go to the releases page of your repository (GitHub should show you a link to this page on the right side of the repository's page). Press "Draft a new release".
2. In the "Tag version" field, insert the same mod version that you included in manifest.json. It's very important that the release tag version is the same as the version field in the manifest.json inside the zip, otherwise your mod will always show as outdated in the Mod Manager.
3. Release title and description are up to you.
4. Add your zip to the release as a binary by drag & dropping the file to the release assets area (or just click "Attach binaries by etc etc" and select your file). Make sure you only upload one zip file, since anything after the first one will be ignored by the mod database / mod manager.
5. Press "Publish release".

Adding your mod to the database

To make your mod show up in the Mod Manager and in outerwildsmods.com, you need to add it to the database. Click here to request for your mod to be added to the database. Learn more about the Outer Wilds Mod Database in the ow-mod-db repository.

Troubleshooting

A NuGet package called OuterWildsGameLibs is used to get references to the game code. If a game update has been released and this nuget hasn't been updated yet, you might need to reference the game libraries manually. More information on the ow-game-libs repo.

If you open ModTemplate/ModTemplate.csproj, you'll find references to $(OwmlDir) and $(ModUniqueName). The value of these variables is read from ModTemplate/ModTemplate.csproj.user.

$(OwmlDir) and $(ModUniqueName) are used in the post-build events, to copy the built mod files (and static files like manifest.json and default-config.json) to the mod directory in "$(OwmlDir)\Mods\$(ModUniqueName)". If you are having problems with post-build events, you can edit them manually in Visual Studio (double click Properties in Solution Explorer, select "Build Events").

You'll also find references to $(TargetPath), which is the path to where Visual Studio places your mod dll after building, and $(ProjectDir), the path with your mod's Visual Studio project. These don't need to be defined manually, they always exist.