How To: Export Import Characters from one orcpub to another - Orcpub/orcpub GitHub Wiki

Since a lot of us are trying to move characters from OP2 (source) to DMV (destination), but there's not a clear import/export path, I thought I'd share my method. This is pretty simple, but does require you to be familiar with the Chrome developer tools. Doing this from other browsers is left as an exercise to the reader.

Prerequisites

Export all content from OP2 (source).

Import the resulting .orcbrew file into DMV (destination).

Export

  1. Open a character in OP2 (source) in Chrome.
  2. Click "Edit". This will load the character definition from the server into your local storage.
  • OP2 (source) has a single character object stored locally, which is one of the reasons there's no simple character export like there is content export.
  1. In developer tools, navigate to Application > Local Storage > https://orcpub2.com (source)
  2. Select the character key.
  3. Copy the contents of the value field for this key.
  4. In another tab/window, create and begin edition a new character in your DMV (destination) account.
  5. In developer tools, navigate to Application > Local Storage > https://www.dungeonmastersvault.com (destination)
  6. If the character key does not exist, create it.
  7. Paste the copied character blob into the value field.
  8. Refresh the page.
  9. Click "Clone".
  • You cannot simply click "Update Existing Character", since the :db/id of the character you just imported does not exist in the DMV (destination) database. I haven't dug into the code to see why, but it actually appears to invalidate the current session and demand a new login. This is likely a security feature when attempting to modify a database object that doesn't exist or you don't have permission for.
  1. Edit the character name to remove the "(Clone)" appended by the Clone button.
  2. Click "Save New Character".

Notes

  • I don't know if this keeps party membership, since I don't use that feature and couldn't be arsed to mock up the situation and test it.

  • Fundamentally, the character object appears to be intended only for use within its originating server. I haven't found obvious places where matching custom content fails; but I don't use a whole lot of custom content. Proofread your character sheets; since the character blobs do reference a lot of db primary keys, and it's entirely possible there are bugs that would cause problems with cross-server use of character data.