I have tried to explain to those working on this the importance of having an importer for. Rome was not built in a day - or seven weeks, for that matter. And even that doesn't really work as there are a lot of feats and class abilities that aren't supported yet, so it can't import the whole stat block. You can have Herolab generate a statblock, then copy+paste that statblock into an importer module for PF1. por file directly about 3 years ago when LWD told the VTT devs that they were going to change their data structure to accommodate HLO's server design. Smiteworks should have migrated FG2's file importer to just read the native.
If FG2 still requires a "save custom output" export file from Herolab then it does. I never have to "save custom output" in Herolab Classic and have not had to for nearly 3 years. por file from HLO - though they may well add it later this summer).Īnyways, the point is that D20PRo now directly imports the. You just don't see that on the user side (and there is no way currently to dl a. You may not know this, but Herolab Online is still entirely based on. And a way to export to D20Pro.īut when LWD decided to move to HLO, they modified their. Herolab Classic had a way to export to FG, yes. In fact, it might even be more accurate to put it that way because it has the ability to export to Fantasy Grounds." " One could just as easily say that Hero Lab Classic is missing the ability to export for FoundryVTT.
0 kommentar(er)
