• 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

Importing Secured Content

What was publicly stated when import/export was announced was that there had been plans for a different sort of functionality for getting content in/out and shared between realms but that it was turning out to be too complicated/taking too long to implement. Import/export is what we have for all of that.

If true, that's most unfortunate. The current export/import system really is much too clunky to be the long-term solution for inter-realm information sharing within the same Realm Works account. Additionally, there's no good reason for it to be - if Realm Works can marshal the information and write it to a file, and then import that file, there is no reason why that external file step can't be skipped. The program should be able to directly take that info from one realm to another without the intermediate external file. In the process, since the information would never leave the program, secure information should be able to be shared between realms.
 
I think the current import/export was used because their original method proved unfeasible as KBS666 says. However, now that the CM is out, they can start planning on improving the import/export methods to maybe take out that intermediate step within the same RealmWorks account.
 
If true, that's most unfortunate. The current export/import system really is much too clunky to be the long-term solution for inter-realm information sharing within the same Realm Works account. Additionally, there's no good reason for it to be - if Realm Works can marshal the information and write it to a file, and then import that file, there is no reason why that external file step can't be skipped. The program should be able to directly take that info from one realm to another without the intermediate external file. In the process, since the information would never leave the program, secure information should be able to be shared between realms.

I agree 100%
Import/Export is far from ideal for exchaging material between realms within RW account.
And the possibility to move secure content between realms of the same account would greatly increase its value...
I think this should be a priority.
 
I agree 100%
Import/Export is far from ideal for exchaging material between realms within RW account.
And the possibility to move secure content between realms of the same account would greatly increase its value...
I think this should be a priority.

Don't you mean after Calendars? :-)

(I thought I would get that in first.)
 
To borrow from the old AD&D Core Rules 2 Expansion toolset, selective content import is a well-used feature of that toolset.

Of course, they didn't have the concept of "secure" imports... but still, you could open an import file and view the contents. It would show what items would conflict with what was in your DB and allow you to either select everything, or just the items you wanted.

VERY handy when you have a large export for archival purposes, but only want to grab a few things from it for a particular encounter set.

This is still a use case I employ today in that tool.

-=Janrith
 
It took about 35 or 40 minutes to import the NPC Codex this evening. Then I had to turn around and delete 90% of the content I imported, as I didn't need it. There has to be a better way...
 
I dont understand this mentality at all.

I guess I'm one of the misunderstood mentalities. I thought that what we got from the CM we would be able to add a few things from it to an already created realm.

Basically, I see the realm (the adventure) as an organized three-ring binder. My impression was that I could buy the Bestiary, take three "pages" that have the monsters I need to for my game from that binder/realm, and add them to my adventure binder/realm. Apparently not.

So why should I bother buying reference and rulebook materials if I can't take "pages" and add it to my current realm? Those reference and rulebook materials are a waste of my money because I still have to 1) create my own reference in my realm or 2) have access to the internet to look it up or 3) have the actual reference books and rulebooks next to my computer. It would be different if we could have more than one realm open. Then we could link to the content in another realm.
 
@Farling That is very true. And I'd imagine that the structure of RW makes that nigh impossible at this time. At least one of RW's competitors can do this seamlessly and totally painlessly, even linking content by other creators as long as you have access rights. It's definitely something RW needs to consider. But it would likely take an engine retooling.

I'd love to have a master world realm, campaign realm and game system realm in RW. Each is focused and recyclable. I'm not holding my breath for RW to do this.
 
Basically, I see the realm (the adventure) as an organized three-ring binder. My impression was that I could buy the Bestiary, take three "pages" that have the monsters I need to for my game from that binder/realm, and add them to my adventure binder/realm. Apparently not.

You can, but in a very not-optimal way: you have to add all the Bestiary and then delete all the unneeded pages.
 
Perhaps I'm missing a vital piece of info, but here's my use case.

I'm preparing a 5e campaign, I've imported the SRD, Midgard Worldbook, Heroes Handbook, and Tome of Beasts.

In Realm Works all of this is stored in the World Almanac and Mechanics Reference.

I rename the "Story Almanac" to "Dornig" which is where the game is taking place, then add all that I need from the World Almanac to the new view. Then I make a Mechanic view called "My Mechanics" and add all of the SRD to it, a few races that I am allowing from the Heroes Handbook, some spells, monsters, etc... from the various other sources. The new views are my 3-ring binder.

So now I have everything I need from all sources in two views, I stop using the World Almanac and Mechanics Reference altogether. I've deleted nothing, so that if I want to add another monster from the ToB or an area from the campaign world, I can easily do that.

In Addition, I can add all the various views and tools from the Ribbon to the the Quick Access toolbar and then minimize the Ribbon so I'm not seeing the World Almanac or the main Mechanics View and just use the Quick Access Toolbar to navigate between the various items.

I realize this doesn't cut down on import times or the amount of data in the database, if that's what the issue is, but it does address only needing to see certain items within the software itself as I'm using it. Also, any custom items I add, even if it is a picture and description to a monster in the SRD (per daplunk's post towards to beginning) can be exported out of this realm, and into another realm with the SRD and it will merge with the existing record.
 
@Kathorus

I've never used the quick-access toolbar, so using that with the ribbon minimized is a good tip.

Creating specific views in a Realm is certainly one way to recycle content for different campaigns, but the problems is that the reveal history is not view specific. You could copy topics and articles and organize them by campaign, I suppose but that seems to even more work than reimporting the SRD, etc. into each campaign.

I am not running concurrent campaigns in the same setting and I don't run many different campaigns, so I don't really have any issue with the current import/export functionality.

But for those who do, I *think* what may be particularly helpful is a feature many have been asking for: individual player reveal. That way you can run multiple groups through the same setting concurrently, without having to make and maintain multiple realms for the same setting/adventure.
 
Back
Top