Troubleshooting Swifty 2.X.X Legacy Build

This is a troubleshooting FAQ for Swifty 2.0 Builds. This guide is not compatible with 3.0 Builds, For that see the Swifty 3.0 FAQ here

Log files

Swifty legacy log files can be found in your Appdata. To easily find this folder type %Appdata% into your windows search bar. This will put you into your Appdata/roaming folder.

The full Path to the swifty log is as follows: C:\Users\username\AppData\Roaming\Swifty

You will then see a text document titled swifty. This is your log file! Simply open it in notepad to read it. If you do not know what to look for yourself, toss the file straight into our tech support channel in discord.

Cache folder

This folder holds files for swifty to know the status of each mod it has downloaded. If you have an error that is the result of a corrupted file, its best to clear this cache to ensure it is redownloaded.

again this is found in appdata. The full path is: C:\Users\username\AppData\Roaming\Swifty\Cache

inside you will see subfolders for every repository you have.

Temp directory

Swifty uses the temp directory to download the files it needs, and then patch them into the existing folders. Ensure you have enough space on the drive you chose for this, as sometimes it can temporarily use several gigabytes of space.

If a download suddenly stops, you may need to clear these files to ensure no corrupt files are moved into your mod directory.

You can find where you set this directory to under the wrench icon.

Error messages

Ran out of file

This error is a catch all. The most common causes are as follows:

Too many parallel downloads, set this setting to 1 or 2. Especially if you are on wifi.

unstable, but not totally lost connection. This results in a corrupt file that you must check your log to find. You can then delete that file, clear your temp and cache folders and try again.

Ran out of memory

This means you either do not have enough space at your install directory, or not enough space at your designated Temp location.

System exception: failed to download

This means the connection to the server was lost at some point. Restart your download and try again.

System nullreference

This is the result of clicking "New" instead of "Import" when inputting the Repository information.