View Full Version : Deadlands configuration. What am I doing wrong?

January 26th, 2012, 18:29
Kinda new to this and I'm a bit confused here.

I have:

- Savage Worlds V3 (GM and Player Guide)
- Deadlands Player Handbook
- Deadlands Marshal Handbook

However, I think i'm missing the ruleset. How do I work in things such as the colored poker chips (Benny replacements)? Also stats like Grit are absent from character sheets.

January 26th, 2012, 18:36
Have you enabled the Deadlands Extension?

January 26th, 2012, 18:38
I don't have any extensions for my Savage Worlds. (Also checked updates for FG just in case)

I recently bought and installed:

Deadlands Reloaded: Marshall's Handbook and Extension (version 1.10)


Deadlands Reloaded: Players Guide (version 1.10)

I have the rulebooks when I load up FG. However, I don't see any extensions for my Savage Worlds when I go to create a game.



January 26th, 2012, 19:00
That's the problem then no extension... not sure why though.

I'd try re-running the .exe file you got.

January 26th, 2012, 19:04
Hmm well I tryed reinstalling both a couple times and still nothing. After a little bit of file snooping I found DeadlandsReloaded1.1.0.ext in my extensions directory. So it is there.

I'm gonna try a quick reinstall of FG and see if that affects anything.

- Redownloaded and reinstalled FG
- Updated Client
- Closed FG, Redownloaded and reinstalled both deadlands .exes
- Still no positive results.

(Using an ultimate user license if that has a chance of changing anything)

January 26th, 2012, 19:08
Right in that case what is the name of the Savage Worlds Pak file?

January 26th, 2012, 19:14



January 26th, 2012, 19:18
Sorry did not make myself clear.... In either the rulesets folder or the Fantasy Grounds II installation folder (where the actual .exe files are), there should be a file name Savageworlds3.pak

If it is not called that that can cause this problem

January 26th, 2012, 19:19
Hang on type /version in the chat window

January 26th, 2012, 19:27
EDIT: Typed version got 3.0.8

Wasn't too sure so I just took a picture of everything for visual reference.

App Data Main Folder

App Data Ruleset Folder

FG2 Install Directory

January 26th, 2012, 19:31

You need to be running Savage Worlds 3.2 (latest version)

Open up that rulesets folder and move out any folder in there called Savage Worlds (keep it just in case)

Assuming you have got the updated 3.2 version installed (if not you need to get the free update), look in (assuming normal install) C:\program files\Fantasy Grounds II\ (if you are running 64 bit windows the folder will be program files (x86) )

Check that there is a SavageWorlds3.pak file.

Failing all that (and save me typing) PM a Skype name and I'll "call" you if you want :)

January 26th, 2012, 19:38
Nevermind figured it out. Was a bit tough to find the link haha. Cheers! Let's see if it works.

EDIT: Works out great. Thanks Dos : ) Such a simple problem, with such a simple solution. Seems to be how it is most of the time with anything PC related.

Add me on skype as Rystrial though. I've never used savage worlds, but I hear heard good things about it. I'll probably get more savage world accessories. I'm not sure what to get though. There's a lot of stuff (Like 8 pages worth)

January 26th, 2012, 20:11
No problem! Happy to help.

If you haven't already watch my videos and if you have any questions please feel free to ask me:D

January 26th, 2012, 22:14
We really ought to have got the SavageWorlds 3.2 (or even 3.1 !) installer to remove that SavageWorlds directory from the rulesets directory...

It didn't use to cause a problem, but since FGII v2.8, directories take precedence to PAK files, so I suspect quite a few people were "downgraded" to SWEX v3.0.8 without realizing.

TL;DR - Users should delete the SavageWorlds3 folder in the rulesets directory - it's stops the new shiny version working

Hope you enjoy DL:R / SWEX - more goodies from me coming out in 2012...

January 28th, 2012, 18:43
Maybe an *option* to remove it. I always hate to have an installer remove things just in case the user had customized files or anything. A simpler, manual solution might be to simply call out attention to this in the instructions portion of the installer.