• 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

What Pathfinder Content Do You Want to See First?

What Pathfinder Content Do You Want to See FIRST?

  • Essential Pathfinder Rulebooks Only (e.g. CRB, APG, ACG, UM, UC)

    Votes: 23 15.2%
  • All Pathfinder Rulebooks

    Votes: 12 7.9%
  • Bestiaries and Similar Books

    Votes: 6 4.0%
  • Modules and Smaller Adventures

    Votes: 7 4.6%
  • Adventure Paths and Huge Adventures

    Votes: 45 29.8%
  • Generally Reusable Content (e.g. NPCs, Artwork, Maps)

    Votes: 4 2.6%
  • Golarian Campaign Setting

    Votes: 10 6.6%
  • Player Companions

    Votes: 0 0.0%
  • Not interested in Pathfinder content

    Votes: 44 29.1%

  • Total voters
    151
  • Poll closed .
I'm going to have to go with the campaign setting. Admittedly I'm very very new to Realm Works but I'm not seeing the value in having the core Rulebooms in RW. I thought RW was supposed to help me manage the intricacies of the game world and all the interactions happening. How does having access to initiative rules in RW help me at all? Am I missing something really awesome about RW?

I think most people want things like Classes, Races, Feats, and such.. not so much Cover, Concealment, Initiative, etc. (although I did enter those in my Rise of the Runelords Realm).

And that, I suppose, exposes another slice of the question.. if you want Rules, do you want ALL Rules, or just selectable things like Classes, Races, and Feats?
 
What is LoneWolf's position viz. Open Game License content?

Specifically, since it is (presumably) legal for any RealmWorks user to enter and re-publish all of the content on the Pathfinder Reference Document as a Realm... what is LoneWolf's expectation along that line?

We have a full license from Paizo for doing ALL Pathfinder material. So it's just a matter of prioritizing what we do first. An army of users will absolutely get stuff done faster than we can, but there's also the question of quality, consistency, accuracy, and quite a few other words ending in "y". :)

Any content that users create and share under the OGL is perfectly fine. And it can co-exist with anything we do. The two co-exist peacefully on the Hero Lab side. Lots of users will want the artwork (not OGL) and the "official" material that we've put the time and testing into. Lots of users will want to save some coin. There's a place for both.

The one big concern I have with our revised Content Market approach is that it may become "the Wild West" for a short time. The original CM model positioned us as sort of "curating" the available content, since users could not share content outside of our ecosystem. Without that chokepoint in place, I can see multiple users providing the same or overlapping material, and it could even become "competitive" on some level. That's going to be confusing (and very annoying) for everyone. So we (Lone Wolf) may have to become involved in the process to some extent. I'm just not sure how that will unfold yet.

This is something that I'm definitely losing sleep over these days, as it's going to have a qualitative impact on the overall experience for everyone. This is probably the one biggest drawback accompanying the revised plan, but we felt the pros far outweighed the cons, and it seems the user community agrees with that view. We're still working to figure out how best to handle this wrinkle.
 
Good question. That then naturally leads into the thought that if this starts to happen than we could end up with dozens of Pathfinder SRD by different community members. Unlike a wiki no way to work cooperatively "yet" on a single realm.

That seems like both a good and bad thing. :)

I imagine the differentiation would be along the lines of whose organization scheme is considered better, or at least more compatible with the buyer's style of play. It would likely lead to some very specialized packages... Core + PFS changes vs. Core + all non-world-specific books vs just Feats, Skills, Classes, etc. from all books... and so on,

LoneWolf, as licensors, could use the actual artwork from the books, which would be one differentiator for them. And some folks just feel better with the "official" version.. so that's another. PFS acceptance of an "official" Realm is unlikely, given that (as I understand) printed copies of PDF pages are required now (and the PDF itself is not accepted)... though that could change, I suppose.

If the re-packaging of Open Content is to be expected, then I would think that pushes the importance of the closed content... the Adventure text and the World-specific setting content... to the front of the priority list for LoneWolf.
 
We have a full license from Paizo for doing ALL Pathfinder material. So it's just a matter of prioritizing what we do first. An army of users will absolutely get stuff done faster than we can, but there's also the question of quality, consistency, accuracy, and quite a few other words ending in "y". :)

Any content that users create and share under the OGL is perfectly fine. And it can co-exist with anything we do. The two co-exist peacefully on the Hero Lab side. Lots of users will want the artwork (not OGL) and the "official" material that we've put the time and testing into. Lots of users will want to save some coin. There's a place for both.

