Manual System Transfer for Saves/Content

Ichii Giki · Feb 9, 2016

@WolfHeroEX Did you transfer the NAND files AND the SD card files to the new Emunand/SD card? If you didn't transfer everything, then your saves wouldn't show up. You also have to make sure you have the matching update to your saves for MiiPlaza to work. I can attest that this process worked for me and I was able to retain all my Miis/MiiPlaza data.

Brunho · Feb 15, 2016

Thanks for your tutorial. I plan on using this to restore the Friends, Mii and MiiPlaza data from my SysNand to my EmuNand. Can I just extract the movable.sed and these folders?

00010026 - Streetpass (active games)
00010032 - Friends
00020096 - Friend List
00020217 - Mii Maker
00020218 - Mii Plaza

Or should I extract and inject all the folders you described?

TheGlow · Feb 15, 2016

I had gotten some new 3dsxls and for some reason I dont know why, I had done a system format on the 2DS's to free up the NNID.
So I realized I couldnt link the NNID so I ended up restoring the 2ds nands and then did a system format.
Somewhere in here it seems to have broken the mii plaza and friends lists.

So for my 2ds and n3dsxl I have the emunand dumps, xors and created mountable images.
I just wanted to confirm this will do what I hope and restore those apps and data. On mine I only played a little MH4U so I can just savedatafiler and restore that.
Does this process have it where it looks for the same Nintendo 3DS\id0\id1 folders and what not?
Would all those installed cia's come back up? I only put a few in as it takes a while but a straight copy to SD card to restore would be great.
I think thats the title.db info.
I have no valid eshop purchases on mine and the 2nd set of ds's was just free dls like netflix, youtube. it had mariokart7 on it but I already grabbed a cia version of that. I'm not even sure if that was associated to the NNID at all or just that 2DS.

As it stands the n3dsxls already have the NNID moved over. That's whats caused me problems before, so I have that out of the way at least for now.

Edit: Ok, it looks like its good. It still didnt have the NNID on the new emunand, so I restored the previous emunand onto a spare sdcard, did system format to free it up, then loaded up the new emunand and linked the NNID and it appears to be good now.
Definitely took a while. Im guessing moving the ticket.db would have let all the old games load up, but id rather not take the chance on it restoring something odd.

TheGlow · Feb 17, 2016

It seems there were some side effects. My daughters friend code changed. So the friends list is there but no one shows as online now since its not the same on their end. I manually added her on my side and confirmed I still had her old one and she had it written down, and that wasnt it.
Also the Mii that showed for her she said is older and not showing what she has on the screen herself.
Any ideas on how to restore the friend code too or is that too late?

Ivan Garcia · Feb 26, 2016

I have decrypted all my SD saves content. I'm trying to reencrypt with my new movable.sed but it doesn't work.
Do you know how can i transfer all my saves from my old console (was dead) to my new one?

kinder_bueno · Feb 29, 2016

Ichii Giki said:
[Tutorial] "Manual System Transfer" for Saves/Content

DISCLAIMER: I AM NOT LIABLE FOR ANY LOSS OF DATA OR DAMAGE TO YOUR SYSTEM! You proceed with this tutorial at your own peril!
PLEASE MAKE BACKUPS FOR EACH STEP AS YOU GO! This will make it easier to recover if some step fails/a mistake is made.
Unless you have a hard-mod for your console, it is HIGHLY recommended to attempt this tutorial on EmuNAND on the target system to avoid bricks.
YOU HAVE BEEN WARNED!!!

This tutorial will instruct you how to do a "Manual System Transfer" from one 3DSsystem to another 3DS system.
It is reversible back to the original system, but will invalidate content on the target system as a normal system transfer would.
Due to this fact, PLEASE BACKUP ANY SAVES YOU CARE ABOUT on the target system with SaveDataFiler/etc. before you proceed.
This method will ONLY transfer saves and give you the ability to install content on the target system.
This method will NOT move your NNID over to the target system/re-link it. This is a server-side thing and must be done by Nintendo.
This method should be especially useful for people with region-changed systems that want to move over saves for Mii Plaza/etc.
This tutorial is a HIGH LEVEL process. Many steps will not be completely spelled out, so if you don't understand a specific term/procedure, please consult the forums.

THANKS TO EVERYONE WHO HELPED MAKE THIS TUTORIAL POSSIBLE!!!

