View Single Post
Farling
Senior Member
 
Join Date: Mar 2013
Location: Greater London, UK
Posts: 2,623

Old August 4th, 2019, 11:38 PM
It looks like this isn't a viable route to take unfortunately.

All domain and tag elements need an original_uuid attribute, and these can only be allocated by Realm Works.

Realm Works uses it's own pattern for the UUIDs rather than following the standard UUID pattern (which would have allowed import tools to specify their own UUID for each element) so only an export from Realm Works will generate valid UUIDs.

Other than that...

tag_global elements should appear inside domain_global elements. The children of a domain element should be a tag element. Both tag and tag_global require a tag_id attribute, which must be unique in the file but otherwise can be of the form "Tag_x" where x is a number.

domain tags require a "domain_id" attribute, typicall of the format "Domain_x" where x is a number (the number can change from one import to another, since it is only used while loading the XML file).

Farling

Author of the Realm Works Import tool, Realm Works Output tool and Realm Works to Foundry module

Donations gratefully received via Patreon, Ko-Fi or Paypal
Farling is offline   #4 Reply With Quote