The one big concern I have with our revised Content Market approach is that it may become "the Wild West" for a short time. The original CM model positioned us as sort of "curating" the available content, since users could not share content outside of our ecosystem. Without that chokepoint in place, I can see multiple users providing the same or overlapping material, and it could even become "competitive" on some level. That's going to be confusing (and very annoying) for everyone. So we (Lone Wolf) may have to become involved in the process to some extent. I'm just not sure how that will unfold yet.

This is something that I'm definitely losing sleep over these days, as it's going to have a qualitative impact on the overall experience for everyone. This is probably the one biggest drawback accompanying the revised plan, but we felt the pros far outweighed the cons, and it seems the user community agrees with that view. We're still working to figure out how best to handle this wrinkle.

Thanks, Rob.

In a way, LoneWolf is pretty much in the position Adobe was in when Acrobat was premiered. A little-known product that offers a new medium for publication.

The difference is that RealmWorks is dependent upon the servers at LoneWolf. That's a more closed-system operation than PDFs were back then. That carries the responsibility to police the closed environment, as you mentioned; the opening up of that environment does have other risks.

Unlike Adobe, who "only" had to worry about establishing PDF as a standard, RealmWorks' consumers are bound to LoneWolf by that closed environment. The gaming market is niche enough that, even if RealmWorks becomes popular within that population, it is not like that is a large enough population (right now, anyway) to support an independent "hosting" environment.

So... fasten your seatbelts... it's going to be a bumpy ride.,

On the plus side, the OGL community has had some time to mature. You may see a few ambitious amateurs pop up, and some may even "make it big", but I'd like to think it won't be quite as wild as the past. :)
 
We have a full license from Paizo for doing ALL Pathfinder material. So it's just a matter of prioritizing what we do first. An army of users will absolutely get stuff done faster than we can, but there's also the question of quality, consistency, accuracy, and quite a few other words ending in "y". :)

Any content that users create and share under the OGL is perfectly fine. And it can co-exist with anything we do. The two co-exist peacefully on the Hero Lab side. Lots of users will want the artwork (not OGL) and the "official" material that we've put the time and testing into. Lots of users will want to save some coin. There's a place for both.

The one big concern I have with our revised Content Market approach is that it may become "the Wild West" for a short time. The original CM model positioned us as sort of "curating" the available content, since users could not share content outside of our ecosystem. Without that chokepoint in place, I can see multiple users providing the same or overlapping material, and it could even become "competitive" on some level. That's going to be confusing (and very annoying) for everyone. So we (Lone Wolf) may have to become involved in the process to some extent. I'm just not sure how that will unfold yet.

This is something that I'm definitely losing sleep over these days, as it's going to have a qualitative impact on the overall experience for everyone. This is probably the one biggest drawback accompanying the revised plan, but we felt the pros far outweighed the cons, and it seems the user community agrees with that view. We're still working to figure out how best to handle this wrinkle.

ME? I want bestiaries followed by rules, but only got one vote.

Rob,

I wouldn't lose sleep over this, it is absolutely going to be the wild west, but this will be the initial short term impact.

Your analogy to HL is valid and a good key way for everyone to see as the future of RW, after the initial rough patch settles down.

LWD's HL work is great, the communities work in HL superbly complimentary to it. That's how I envision RW in a year or so, people like Shadow leading the way for the community to rally around, like the RW Desert Rangers.
 
How will RW > HL integration be handled in situations where the *.user file has not been released to the user?

I know we can embed portfolios in RW but they still require the underlying *.user file to pre-exist in Hero Lab in order for the content to work.

Lets say a new monster book is released via RW. Does that then come with the HL user file? Will installation be possible on HL for the purchased content within RW?
 
How will RW > HL integration be handled in situations where the *.user file has not been released to the user?

I know we can embed portfolios in RW but they still require the underlying *.user file to pre-exist in Hero Lab in order for the content to work.

Lets say a new monster book is released via RW. Does that then come with the HL user file? Will installation be possible on HL for the purchased content within RW?

Those are two different products with two different stores. So You would have to buy the product on both, or the 3PP doing the release would have to make both available I would think.

For my take, if I decided to share out my Daede campaign, it would include the Daede.user file I have created to support the campaign in HL. But I am not a publisher for money on it, it would be just a dude sharing his work for others to use if they so desired.
 
This is where I go back to some of my other comments in that Hero Lab and Realm Works need to become closer. One store, one cloud solution, one login that manages your license issues.

Given the two integrate it would not make sense to have to buy the content twice.

At this stage with my current understanding, the only way I would want to release Hero Lab portfolios would be content that is made using a custom monster race that is included in the core content. Then comparability would not be an issue.
 
I don't play Pathfinder, BUT I DO use some of their adventures (slightly modified). I've done this sort of thing for over 30 years - taken adventures, NPCs, artwork, maps, etc, from other game systems and adapted them for the game system I am currently using.

Often, I have found that the one thing most lacking in many game systems is adventures and similar material. But if I can snag a Pathfinder, D&D, Warhammer or other adventure and tweak it just enough to fit the system I am using, I'm golden!

What this boils dow to is this - by starting with adventures, and building from there, you cater not just to the Pathfinder folks, but also to people who don't play Pathfinder, or even D&D. You will get people who play all sorts of game systems purchasing the material and adapting it to their own games. This is a big win, because I am sure that after all of this time and all of these delays, Lone Wolf is chomping at the bit to see some cash flow!

Oh, and on a personal note - I want the Grand Temple of Jing as soon as possible! I have plans for that place! Bwahahaha!
 
Last edited:
How will RW > HL integration be handled in situations where the *.user file has not been released to the user?

I know we can embed portfolios in RW but they still require the underlying *.user file to pre-exist in Hero Lab in order for the content to work.

Lets say a new monster book is released via RW. Does that then come with the HL user file? Will installation be possible on HL for the purchased content within RW?

You should never be sharing ".user" files directly. You should be generating an export file to contain those files. Once you do that, the user just double-clicks that file and HL sucks it in and does the right things with it automagically.

So...

All you need to do is add a single "Foreign Object" snippet to the entry point topic for your exported RW content. This snippet is assigned the HL file you created above. And you can include some GM Directions atop that snippet to tell users what the file is and does, along with instructions to just launch the file from within RW. When the user does that, HL gets launched and the file gets sucked in.

Everything is ready to go, and it just requires a single snippet be added to your content! :)
 
Those are two different products with two different stores. So You would have to buy the product on both, or the 3PP doing the release would have to make both available I would think.

If the content is being sold separately for the two products, then separate purchases would be required.

For my take, if I decided to share out my Daede campaign, it would include the Daede.user file I have created to support the campaign in HL. But I am not a publisher for money on it, it would be just a dude sharing his work for others to use if they so desired.

In your case, you could easily leverage the approach that I outlined above for @daplunk.
 
You should never be sharing ".user" files directly. You should be generating an export file to contain those files. Once you do that, the user just double-clicks that file and HL sucks it in and does the right things with it automagically.
To build on this see THIS article on LW website on how to build the .hl file that Rob is talking about. Yes it talks about the iPad but all version of HL can suck in the "export file" (ie .hl file).

All you need to do is add a single "Foreign Object" snippet to the entry point topic for your exported RW content. This snippet is assigned the HL file you created above. And you can include some GM Directions atop that snippet to tell users what the file is and does, along with instructions to just launch the file from within RW. When the user does that, HL gets launched and the file gets sucked in.
This to me opens up a whole can of worms actually of potential issues. I will wait to see how the content market actually works before asking questions. I will for now safely assume that Rob has already foreseen those and worked them all out. :)
 
This is where I go back to some of my other comments in that Hero Lab and Realm Works need to become closer. One store, one cloud solution, one login that manages your license issues.

Given the two integrate it would not make sense to have to buy the content twice.

There will be users who want the Hero Lab stuff without Realm Works. There will be users who want the Realm Works stuff without Hero Lab. And there will be those that want both. That leaves us with two options: sell them separately or require users to pay the combined price for both when they only want one piece of it. We think users clearly would prefer the former option.

A common misconception is that users are paying for the same content multiple times. That couldn't be farther from the truth, as that would mean the exact same work is being done for writing the original material (by the publisher), creating the Hero Lab files, and getting everything folded neatly into Realm Works. I think everyone here on these forums is well aware that those are three RADICALLY different efforts. Yet they still get conflated with some regularity.

That being said, your proposal is absolutely a good one regarding a closer integration of the two products. In fact, that's something we're actively working towards behind the scenes right now. You'll be hearing more about that in the months to come. Once that happens, though, you'll still see a clean separation between the two products, at least for quite some time. The only thing we'd be able to do better is provide a discount to someone who wants both the Hero Lab AND Realm Works material, which is something we'd love to offer but currently cannot.
 
This to me opens up a whole can of worms actually of potential issues. I will wait to see how the content market actually works before asking questions. I will for now safely assume that Rob has already foreseen those and worked them all out. :)

Um, maybe. Maybe not. I'd vastly rather you flag the concerns NOW and have me confirm that it's already been considered than get blind-sided by something I overlooked in a couple months. :)
 
