Senior Member
Lone Wolf Staff
Join Date: Apr 2013
Posts: 691
|
That may be all you want personally, but as is clear from this thread, others want to export for use in 3rd party software. It is our (Lone Wolf's) job to address not only the features explicitly requested by users in forum threads for their own benefit, but also that of anyone reading who may not be directly responding.
|
#11 |
Senior Member
Join Date: Jul 2015
Posts: 216
|
Sure, but I can only read what's written. You specifically mentioned 3rd party, which is very different from sharing only between HLO users. I respect that LWD is making decisions on what they think their customers are wanting.
|
#12 |
Senior Member
Join Date: Mar 2013
Location: Melbourne, Australia
Posts: 1,094
|
I think he was also taking into account Boomer's comment (above your first post) who does specifically mention 3rd party software using HLO data.
Current RPG's: Pathfinder (GM), Pathfinder (Player), Gamma World (GM, Pathfinder homebrew). HeroLab: 3.5 & Pathfinder. HL User Files for PF: Greyhawk Setting, Gamma World (WIP). DM and player of D&D since 1980. |
#13 |
Senior Member
Join Date: Jul 2015
Posts: 216
|
@Dami,
Headslap! Yes, I'd like FG integration too, but I was trying to take baby steps as exchange between the native application shouldn't be that difficult. Sorry I missed that one line. |
#14 |
Member
Join Date: Jan 2018
Posts: 39
|
The hinky part of exporting a character from one account to another is the possibility that the character uses resources/add-ons that the receiving account doesn't have.
You run into the same issue even now. Save out a portfolio of a character and email to someone else to import into their copy of HL and watch it puke errors all over the place when they don't have supplement X. I'm sure that they'd like that to degrade gracefully. How that would be, I have no idea. |
#15 |
Senior Member
Lone Wolf Staff
Join Date: Apr 2013
Posts: 691
|
Quote:
HLO will work the same way, albeit with a nicer presentation of the content that won't be loaded. |
|
#16 |
Member
Join Date: Jan 2018
Posts: 39
|
Quote:
So I need Players Companion #15 for the missing feat. Got it! As it is now, it's all guess-work. |
|
#17 |
Junior Member
Join Date: Dec 2010
Location: Somewhere in the NE US
Posts: 23
|
Quote:
Today as we play PF2E, I'm less likely to use HLO as it's a standalone tool; I can't import what the players have created. If I updated the player's sheets with XP, items, etc., I could send them their sheets. They were able to immediately import, view the changes, keep notes in the Hero Lab journals, and send it all back. This isn't about 3rd party anything for me. It's about organization, ease of use, and portability. In a world where most everything can be saved and imported, this was a backwards step for Lone Wolf Dev and a rather surprising one at that. Steve Last edited by skald1; January 10th, 2020 at 12:59 PM. Reason: Tighter verbiage |
|
#18 |
Junior Member
Join Date: Mar 2019
Posts: 19
|
Essentially it's just JSON out, JSON in, besides validation checks (for funky data) it should be trivial, but that's making assumptions about how they handle their service calls.
|
#19 |
Senior Member
Join Date: Mar 2013
Location: Greater London, UK
Posts: 2,623
|
Oh, if software was really this simple! ;-)
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 |
#20 |
|
|