- Download and unzip the latest FNIStash release. You can unzip it anywhere on your system you like, but keep the files together.
- Launch FNIStash by double clicking the “Launch FNIStash.bat” file. A console window will pop up and FNIStash will load in your browser window.
- When you are done with FNIStash, close your browser window and enter Ctrl+C in the console (possibly twice) and choose to terminate the batch job. Alternatively you can leave the FNIStash console window running in the background and connect to it with your browser at anytime by navigating to localhost:10001.
If you play TL2 through Steam and play softcore, the default configuration will likely work for you. If not, you can edit the configuration file at
to point FNIStash to the appropriate locations for your system.
First Time Start Up
When FNIStash is started for the first time, it will create the following items within AppData\Roaming\FNIStash\
- Backend.conf – FNIStash configuration file.
- fnistash.db – SQLite database of registered items.
- Backups – Directory of automatic backups. At most 10 backups are retained.
- Export – Directory where exported database shows up.
- FailedItems – Items that FNIStash is unable to parse are saved here so they are not lost.
- GUI – Directory containing all GUI assets.
- Import – Directory used for importing items.
NOTE: starting in release r1.4, you can optionally specify the location of the fnistash.db file. This allows you to place the DB file on a network location and share with a friend, but only one of you can use FNIStash at a time.
At first time startup, FNIStash extracts all necessary GUI assets from the TL2 PAK file and writes them to disk. This takes several minutes, even on a fast machine.
If you’d like to run separate instances for FNIStash, such as one for softcore and one for hardcore, just add a keyword as a second argument to the FNIStash launcher. For example you can edit the launcher .bat file like so
start http://localhost:10001 FNIStash Hardcore
and FNIStash will start up looking for the “Hardcore” instance. You must still edit the configuration file to point to your desired locations for this instance.