satisfactorymodding / SatisfactoryModManager

# Satisfactory Mod Manager
Mod manager for Satisfactory.
Handles all the steps of installing mods for you.
Implemented in Wails using Svelte and Skeleton.
## Installation and Usage
Check the modding documentation
for installation and usage instructions.
## Features
* One-click install of any mod
* Automatically downloads the dependencies of any mod
* Mod update notifications
* Mod profiles and sharing of them
* View the mod description in the app
## Reporting issues
If you have any questions or run into issues, you can ask in the
Satisfactory Modding discord
for quicker responses than the GitHub issues.
If there is any error message, please include it along with the generated debug info zip.
## Troubleshooting
Check the modding documentation
for common issues and their solutions.
* Profile and installation records are located in `%APPDATA%\ficsit\`
* Downloads are cached in `%LOCALAPPDATA%\ficsit\downloadCache\`
* Logs are stored in `%LOCALAPPDATA%\SatisfactoryModManager\logs`
## Development
### Dependencies
* Go (the version in the Setup CI action `go-version`)
* pnpm
* nodejs (the version in the Setup CI action `node-version`)
* Wails (to install, execute the `run` command from the Setup CI action's `Install Wails` step)
* IDE of Choice. Goland or VSCode suggested.
### Configuration
If you want to point to the SMR staging API instead of production, edit:
* `main.go` to set `api-base` to the staging api (`https://api.ficsit.dev`)
* `frontend\.graphqlrc.yml` to set `schema` to the staging api (`https://api.ficsit.dev/v2/query`)
If you want to use a local build of ficsit-cli,
use the Go `replace` directive (and do not commit the change),
for example:
 [code] 
### Development Server
The development server will hot reload whenever you make changes to the Go or Typescript code.
 [code] 
Upon successful launch of the development server, the application will open automatically.
The command line output will also include a localhost URL you can visit in your browser if you wish to utilize browser developer tools for debugging.
Make sure you don't already have a copy of the application running or the command will silently fail.
Although `wails dev` should run these commands for you under normal circumstances,
you may need to run `pnpm graphql-codegen` in the `frontend` directory to update the code generated from the SMR API,
or run `pnpm translations` to update the translation data.
### IDE Configuration
Make sure that your IDE is connecting with the frontend's installation of ESLint to get the best experience.
VSCode users, a preconfigured workspace is provided in `.vscode/`
that allows editing both Go and Svelte files
while maintaining correct ESLint functionality.
### Building
 [code] 
To build a version that includes browser devtools (extending production debugging capabilities),:
 [code] 
### Linting
Install `golangci-lint` via the directions in the Golangci-lint documentation,
but make sure to install the version specified in `.github/workflows/push