Forge item: Pathbuilder Importer

[ThirdSign]

I published version 0.14 with the following changes:

* Automatically builds the default activities before applying any of the imports (This fixed your missing activities draykor)
* Explicitly imports weapon/armor proficiencies, rather than relying on FGU automation
* Explicitly imports spell proficiencies, rather than relying on FGU automation (really only applies to legacy ruleset)
* Explicitly imports save proficiencies, rather than relying on FGU automation (This fixes your fortitude importing wrong draykor)
* Fixed an issue where stealth wasn't imported (and this fixes your stealth importing wrong)

[Draykor]

Thank you very much for all that you do

[hobit]

I'm getting the following error:
[7/21/2024 7:38:43 PM] [ERROR] Script execution error: [string "..builder_import-main:..rom_pathbuilder.lua"]:140: openTextFile: Only available on host.

I'm a player playing with a GM that has an unlimited license.

[ThirdSign]

I'm getting the following error:
[7/21/2024 7:38:43 PM] [ERROR] Script execution error: [string "..builder_import-main:..rom_pathbuilder.lua"]:140: openTextFile: Only available on host.

I'm a player playing with a GM that has an unlimited license.

I'll take a look after work tomorrow.

In the interim, can you paste the file contents into the text field and submit that instead of using the file select functionality?

[Montis]

We've had some issues importing a character with General Training -> Armor Proficiency today. The import basically stopped at the level where this was taken and the character was a bit of a mess afterwards.

Might be worth looking at; we circumvented it by choosing a different feat at the level and then manually adding Armor Proficiency afterwards.

[Montis]

In addition to the above, the Importer seems to have quite a bit of trouble detecting higher level items that have a weaker version at lower level, or sometimes even gives higher level items than it's supposed to. Also some of the magic items are Unidentified after import.

Examples:

[Item in Pathbuilder] -> [Item in FG after Import]

Antidote (Greater) -> Antidote - major
Antiplague (Greater) -> Antiplague
Boots of Bounding (Greater) -> Boots of Bounding
Demon Mask (Greater) -> Demon Mask
Healer's Gloves (Greater) -> Healer's Gloves
Staff of Healing (True) -> Staff of Healing
Living Mantle (Greater) -> Living Mantle
Mistform Elixir (Greater) -> Mistform Elixir - lesser

[ThirdSign]

We've had some issues importing a character with General Training -> Armor Proficiency today. The import basically stopped at the level where this was taken and the character was a bit of a mess afterwards.

Might be worth looking at; we circumvented it by choosing a different feat at the level and then manually adding Armor Proficiency afterwards.

I tried importing armor proficiency, and while it's not _perfect_, the resulting proficiencies were correct. Eg. my test ranger was proficient in heavy armor correctly. The imported feat didn't have the (Heavy) like it does when you add it manually in FGU though.

If you're not seeing the proficiency at all, can you share the JSON that wasn't working?

[Montis]

If you're not seeing the proficiency at all, can you share the JSON that wasn't working?

It wasn't about the proficiency, it was that the import stopped completely and the resulting character was incomplete. I'm attaching the JSON in question.

EDIT: Sorry, I attached the incorrect file. I reattached the correct file that gives the broken output.

[ThirdSign]

It wasn't about the proficiency, it was that the import stopped completely and the resulting character was incomplete. I'm attaching the JSON in question.

That export helped a ton. I've got that armor proficiency issue fixes.

The item issue is harder to fix. The problem is PB exports something like Staff of Healing (true), but in FGU it's Staff of Healing - true staff of healing. This isn't consistent across items either, some items in FGU are <item name> - major, and some are <item name> - major <item name>.

I hard coded some workarounds for <item name> - <qualifier> but I don't have a general solution yet, so we'll still have some mismatches.