Posts by GhostAssassinLT

Aaaahhhhh....

I'm not that used to GitHub, so I didn't know where the download button was.

I found that I could download the files by clicking on the Code button.

It sure helps if you look at everything on the page... LOL

Anywho, thank you very much for your help. Much appreciated!!!

I know it shouödn't be that hard to install the mod. I've played SPT for a couple of years now.

However, when I download the files via the link above I get a bunch of .cs-files and a .csproj, no .dll-file.

How do I get this mod to work?
I've used it with previous versions, but can't get it to work with 3.11.

For 3.10 I have a .dll-fix in BepinEx/plugins, but there is no .dll-file in the folder when I unzip it and installing via SPT Mods Installer doesn't work either.
I would love to get it working as it's been one of my favorite mods for SPT.

Quote from Jomfaca

I've accidentally updated to the latest version: 0.15.0.3.32280 (29 August 2024)

Is there anything like this for my version of the game?

You can always try the installer. It worked for me with 32197.

You are the man Sir!

I just managed to get 3.9.8 installed using the installer even though I had to patch my EFT to version 0.15.0.2.32197 because I opened my launcher...

Will have to download and install all mods later tonight as we're going out for dinner to celebrate my wife's birthday earlier this week.

The curse of a new computer and a terminated email address...
BSG took so long to agree to change the email address for my account that the wipe happened...

Oh well, I guess I'll have to give PvE a try or settle for either Hogwarts Legacy or Black Myth Wukong until the gods of SPT bless us with a new version...

Any ideas as to why I get an error message in the server window when I launch the server saying:

[gunsmith] Preset items are not defined for preset: [object Object]

New install of SPT 3.8.3 with gunsmith as the only mod installed.

Also, the downloaded version says version 2.0.7 even though it says 2.0.8 on the download page.

Update: Reverting to v2.0.7 removed the error from the server.