Requirements:
Both the source and target systems must be on exploitable firmwares (for the purpose of this guide, this basically means <= 9.2 SysNAND FW)!
The method used to run unsigned code on the source system (for example Gateway, or a 4.5 CFW) must also be able to be run on the target system for full transfer.
Example: If you utilize a 4.5 exclusive CFW on your source system, you wouldn't be able to transfer with that onto a New 3DS as New 3DS systems cannot run 4.5 FW.

Note: I personally used this method between the 9.7 EmuNAND of an original 3DS system to a region-changed 9.5 EmuNAND New 3DS system.
I also utilized a Gateway card for running my transferred content on the target, New 3DS system. Other methods are possible, but again, they must be compatible between systems.
For optimal results, you will want to utilize firmwares on both systems in the same major version (for example, 9.x and 9.x on both systems).

Limitations:
This method will NOT transfer over your NNID from the source system to the target system as a legit system transfer would.
This method was mainly born from the issues stemming from region-changing a 3DS system and then wanting to transfer content to that system.
Personally, having done this method between my US O3DS and my originally JPN N3DS, my NNID was left on my O3DS and all my saves were copied to the N3DS.
From there I continue to make future purchases on the O3DS under my NNID and then manually install said purchases on the N3DS with Gateway.
Please note this part of the procedure is specific to my issues with not being able to system transfer from a US O3DS to a region-changed N3DS completely, but hopefully this tutorial will still be useful for you!

Let's get this show on the road!

A. Source System
1. Dump/extract your source NAND

On the source system, you will first need to dump the NAND you will be pulling your save data from (either SysNAND or EmuNAND).

This can be done either through something like the Gateway menu with a SysNAND backup or EmuNANDTool to extract your EmuNAND from your SD card.

2. Extract the Fat16 CTR partition from your source NAND backup

This can be done with a script such as Cearp's "3DSFAT16tool.py" python script.

3. Generate NAND XORPads for your source NAND

This can be done with a tool such as Decrypt9 (which runs through Ninjhax and is currently the only method to generate XORPads for the New 3DS).

4. Decrypt your NAND backup with the XORPads from the previous step

This can be done by simply xor-ing your extracted Fat16 CTR partition with your NAND XORPads (using something like the "XOR Tool" in 3DSExplorer).

5. Mount your decrypted NAND backup for editing

This can be done with a tool such as WinImage in Windows or directly as an ISO in Mac OSX.

6. Extract necessary files/saves from source NAND

The files you want to extract and are safe from your source NAND are as follows:

NAND://private/movable.sed - THIS IS THE MAIN FILE FOR THIS PROCESS! It is the file which identifies/is used to decrypt the saves from your source NAND/SD card.

NAND://dbs/ticket.db - This file will be used later to recover our purchased content for the target system.

NAND://data/<ID0>/extdata - You may extract and save all the subfolders in this folder (<ID0> will be a randomly generated number, matching the number of your save folder in the "Nintendo 3DS" folder on your SD card).

NAND://data/<ID0>/sysdata - Extract and save ONLY the following folders! (For reference, these titles are for US systems and may vary by region - consult: http://3dbrew.org/wiki/System_SaveData for your region):

000200bd - Miiverse

0001000f - Unknown

0002021b - Nintendo Zone

0002021d - Face Raiders

0002021e - AR Games

00010011 - FS module (for Anti Savegame Restore games like Animal Crossing/PKMN/Smash)

00010022 - Pedometer

00010026 - Streetpass (active games)

00010032 - Friends

00010034 - Spotpass

00010035 - News

00020093 - Game Notes

00020094 - Internet Browser

00020096 - Friend List

00020212 - Activity Log

00020214 - Nintendo 3DS Camera

00020215 - Nintendo 3DS Sound

00020217 - Mii Maker

00020218 - Mii Plaza

