There will be no future changes to this project, keeping it around for posterity and as reference material. :)

Check out SMAPI for the main Stardew Modding API.

Note that this only applies to those wanting to develop the API. Mod developers do not need to go through this and the installer provides you with prebuilt packages you can use for mod development.

(This isn't nessecary unless you want to compile the SMAPI compatibility extension.)

After cloning the repository, the first thing you'll need to do is download the SMAPI submodule. To do this, execute the PopulateSubmodules.bat file, or use the following command:

git submodule update --init --recursive

Next we need to prepare a folder so the project knows where to locate Stardew files to inject into:

• Create a folder in the project root directory called 'Staging'.

• Create a folder in this new Staging folder called 'Windows'.

• Copy your entire Stardew Valley install, including dlls, executables, and the Content folder, into this directory.

• If you wish to also build a Linux compatible version, create a folder called 'Linux' in the new staging folder and copy a Linux version of the game to it.

Now open the project's solution file. Note that if you do not have Sandcastle or XNA Game Studio installed, you'll receive an error about two of the projects failing to load, this can be ignored unless you are wanting to generate documentation (Sandcastle) or compile the shader test mod (XNA Game Studio).

Once the solution is open, the Stardew Farmhand executable can be compiled by Rebuilding the BuildFarmhandFinal project.

Because of how the project is structured, there are 3 tiers of dependencies in the core project.

• Tier 1: The first tier includes projects without any dependencies. This tier consists mostly of Farmhand.csproj, and is compiled into the Teir 2 dependency by the BuildFarmhandIntermediate project.

• Tier 2: These projects (Libraries/Farmhand{X}) depend on the build output from BuildFarmhandIntermediate (StardewFarmhand.int1.dll). These libraries build upon modifications made by the Tier 1 changes, and are themselves a part of Stardew Farmhand after being compiled into the Tier 3 dependency, the final executable, by the BuildFarmhandFinal project.

• Tier 3: Tier 3 libraries are ones which depend on the final Stardew Farmhand.exe, these include things such as all the mods and the SMAPI Extension project.

Because of these distinct dependency layers, changing a project in a lower layer wont be reflected in one in a higher level until you have rebuilt the layer. For example, if you add a new class in Farmhand that you want to be accessible in FarmhandGame, you need to have rebuilt BuildFarmhandIntermediate so it is in the intermediate DLL it actually references. If you needed to access our example class from a mod, you'd need to rebuild BuildFarmhandFinal so it's in the final executable which the mod references.

Because MSBuild cannot track dependencies properly on projects such as this, you'll need to Rebuild the BuildTask projects, so that the build commands that handle packaging are actually executed.

To build the project on Linux, follow the steps above, constructing only a Linux staging folder instead of a Windows folder.

There are a few issues which are only present in the Linux build:

• When opening the project in an IDE (MonoDevelop), you will get a warning about the Farmhand (Sandcastle) and VignetteMod projects. Just click to ignore these issues. You will not be able to build either of these projects but neither are vital.

• MonoDevelop will frequently just cease to work with the project, and cause random compile errors. If the error reports that it is due to an internal MSBuild error, clean the solution and build again; for other errors relating to undefined references in the project files, restarting MonoDevelop resolves these. Please let me know if you find an IDE which works better with the project!

These projects create a MSBuild-able flow for the project, so manually patching is not required.

Packages Farmhand Core into Stardew and applies the appropriate hooks. This is the project you should click "Rebuild" on when altering the engine, as it will force all builds to trigger in the correct order.

Packages the projects dependent on the results of BuildFarmhandIntermediate into Stardew and produces the final Stardew Farmhand.exe

Compiles documentation using SandCastleFileBuilder into HTML

Contains common patcher code, and is the core library responsible for modifying the Stardew executable.

Thin libraries used to ensure the correct libraries are used for each injection pass.

A command line interface used for running the patcher. This will not be included as a public installer and instead is just used as a part of the build process.

This is the distributed Farmhand installer. It currently uses WPF but will soon be replaced by platform specific installers.

The core code which is injected into Stardew. Most of the heavy lifting and API functionality takes place in this library, with second-pass libraries only being used for things which rely on the changes caused by this library.

Contains NPC and Monster related API functionality.

Contains overrides for the Game1 instance and overrides for certain item classes.

Contains a modified version of Entoarox's UI framework, as well contains additional UI enhancements such as the mod configuration menus.

Far too many to list, the mods packaged serve a both examples and integration tests to ensure features continue to work.

Just serves as an entry point for me to step through and debug Stardew Farmhand. This should be set as your startup project when not debugging the build process. A benefit of this is that since Farmhand itself does not invoke a console window yet, console output will be redirected to the debugger's window.

Prepares a number of data-defined packages for inclusion in the installer.