HLO will _never_ support user-created content

[thaX]

Likely, it is self made files from users putting the information in, not the files being sold on the web site. The main reason for the program is to aid in making of the character for the user to play. Piracy of other companies' content, either the compiled files for use of the program or relayed info from the builder within the program, is not a good reason to exclude them or disallow players to transfer the info needed to play the game.

I know Lonewolf has been very good at keeping IP from being "leaked" on their end, and a lot of mechanics of PF1 in particular had some very hard work arounds that put a strain on the program in the latter stages of it's run.

Something like this is perhaps the reason Lonewolf went to an Online App instead of sticking with the (Still superior) program. I am surprised that there isn't a bootleg of Etools somewhere around with all the extras up until it was yanked from the market.

It is well known for this? A surprise for me to hear this, as the licensing that the program uses makes it difficult, at least for the typical user.

[Roadie]

Copyright may be a reason, but I'd imagine that just as a big a reason has to be the .por format and all its legacy bits and custom XML trees being a pain in the butt to work with, as compared to the HLO API just giving you a big JSON feed that any half-competent web dev can write a parser for in an afternoon.

[Farling]

Originally Posted by Roadie

Copyright may be a reason, but I'd imagine that just as a big a reason has to be the .por format and all its legacy bits and custom XML trees being a pain in the butt to work with, as compared to the HLO API just giving you a big JSON feed that any half-competent web dev can write a parser for in an afternoon.

The import of the XML files from inside .por files isn't too complicated - my realm works importer is doing it for 2 (soon to be 3) game systems.

Foundry VTT provides core functionality which doesn't, by itself, directly support importing from anywhere. It is entirely up to community (or paid for) modules to provide any actual import/export functions.