#nedlaness migration
1 messages ยท Page 1 of 1 (latest)
Cool, gonna drop us in a thread here.
Do you know how to open up your userdata folder?
Yes
Okay. What we're going to do is a series of tests to narrow down which database(s) are the problem.
Open up your userdata, go into Data/worlds/ and a problem-world's folder, then into the data folder in there.
If you see a bunch of bare files in there (ending in .db if you can see their file endings), delete those. These are old v10-era databases that we don't want interfering.
There should otherwise just be a bunch of folders, like actors, items, etc.
only folders
Coolcool
Now a sequence of steps that we're going to repeat:
- Close Foundry.
- Pick one of those folders, and rename it with
-temp. So, say,messagesbecomesmessages-temp. - Launch Foundry, try launching the world. If the world launches, then that folder you just renamed had the problem in it, and we can stop.
- If the world still gets stuck on the migration, cancel it, and return to step 1, repeating with a new folder.
Is there any folders that will likely be more problematic or I can do it in any order?
Any order is fine.
The world launches without issue, with just the actors folder renamed?
yes
Welp, nailed it in one, good stuff ๐
So, now we move on to phase 2.
(Assuming at this point that you want those actors in this world, and aren't okay with just not having them any more.)
Yes, I want to keep them or my players will kill me ๐ฅบ
haha, fair
Okay, zip up the actors-temp folder (this is the one with all your actual data in it), and drop that zip file in here. If it's too large to drop here, DM it to me.
Thanks! Now I throw a ping at @golden rose, who's our forensics expert. When he's got a chance, he'll dig into this and see if he can nuke the bad data.
I'll take a look in a bit, will be leaving work in 20, then heading home.
Right, I've cleared out the bad data. I will strongly recommend sticking to modules that are listed on the Foundry site to avoid issues like this in the future.
Thank you very much!