Note: These are the only saves I have tested to work and transfer safely. If you try to transfer saves for more system apps (such as NNID/config) I cannot guarantee success/positive results.
Further Note: I CAN confirm that if you transfer the app of something like Config from original 3DS to New 3DS, you will likely have weird results for screen display/etc. [DON'T TRY THIS!!!]

B. File Modification
1. Open your "movable.sed" file from the source system in you favored hex editor (such as "HxD").
2. Once open, you will want to remove the last 0x20 bytes from the file (actually shrinking the size of the file from 0x140 to 0x120).
3. At the beginning of the file, clear the 4 BYTES after the 'SEED' value (each byte should consist of two hex-based numbers, such as '00' or 'AF'; when clear, the value for that byte should show '00'/'.').

For example, the beginning of your file after modification should show '53 45 45 44 00 00 00 00' or "SEED...."

4. Save changes to your "movable.sed" file and close it (Recommend saving in a new copy of the file in case any mistakes are made!).
Note: Thanks to motezazer for the instructions on this step! (This was the most important step of this process!)

Note: REMEMBER! THIS METHOD WILL INVALIDATE EXISTING CONTENT/SAVES ON THE TARGET SYSTEM! Please backup any important saves before proceeding!
C. Target System
1. Dump/extract your target NAND

On the target system, you will need to dump the NAND you will be injecting your save data to (either SysNAND or EmuNAND).

This can be done either through something like the Gateway menu with a SysNAND backup or EmuNANDTool to extract your EmuNAND from your SD card.

2. Extract the Fat16 CTR partition from your target NAND backup

This can be done with a script such as Cearp's "3DSFAT16tool.py" python script.

3. Generate NAND XORPads for your target NAND

This can be done with a tool such as Decrypt9 (which runs through Ninjhax and is currently the only public method to generate XORPads for the New 3DS).

4. Decrypt your NAND backup with the XORPads from the previous step

This can be done by simply xor-ing your extracted Fat16 CTR partition with your NAND XORPads (using something like the "XOR Tool" in 3DSExplorer).

5. Mount your decrypted NAND backup for editing

This can be done with a tool such as WinImage in Windows or directly as an ISO in Mac OSX.

6. Inject your MODIFIED "movable.sed" file to your target NAND

Simply copy your modified file and overwrite the existing "movable.sed" file.

7. Delete the contents of the of the NAND://data folder

This step is necessary to reinitilize the system with the new "movable.sed" file. Do NOT delete the "data" folder itself!

8. Re-encrypt your target NAND with XORPads

This can be done by simply xor-ing your extracted Fat16 CTR partition again.

9. Inject your modified Fat16 CTR partition into your target NAND

Use the injection function of a script such as "3DSFAT16tool.py", for example.

10. Flash/inject your modified target NAND to the target system

Using either a hardware restore method (Gateway menu/hard-mod) or software (EmuNANDTool for EmuNAND).

11. Boot into the target NAND

Let the system boot up to the start of the system setup procedure. Once you get to the system setup start screen, you may power off the system without going through the setup.

12. Extract your target NAND again
13. Extract your Fat16 CTR partition again
14. Decrypt your partition with XORPads again
15. Mount your decrypted partition for editing again
16. This time, inject your "extdata" and "sysdata" saves from the source system into the newly created folder under NAND://data/<ID0>

Overwrite any existing saves with your source system data.

17. Re-encrypt your target NAND with XORPads again
18. Inject your modified Fat16 CTR partition into your target NAND again
19. Flash/inject your modified target NAND to the target system again
Note: DO NOT POWER ON YOUR SYSTEM YET!

D. SD Card Content
*. Now that we have prepared and transferred the NAND content from the source system to the target system, we much now transfer our SD card content to get ALL our saves for system titles
1. From the source system, start by copying the following folders and their contents from the source SD card the target SD card:

SDMC://Nintendo 3DS/<ID0>/<ID1>/backups

SDMC://Nintendo 3DS/<ID0>/<ID1>/extdata

Note: <ID1> won't match between source/target SD card folders, but <ID0> should match. This is normal.
2. Next, we will need to obtain any system application updates/DLC you had on your source system on the target system

This can be done utilizing your "ticket.db" from the source system and a script like "FunkyCIA2.py" (again by Cearp ) to obtain the CIAs

For reference, the title IDs of the Mii Plaza update and DLC are:

0004000e00021800 - Mii Plaza Update

0004008c00021800 - Mii Plaza DLC

3. You may now insert your target SD card and boot up the target system

Once you have reached the home menu, install the CIAs obtained from the previous step using your favorite CIA management tool (I recommend FBI, by Steveice10 ).

4. You may now run system apps and your save data should be intact and available!

If you had updated the Mii Plaza/purchased DLC and then tried run your transferred save without installing them in the target system, you would get an error saying your save is not on the correct version.

Note: The main limitation of this transfer method is we cannot yet locally transfer the tickets for purchased content from from one system's "ticket.db" file to another.

In a legit system transfer, the tickets are sent to Nintendo from the source console and then returned to the target console, rewritten with the console ID of the target system.

For this reason, we must utilize CIAs/unsigned installations for our purchased on content on the target system.

E. Remaining SD Card Content
*. Once you have achieved access to your system applications saves on the target system, you can proceed with installing and transferring the saves of your other purchased content
1. Obtain CIAs for your remaining purchased content

Utilize your ticket "ticket.db" from the source system again and something like "FunkyCIA2.py" to obtain CIAs of your purchased content.

2. Install CIAs on your target system

Utilize an installer such as FBI.

3. Once installed, copy your saves for the associated content from the source SD card to the target SD card

Locate the matching title ID and save file on the source SD card and copy it to the appropriate folder on the target SD card.

For example: On the source SD card, your save for Animal Crossing: New Leaf [US] (titleID: 0004000000086300) would be in the folder:

SDMC://Nintendo 3DS/<ID0>/<ID1>/title/00040000/00086300/data/00000001.sav

Copy that save file to the corresponding folder on your target SD card and your save should now be accessible on the target system!

Closing Thoughts:
I really hope this tutorial has helped some people who may be in the same boat I was, wanting to transfer my content from my O3DS to my region-changed N3DS.
Thank you for your reading and have a "Nintacular" day!

@Ichii Giki - can I use this method to move my mii plaza data (puzzles etc) from my O3DS USA to N3DS EUR? I am not sure if I understand correctly but it sounds like you moved your stuff between NANDs of the same region.

UPDATE:

I tried to move my stuff from o3DS (U) to n3DS (E). I've modified movable.sed as it was described in the tutorial and also moved content of NAND's sysdata, extdata. I've changed folders names accordingly to european names so the moved saves should be found by target NAND. Unfortunately target NAND says that my saves are corrupted, only friend list was moved, mii plaza/mii not. Is there some other way? E. g. decrypting those saves, converting them to european ones? Any help will be apreciated!

Nephiel · Mar 5, 2016

I'm setting up a9lh on a N3DS and I want to start up with a clean slate, but keeping the data from:

Mii Plaza
Face Raiders
AR Games
Friends
Friends List
Camera
Sound
News

My goal is to end up with a "clean" emuNAND with my NNID linked, a clean Activity Log and no fake tickets in ticket.db, but without losing my progress in the above titles.

So I'll be following this guide to copy only these saves from my current, "dirty" emuNAND (which has all my progress to date, but fake tickets and the Activity Log full of homebrew CIAs, SaveDataFiler, BigBlueMenu...) to a previous, "clean" emuNAND of the same console (the original dump I made back then when I set up this console for the first time).

I have confirmed that both the source and target emuNANDs are still linked, (same NNID, successfully replaced "dirty" ticket.db with "clean" one), so in the end I'll be just replacing old saves with newer ones on the same NAND.

Am I right in assuming movable.sed and the xorpads would be the same for both source and target in this case?

----
Edit: The Xorpads are the same, but I compared movable.sed between source and target and it has changed, so I'd have to edit it, and thus lose the saves of the other titles.
At this point it seems easier to just delete the save from Activity Log in the target NAND, so I'll probably try that and see what happens.
----
Edit 2: Tried deleting the Activity Log save file /data/<ID0>/sysdata/00020222/00000000, reinjecting with 3DSFAT16tool, and flashing the image to emuNAND again. This had no effect - Activity Log still shows everything like before. Bummer. (Edit 5: now I know that I probably should have deleted the PTM history as well. Since I didn't, Activity Log just read the history and recreated everything when opened.)
----
Edit 3: Followed the whole process and it looks like it worked. I now have a 10.6 emuNAND with a clean Activity Log but all my Mii Plaza encounters intact. Mii Maker was empty, but after entering my NNID, the system allowed me to retrieve my main Mii from my account. Not sure about the Mii Plaza DLC games yet, I have to download them to check if the saves for those have been transferred as well.
----
Edit 4: It turns out the saves for the Mii Plaza DLC games are on the SD card, so they also work. Success!

Chrushev · Mar 7, 2016

Can you provide more details on Step 3 and 4? Which option do I pick to generate the XorPads? There are 8 options in XORpad generation options.

Nephiel · Mar 7, 2016

I used CTRNAND Padgen and CTRNAND Padgen 0x4, iirc.

Chrushev · Mar 7, 2016

Nephiel said:
I used CTRNAND Padgen and CTRNAND Padgen 0x4, iirc.

Can you give step by step? ive never used any of these tools before and really dont want to mess anything up.

Nephiel · Mar 7, 2016

Chrushev said:
Can you give step by step? ive never used any of these tools before and really dont want to mess anything up.

I ended up following the first post on this thread almost to the letter. Even so, I had to read up on each tool and how to use it - for example, the current version of 3DSFAT16tool.py extracts the FAT16 CTR partition, reads the XORpads, and encrypts/decrypts in a single step, so that saves some steps.

Chrushev · Mar 7, 2016

Nephiel said:
I ended up following the first post on this thread almost to the letter. Even so, I had to read up on each tool and how to use it - for example, the current version of 3DSFAT16tool.py extracts the FAT16 CTR partition, reads the XORpads, and encrypts/decrypts in a single step, so that saves some steps.

its a shame this guide is out of date and is very vague on some steps. I dont have any experience with any of these tools... Im trying to do step 4 to decrypt my emunand, but am not sure how, or even if 10.6 emunand can be decrypted. Can you point me to this documentation you speak of? Maybe that will help me. Someone should update the guide.

Thats one complaint I have about 3DS hacking scene, there is very little clarity, people use "just use tool X" or "google for Y" as their steps or answers. Which to someone who never heard of tool X or Y makes it very hard to make sure they are doing the correct thing and are looking at the correct thing. Like in this guide for example how much harder would it be to just say what to do to decrypt it? Would still be like 1 sentence. Not much more effort than to type "Go look for tool X and decrypt it", something like Use Tool X from <link> to Step1 -> Step 2 -> Step 3

Sorry for a bit of a rant, just frustrated... have been trying to piece this puzzle together for days, and I dont even know if its possible to decrypt 10.6 Nand

Nephiel · Mar 7, 2016

Sorry if I wasn't clear, it's just that I don't have my console here and I honestly don't remember the exact steps. Give me a minute to google it.

Edit: it turns out it was a little bit longer than "1 sentence"

Nephiel · Mar 7, 2016

Decrypt9: Download, How to run
3DSFAT16tool.py: Source, Download. It is a Python script, so you need Python 2.7 to run it.
Make sure the SD card in each console has at least 5 GB of free space, or you'll have to copy the dumped files to your computer after every dumping step to free space on it.

This is how I did steps A1 to A4, also C1 to C4, and C12 to C14:

To dump sysNAND and emuNAND of source and target console with Decrypt9:
sysNAND/emuNAND options -> NAND Backup.

To get XORPads with Decrypt9:
XORpad Generator Options -> CTRNAND Padgen
XORpad Generator Options -> CTRNAND Padgen 0x4

This generates the XORpad files nand.fat16.xorpad and nand.fat16.0x4.xorpad on your SD card. They are 1GB each. I'm not sure if the 0x4 xorpad is needed after all, but I generated it just in case (I used a N3DS).

To extract and decrypt the FAT16 CTR partition image from your dumped NAND, run it like this from a command prompt (in a single line):

3DSFAT16tool.py -d -n3ds your_nand_dump.bin your_decrypted_nand.img your_nand.fat16.xorpad

-d stands for dump
-n3ds only if your NAND is from a New 3DS
your_nand_dump.bin is the NAND dump you want to decrypt
your_decrypted_nand.img is the resulting disk image file containing the decrypted partition, ready to be mounted. IF THIS FILE ALREADY EXISTS, IT WILL BE OVERWRITTEN.

And this for steps C8 and C9, also C17 and C18:

To encrypt and inject the modified FAT16 CTR partition image back into a NAND dump:

3DSFAT16tool.py -i -n3ds your_nand_dump.bin your_decrypted_nand.img your_nand.fat16.xorpad

-i stands for inject
-n3ds only if your NAND is from a New 3DS
your_nand_dump.bin is the NAND dump you want to encrypt back. THIS FILE MUST EXIST, BUT IT WILL BE OVERWRITTEN with the changes you made, so make sure to use a COPY of the .BIN file here, and KEEP THE ORIGINAL SOMEWHERE ELSE.
your_decrypted_nand.img is the disk image you want to encrypt after changing the files in it.

Always make backups before anything, and don't blame me if something goes awry.
Good luck!

Chrushev · Mar 7, 2016

Thanks Ill give it a shot when I get home! Hopefully it works on 10.6 emunand.

Chrushev · Mar 8, 2016

Nephiel said:
Decrypt9: Download, How to run
3DSFAT16tool.py: Source, Download. It is a Python script, so you need Python 2.7 to run it.
Make sure the SD card in each console has at least 5 GB of free space, or you'll have to copy the dumped files to your computer after every dumping step to free space on it.

This is how I did steps A1 to A4, also C1 to C4, and C12 to C14:

To dump sysNAND and emuNAND of source and target console with Decrypt9:
sysNAND/emuNAND options -> NAND Backup.

To get XORPads with Decrypt9:
XORpad Generator Options -> CTRNAND Padgen
XORpad Generator Options -> CTRNAND Padgen 0x4

This generates the XORpad files nand.fat16.xorpad and nand.fat16.0x4.xorpad on your SD card. They are 1GB each. I'm not sure if the 0x4 xorpad is needed after all, but I generated it just in case (I used a N3DS).

To extract and decrypt the FAT16 CTR partition image from your dumped NAND, run it like this from a command prompt (in a single line):

3DSFAT16tool.py -d -n3ds your_nand_dump.bin your_decrypted_nand.img your_nand.fat16.xorpad

-d stands for dump

-n3ds only if your NAND is from a New 3DS

your_nand_dump.bin is the NAND dump you want to decrypt

your_decrypted_nand.img is the resulting disk image file containing the decrypted partition, ready to be mounted. IF THIS FILE ALREADY EXISTS, IT WILL BE OVERWRITTEN.

And this for steps C8 and C9, also C17 and C18:

To encrypt and inject the modified FAT16 CTR partition image back into a NAND dump:

3DSFAT16tool.py -i -n3ds your_nand_dump.bin your_decrypted_nand.img your_nand.fat16.xorpad

-i stands for inject

-n3ds only if your NAND is from a New 3DS

your_nand_dump.bin is the NAND dump you want to encrypt back. THIS FILE MUST EXIST, BUT IT WILL BE OVERWRITTEN with the changes you made, so make sure to use a COPY of the .BIN file here, and KEEP THE ORIGINAL SOMEWHERE ELSE.

your_decrypted_nand.img is the disk image you want to encrypt after changing the files in it.

Always make backups before anything, and don't blame me if something goes awry.
Good luck!

Tried it.. getting errors and it exits:

Dumping... please wait
Traceback (most recent call last):
File "C:\Users\<>\3DSFAT16tool.py", line 103, in <module>
w.write(xor(fat16, xorpad))
File "C:\Users\<>\3DSFAT16tool.py", line 36, in xor
if i == 8: dt = numpy.dtype('<Q8');
TypeError: data type "<Q8" not understood

Nephiel · Mar 8, 2016

Which version of Python do you have?

Chrushev · Mar 8, 2016

Nephiel said:
Which version of Python do you have?

I tried 3.4 and 2.7

I also tried the C rewrite of this - https://gbatemp.net/threads/port-release-3dsfat16tool-c-rewrite-by-d0k3.390942/ which creates the file sucessfully but the file cant be mounted... now im wondering if this works with 10.6 emunand.

EDIT - spoke too soon.... i can mount the one that was output by the C version. WOOT!

Now Im at Hex Editing section... now sure which parts it wants me to delete..... help?

Nephiel · Mar 8, 2016

For hex editing movable.sed, see steps 3 and 4 from this thread, they have screenshots. Ignore the other steps, they are different from this guide.

Chrushev · Mar 8, 2016

Nephiel said:
For hex editing movable.sed, see steps 3 and 4 from this thread, they have screenshots. Ignore the other steps, they are different from this guide.

Awesome thanks! Now it appears that Decryptor9 cant generate proper xorpads from 10.6 on new 3ds (my target system)... but sounds like fix is coming soon.. looks like Im going to have to wait.

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Artificer

Well-Known Member

Artificer

Well-Known Member

Artificer

Well-Known Member

Artificer

Artificer

Well-Known Member

Well-Known Member

Artificer

Well-Known Member

Artificer

Well-Known Member

Similar threads

Popular threads in this forum