Test on a new game instead of on a savefile. doc file), there might be invisible characters that the game considers invalid, so be careful with that. If you copy-paste text from some document (such as a. It's also common to forget to prefix the mixintos and overrides with the mod's namespace.
You can also open your mod with SHED and it will tell you if something's pointing to unexisting files. They might have some wrong letter and therefore they reference something that doesn't exist, or you forgot to prefix your aliases with the correct namespace in your files. Search for typos in your aliases, or in your localization strings. This tool will tell you the differences even if the key-value pairs are in different order, it's good for checking if you've missed some key or value. You can also compare your JSON files with other files from the game with JSON Diff. This will tell you if you had any missing or trailing commas, which is a common typo that will make the game not read your files correctly. If you had something wrong in your manifest, it might get marked as invalid or outdated in the Mods menu, and the game won't load your mod. Make sure that your mod is enabled before starting a game. You can also output text to the stonehearth.log from within your mod's Lua files. If there's some file that couldn't be loaded properly, it will be mentioned in the log (sometimes errors will only appear inside the log, instead of popping up in the game). It is inside the folder where Stonehearth is installed, and it gets overwritten every time you run the game.
While modding it is pretty common to break things accidentally, so here are a few tips for when you don't know why something's not working as intended: