• 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

Integrated SRD and early access (sorta) questions.

I do still believe that RW is primarily for fluff rather than crunch, but I have no issue with crunch being included where appropriate.

I get where you're coming from and understand you, I just think that fluff/crunch is an artificial divide. However, I also see myself putting in way, way, way more "fluff" than "crunch", like you.

<snip>

Now, since I'm not (yet, hopefully soon to change...) familiar with the tagging and linking features that RW has, would it require a consistent tag format for PRD items? Is RW smart enough to allow selection from a list? Can multiple tags with the same name exist?

I believe it was shown or mentioned, possibly in the Kickstarter video, that there is smart tag/linking - so if you put in a name and want it to auto-link, it will show you a list to choose from if there are multiple results.
 
I was thinking at cross-purposes. I have no intention of using Realm Works as a virtual tabletop and hadn't thought about it that way, just as a GM (or multi GM) tool.

Likewise the systems I play in or run only need the GM to have rules - players just need their character sheets.
 
No worries, like I said we all are going to have the best way for it to work for us.

At my group, we all have laptops and so we're eyeing this with that in mind and so the more we can have in RW, the better.

Were I in your position, I wouldn't care about putting all of the rules stuff in RW either.

I hope you're still going to write that guide though. :)
 
...Best case would be that RW can handle multiple tags with the same name and lets you choose none, one, or more of them each time it links something.

Yet another reason I can't wait to get my hands on it.

That's exactly how it works! (Based on my watching the Kickstarter video, reading the KS comments and looking over this forum.)

So if you have Fred the barman, Fred the innkeeper, Fred the Taxman, Fred the Watchman, Fred short for Romanadvoratrelundar, and Fred who works at the quarry, and then add info that said, "Fred went to bowling after work," RW would give you a list of all the Freds so you could decide which one (or none) it was...
 
Last edited:
I do want to write some tutorials once I actually get my hands on it. It'll put my academic learning as a librarian to some use. I specialise in metadata, and this package is 90% metadata and its proper use.

There are other workarounds as well you could use - if every player is using realm works, then you may as well be on the same network/wi-fi, so you may as well set up a shared drive with rulebooks on it :)
 
There are other workarounds as well you could use - if every player is using realm works, then you may as well be on the same network/wi-fi, so you may as well set up a shared drive with rulebooks on it :)

Yes, and we've done such things - but don't forget one of the potential benefits is the ease of sharing, without having to fiddle with network sharing or server software.

And if client-access is web based, then it means leveraging different operating systems and platforms (e.g. tablets or phones), transparently to the DM.

And from my own planning, I agree - metadata is going to be a big deal to plan and execute right, the first time. Or at least by the 5th time. :)
 
I've been trying to promote the use of existing standards for metadata to the developers - because basically, the folk that made them have already spent many months working out the best way to implement them and have written up the documentation on it.
It would a) save work and b) be a standard, compatible with other software
 
I've been trying to promote the use of existing standards for metadata to the developers - because basically, the folk that made them have already spent many months working out the best way to implement them and have written up the documentation on it.
It would a) save work and b) be a standard, compatible with other software

Where's the like button when you need one!
 
Back
Top