• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Foundry loose integration

Sword_of_Spirit said:
I found one more glitch. I tried to change the setting for "Location of Extracted Assets" from the default to a different folder (in this case Data/media/realmworksimport), and it ruined the import. Only 4 or 5 scenes made it in, and it didn't look like any journal entries made it in. (Lots of errors in the console naturally.) Worked fine in the default location.
Click to expand...

I'd be interested in seeing the first few errors in the console. One of the early ones might indicate why it doesn't like the supplied location.

Did you mean that the settings panel now says,

[data] media/realmworksimport

Or did you actually select "Data/media/realmworksimport" from the folder picker?
 
Farling said:
I'd be interested in seeing the first few errors in the console. One of the early ones might indicate why it doesn't like the supplied location.

Did you mean that the settings panel now says,

[data] media/realmworksimport

Or did you actually select "Data/media/realmworksimport" from the folder picker?
Click to expand...

That's strange. It worked this time. The time it didn't work it actually uploaded the files to the correct folder--it just didn't finish implementing them or the journals in the world.

It's the former path. Maybe I did the latter last time? I don't know. Maybe there was just a glitch.
 
Sword_of_Spirit said:
That's strange. It worked this time. The time it didn't work it actually uploaded the files to the correct folder--it just didn't finish implementing them or the journals in the world.

It's the former path. Maybe I did the latter last time? I don't know. Maybe there was just a glitch.
Click to expand...

It's good to hear that it is working now though :-)
 
I'm not sure if you need any sort of heads up for this, but Foundry v10 will be on the release channel soon, and with its journal system completely revamped, there may be tweaks that need to be made to the module for it to work right. Once it's out I'll report any abnormalities I can find.
 
Sword_of_Spirit said:
I'm not sure if you need any sort of heads up for this, but Foundry v10 will be on the release channel soon, and with its journal system completely revamped, there may be tweaks that need to be made to the module for it to work right. Once it's out I'll report any abnormalities I can find.
Click to expand...

I already have the journal code updated - it will have only one page per journal document though. There isn't an easy way to understand which RW topics might be pages within a single journal document.

Actor generation is more difficult, since each supported game system would have to be re-evaluated and tested to ensure that actors are created from the embedded HL portfolios. Actor generation for CoC7 is already working in the V10 version.

I am awaiting each game system to be converted to work with V10 before I can start on converting my importer for that game system (DND5E, PF1, SWADE)
 
Last edited:
Hello, i use the Realm Works Importer for Foundry VTT and i imported the .por-Files from the pc and nsc - that works, but i can't open their character sheets. Need help!

I use Foundry 10.291 and Realm Work Importer 2.7
 
SLger said:
Hello, i use the Realm Works Importer for Foundry VTT and i imported the .por-Files from the pc and nsc - that works, but i can't open their character sheets. Need help!

I use Foundry 10.291 and Realm Work Importer 2.7
Click to expand...

Which game system and version of that game system?

I haven't updated the dnd5e importer to support dnd5e v2.1.x, but it should stil work with dnd5e v2.0.x
 
SLger said:
i use Pathfinder 1 version 0.82.5 for foundry vtt
Click to expand...

My test imports seem to work properly in that version of the PF1 system.

Is it possible for you to send me the POR file as a DM so that I can test it.

Also, could you look in the browser console (open with F12 on Windows) in order to see if there are any errors reported during the import process.
 
Farling said:
My test imports seem to work properly in that version of the PF1 system.

Is it possible for you to send me the POR file as a DM so that I can test it.

Also, could you look in the browser console (open with F12 on Windows) in order to see if there are any errors reported during the import process.
Click to expand...

Here is one of the .por-files
 

Attachments

Hey there!

Love the importer (use it just for HL Classic files), however it seems like with the latest update the importer stopped working. When I try to import a .por, the status gets stuck at "Reading [file name].por" with no actors being created.

I tried unpdating the module, uninstalling and reinstalling the module, and in the world itself disabled and re-enabled the importer. I also tried different .por files (including one that I had previously imported) and still the same result. Any help would be appreciated!!!

I'm running Pathfinder 1e (9.1) and it looks like Realmworks Importer 2.8.1. Neither are flagged as having compatibility issues.
 
The Numerator said:
Hey there!

Love the importer (use it just for HL Classic files), however it seems like with the latest update the importer stopped working. When I try to import a .por, the status gets stuck at "Reading [file name].por" with no actors being created.

I tried unpdating the module, uninstalling and reinstalling the module, and in the world itself disabled and re-enabled the importer. I also tried different .por files (including one that I had previously imported) and still the same result. Any help would be appreciated!!!

I'm running Pathfinder 1e (9.1) and it looks like Realmworks Importer 2.8.1. Neither are flagged as having compatibility issues.
Click to expand...

It is probably caused by a change in the format of Actors in PF1 version 9.1

