Log in

View Full Version : What is the location of custom races?


ranisalminen
April 19th, 2022, 18:52
Hi!
I'm n00b user, n00b to this forum :-)

Question:
Managed to make a homebrew race to my campaign in the weekend, but yesterday it was lost. I tried second time as a simple test (uncategorized race), but cannot find it's data anywhere. I searched files both in \AppData\Roaming\SmiteWorks\Fantasy Grounds\campaigns\mycampaign and \AppData\Roaming\SmiteWorks\Fantasy Grounds\modules\mycampaign.mod (zip) file. Can not find it.
Is it somewhere else? I'd prefer to be able back up the file before I redo it, so it won't get lost again.

Cheers,
Rani
Sulimo
April 19th, 2022, 19:19
It depends on if you exported it or not.

If it is not exported, it would be in the campaign you created it in.

If you did export it, it would be in the modules folder (see the file name field below) with the name you gave it. If you did export it, did you make sure to check the box for Races when exporting?

https://i.imgur.com/JO9b84e.png
Zacchaeus
April 19th, 2022, 19:30
If you didn't export it then the data for your race will be in the db.xml file inside your campaign folder at \AppData\Roaming\SmiteWorks\Fantasy Grounds\campaigns\mycampaign (We're assuming here that you are looking for the raw code of the race rather than just the raceitself - which will still be in the campaign you created it in.)

If you exported it then it is as @Sulimo says.
ranisalminen
April 19th, 2022, 19:34
Hi!
Thank you for the quick reply, I found it: In the campaign folder, db.xml, and when exported, in client.xml file in the .mod
I don't know how I lost it in the first place, but now I know how to back it up :-)

Thank you for your help!
Sulimo
April 19th, 2022, 21:36
It's probably best to back up the whole campaign folder rather than just the db.xml, same with the module, back up the whole module file instead of cracking it open and just saving the client.xml.
ranisalminen
April 20th, 2022, 04:48
It's probably best to back up the whole campaign folder rather than just the db.xml, same with the module, back up the whole module file instead of cracking it open and just saving the client.xml.

Yes, you're right.