I'd like to see large amounts of complex content in Realm Works first. Ideally, I want everything (yeah, I'm a Pathfinder junkie), but my dream is for the Rise of the Runelords adventure path already entered into RW, since that's what my group's getting me to run.
 
You should never be sharing ".user" files directly. You should be generating an export file to contain those files. Once you do that, the user just double-clicks that file and HL sucks it in and does the right things with it automagically.

So...

All you need to do is add a single "Foreign Object" snippet to the entry point topic for your exported RW content. This snippet is assigned the HL file you created above. And you can include some GM Directions atop that snippet to tell users what the file is and does, along with instructions to just launch the file from within RW. When the user does that, HL gets launched and the file gets sucked in.

Everything is ready to go, and it just requires a single snippet be added to your content! :)
This opens up some exciting possibilities.

A campaign author could provide not just a RW realm but a customized HL export file that automatically had the campaign's languages, deities etc. available in HL without the purchaser needing to do a thing.
 
(...)
The one big concern I have with our revised Content Market approach is that it may become "the Wild West" for a short time. The original CM model positioned us as sort of "curating" the available content, since users could not share content outside of our ecosystem. Without that chokepoint in place, I can see multiple users providing the same or overlapping material, and it could even become "competitive" on some level. That's going to be confusing (and very annoying) for everyone. So we (Lone Wolf) may have to become involved in the process to some extent. I'm just not sure how that will unfold yet.

This is something that I'm definitely losing sleep over these days, as it's going to have a qualitative impact on the overall experience for everyone. This is probably the one biggest drawback accompanying the revised plan, but we felt the pros far outweighed the cons, and it seems the user community agrees with that view. We're still working to figure out how best to handle this wrinkle.

If it's going to be the Wild West for a while, perhaps what you need is simply some Sheriffs, to keep the metaphor.

Let the users go wild with things. It's a large new free open world. But for various community efforts, give us the tools to set up "mayors" and "sheriffs", people who coordinate community content creation efforts and who can gate the user-created content for inclusion in community packs.

Basically, the wikipedia approach. Would that work?
 
Alternatively, why worry about it at all?

If several content creators produce something similar then let them compete against each other. If it is something the community wants people will find the approach they like best and use it.

Look at the Steam Workshop. For a popular game many different modders may do essentially the same thing. People post reviews and the community figures out which ones are good and which ones aren't.
 
Um, maybe. Maybe not. I'd vastly rather you flag the concerns NOW and have me confirm that it's already been considered than get blind-sided by something I overlooked in a couple months. :)
Fair point. My concern would be now that you just turned RW into a source code repository tool that it has to be allowed to "update" the source file. The .hl file that contains the .user files is simply not guaranteed to work with each new update to the Pathfinder HL game. That is not a put down just a simple statement of fact. So the .hl file in the snippet has to have a way to be updated/changed/fixed.

Based on your comments before the content market data can be used in a way that the snippet would "point" to the data. In other words a full copy of the snippet/data would not need to be duplicated into each persons realm. My assumption is that when the data that is being pointed/referenced is updated that a person would be notified. Hence the same could happen to get a new .hl file to everyone.

I said you must have taken this into account as RW needs to be able to take into account changes/fixes/errata to published rules/adventures. But sense I have not seen the content market stuff yet I am not 100% sure.

If the above is not possible then the idea of supporting a secondary update URL in addition to the .hl file could be done. The GM Snippet could have info on setting up the URL into HL. So that future updates would happen from HL not RW. That is an alternate solution that is both good and bad.

The next issue I was seeing was that publisher ABC puts out a .hl file. They stop supporting the RW stuff or maybe go out of business. For community stuff the person simply gets bored of gaming and leaves. The .hl file stops working a year down the line when a new official Pathfinder update comes out. Another person (like myself) fixes the .hl file but now I have no way of getting the fixed file to everyone as I don't have authority to update the Realm the HL file is in. Leaving many people that don't check forums unable to use the HL part of what they got. :(

You asked but I am feeling this is derailing way off the threads topic... :o
 
If it's going to be the Wild West for a while, perhaps what you need is simply some Sheriffs, to keep the metaphor.

Let the users go wild with things. It's a large new free open world. But for various community efforts, give us the tools to set up "mayors" and "sheriffs", people who coordinate community content creation efforts and who can gate the user-created content for inclusion in community packs.

Basically, the wikipedia approach. Would that work?

There's one critical distinction wherein the core problem lies. Everything for wikipedia is wholly contained within wikipedia. So a "sheriff" would be someone that assists us within an ecosystem we controlled. Alas, users will be able to distribute content independently of us. As such, there is no way to appoint anyone "sheriff" and give them any actual authority whatsoever.
 
Back
Top