I will need to investigate to see what needs changing.
 
PF1 characters should now import properly for Foundry PF1 v9.x on Foundry V11 (module version 2.9.0)

(Note that you still need to set the character type in the module settings.)
 
Last edited:
It's been working well since the update!

One question... I noticed when I upload monsters w/ class levels, the HP that they gain from the favorite class seem to go away. If I look at the class setting, it's showing as NPC and not Base. I did check the module settings, and I have the default set to base.

I'm uploading from HL files, which are saved from using the Encounter Builder for the official PF APs (currently Runelords). Is there something in the HL build that is causing this to override the module default?

If you wanted to do a simple test, just try importing a goblin. It's supposed to have 5 HP, but once imported only shows 4.
 
The Numerator said:
It's been working well since the update!

One question... I noticed when I upload monsters w/ class levels, the HP that they gain from the favorite class seem to go away. If I look at the class setting, it's showing as NPC and not Base. I did check the module settings, and I have the default set to base.

I'm uploading from HL files, which are saved from using the Encounter Builder for the official PF APs (currently Runelords). Is there something in the HL build that is causing this to override the module default?

If you wanted to do a simple test, just try importing a goblin. It's supposed to have 5 HP, but once imported only shows 4.
Click to expand...

I think that the official monsters from the PF APs might not have all of their data exported, due to the copyright(?) nature of the data stored in HL. Although I could be wrong.

I will have a quick look at some point to see if that is the case.

I've raised https://github.com/farling42/fvtt-import-realmworks/issues/85 to track it.
 
Last edited:
The Numerator said:
It's been working well since the update!

One question... I noticed when I upload monsters w/ class levels, the HP that they gain from the favorite class seem to go away. If I look at the class setting, it's showing as NPC and not Base. I did check the module settings, and I have the default set to base.

I'm uploading from HL files, which are saved from using the Encounter Builder for the official PF APs (currently Runelords). Is there something in the HL build that is causing this to override the module default?

If you wanted to do a simple test, just try importing a goblin. It's supposed to have 5 HP, but once imported only shows 4.
Click to expand...

When I used HL's Encounter Builder and selected "Goblin" to put into it's own POR file, importing this POR file into Foundry created a goblin with 6 HP (which matches the number in HL).

This is with Foundry 11.314, PF1e 9.5 and Realmworks Importer 2.9.1

I've release 2.9.2 to support the changes in Foundry's PF1 version 9.x series (so that creature ability scores are set correctly based on the Race of the creature).
 
Last edited:
A possible feature request has been rolling around in my mind for a while now, although I'm uncertain if it would work right or have issues.

Basically, I'm not aware of any components of Foundry's journal documents that aren't functional from within a compendium. While Foundry's scenes/maps are absolutely crippled in a compendium (all you get is the image), and actors and items are fully viewable but non-functional in a compendium, journals seem to work just fine from within a compendium.

My first concern is that I may be wrong, and there may actually be some journal functionality that isn't present in compendiums. If that is the case, the feature I'm thinking about may not be a good idea. (And in general, if anyone knows of elements of journals that don't work in compendiums, I'd appreciate hearing about it anyway.)

But, if journals *are* fully functional from within compendiums, I think it would be great if we could have an option to import journals directly into compendiums (including a shared compendium), rather than into the world. This would free up memory usage for those of us with enormous worlds we want to transfer to Foundry. And if we create new Foundry journals directly in the compendium, this would allow us to keep everything together.

Again, I don't know whether there are any problems with this proposed idea, but I wanted to suggest it, because it could be a good optional way to free up memory and consolidate organization.
 
Sword_of_Spirit said:
A possible feature request has been rolling around in my mind for a while now, although I'm uncertain if it would work right or have issues.

Basically, I'm not aware of any components of Foundry's journal documents that aren't functional from within a compendium. While Foundry's scenes/maps are absolutely crippled in a compendium (all you get is the image), and actors and items are fully viewable but non-functional in a compendium, journals seem to work just fine from within a compendium.

My first concern is that I may be wrong, and there may actually be some journal functionality that isn't present in compendiums. If that is the case, the feature I'm thinking about may not be a good idea. (And in general, if anyone knows of elements of journals that don't work in compendiums, I'd appreciate hearing about it anyway.)

But, if journals *are* fully functional from within compendiums, I think it would be great if we could have an option to import journals directly into compendiums (including a shared compendium), rather than into the world. This would free up memory usage for those of us with enormous worlds we want to transfer to Foundry. And if we create new Foundry journals directly in the compendium, this would allow us to keep everything together.

Again, I don't know whether there are any problems with this proposed idea, but I wanted to suggest it, because it could be a good optional way to free up memory and consolidate organization.
Click to expand...

Putting all created journals into a compendium is entirely feasible. A similar thing could be done for Items, since Items are not ever required in Foundry's sidebar either.
 
You must log in or register to reply here.
Back
Top