• 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

Custom Save locations and other Qs

I do want to embed mechanics in story content. That way skill checks, spells and mobs are identified as having information available.

If we can get a different color for mechanics links, that would be super-duper helpful. That way we could discern the two types of content.

Even better would be customizable link colors as I'd love mobs and NPCs to be the same color.
 
I think the question of auto-linking across the Story vs. Mechanics boundary is probably a very subjective matter. Lots of users have commented (here on the forums and elsewhere) that they can't wait to have the rules linked from all the story content that references them. It can be incredibly useful to just click on the mechanic name within the story content and view the appropriate rules. If we were to adopt your proposal, that capability would not exist. And I've got a feeling that lots of users would complain very loudly about that.

I'm not opposed to making this something that users can configure to their tastes, but it's definitely not a change to be made wholesale. And the question then becomes how many users feel the same as you on this matter, since that drives how to prioritize this relative to the zillion other things on our todo list. :)


I think you misunderstood my point. I was saying that there is likely more need for Story to link to Mechanics ("that Story will rely on Mechanics" is how I phrased it originally) than the other way around. There are very few, if any, use cases I can see for Mechanics to need to link to Story content.. but many the other way around.
 
I think you misunderstood my point. I was saying that there is likely more need for Story to link to Mechanics ("that Story will rely on Mechanics" is how I phrased it originally) than the other way around. There are very few, if any, use cases I can see for Mechanics to need to link to Story content.. but many the other way around.

Based on our experience with content entry thus far, there are very few (if any) instances where Mechanics articles are getting tripped up on terms used within Story topics. The terminology is just so different. So limiting Mechanics articles to only scan other Mechanics articles will yield no appreciable difference in behavior. At least, that's based on the content we've been working with on our end. I guess it's possible that other game systems may blur the lines more, but I'm not able to think of any examples that make any sense in this regard.
 
It's definitely something that we've mapped out for the future. However, it's not something that we'll realistically have in place relatively soon. We'll be doing another user survey a little while after the Content Market rolls out, at which point we'll be seeking user feedback on what capabilities are most important for us to focus on next.

Yes, I've noticed that using the tabs to flip back and forth on my content for comparison/editing was fluid and good. But what I was trying to portray was in HL a base set of system content that you don't want to (or often can't) change and leave alone, but that a 2nd instance of HL holding the modified bit of content that has its own data file.

I.E. using Pathfinder core files, looking at how the core system does something, then loading up the editor and creating a user specific set of files that get loaded into a player's HL file with the .user extension.

But from what I take from your reply is that RW is basically a different animal all together since each realm is a custom creation from the word go. It does make me wonder how the content market interacts then, however if I understand everything I've read on it is that once imported, one adds custom snippets and now that content becomes your unique content with one's custom spins not having any effect on the file hosted on the content market. Which is really cool stuff btw, looking forward to seeing it.

(also, i got to ask, does LWD plan on creating future RW content that they acquire licenses for such as Golarion or Shadowrun world setting, etc? that one can purchase, intergrate into one's master-realm file and then customize?)

As for the future of collaboration. I understand, get one thing down and working smoothly first and then build on it, and I'll definitely be looking forward to seeing it go live. Just sometimes i want my toys now darnnit! ;)

I do want to embed mechanics in story content. That way skill checks, spells and mobs are identified as having information available.

If we can get a different color for mechanics links, that would be super-duper helpful. That way we could discern the two types of content.

Even better would be customizable link colors as I'd love mobs and NPCs to be the same color.

I do the same thing as Aeiou does, perhaps I'm a little OCD here but my masterfile is a growing data base of system info, particularly since HL doesn't have an Exalted data-pack. This lets me integrate any errata that comes out and puts it all into one library of data so my players don't have to hunt through errata docs. I've been digging into customizing the links via case sensitivity and when it builds link to reduce the number of links in one article going to the same place due to grammar rules being in play, I've learned a thing or two about the menu of choices when building links. All cool stuff.

And briefly, I'd heartily welcome color coding to link, while custom coloring would of course be nice, I'd be happy with just general colors such as Blue leads to the World Almanac, Green = Story Almanac, Red = Mechanic Ref, just so that with a mere glance you know where those links have their containers.

Other Q's
I do seem however, to be operating under a flawed assumption with topic titles and link detection.

My assumption is that every character in the topic title helps make it a unique thing. I.E. Terrestrial vs Terrestrial-, vs Terrestrial-Breeding. Each as a separate topic title/article will have the auto-link detection pick up on the differences. But this is turning out not to be the case, or perhaps it would be but I'm not using the settings correctly.

Right now, if I let the links create by themselves, RW makes no distinction between them, all 3 point at the same thing and it doesn't even offer me a choice of which container to choose from, it points at the alias of "Terrestrial" es the only option. I have to create a custom link to the article I want the link pointing to.

So my question would be this: Does RW notice the difference in link detection with certain characters or even letter casing within a topic as separate thinks to link to?

A current example:
Topic Title = "Terrestrial" (used as an alias to the topic Dragon-Blooded, case matching = sensitive, Priority = normal)
Any text that uses "Terestrial" links to the Dragon-Blooded topic automatically upon approval (this is as I wish it to).​
Topic Title = "Terrestrial-" (with the hyphen)
Is desired to link to a different topic containing the hypen in the topic title, but instead links to article on Dragon-Blooded, the link created sees and marks as blue the word "Terrestrial" but ignores the hyphen forcing me to customize where it points at​
Topic Title = "TerrestrialX"
Is desired to auto-link to a yet another different topic containing the capital X on the end, instead it connects to the topic Dragon-Blooded just like it does with a hyphen on the end. No choices pop up to choose between "Terrestrial" or "TerrestrialX"​

Up till now, I thought case sensitive assigned via F7 "Manage Names would do the trick, for both the use of a hyphen (or any other symbol for that matter) or using upper case characters in the topic title, but this doesn't seem to be the case. What would be the recommend best practice for handling something like this?

Quick Note: My use of these terms is based on the desire to have Dragon-Blooded as a topic, Terrestrial as an alias to Dragon-Blooded, and a merit that a given Dragon-Blooded can buy called Terrestrial Breeding that grants specific enhancements depending on the investment. I like to keep all the merits of the game, regardless of race, under the topic container of "Merits". So putting this under a snippet in the Dragon-Blooded article goes counter to this intent.
 
For the hyphen, I know that at least some punctuation is ignored so that parenthesized entries without spaces between the term and the parentheses, for example, would work. There were persistent issues for people where the Topic "The Shadow" would not link if the text was like "Lamont Cranston (The Shadow) made his way... ".

A single trailing "X" may be treated like a punctuation mark.. an extraneous character that is being ignored as "not different enough" (though that's just a guess). Have you tried making it "TerrestrialXXX" instead of "TerrestrialX", or something equally different?
 
But from what I take from your reply is that RW is basically a different animal all together since each realm is a custom creation from the word go. It does make me wonder how the content market interacts then, however if I understand everything I've read on it is that once imported, one adds custom snippets and now that content becomes your unique content with one's custom spins not having any effect on the file hosted on the content market. Which is really cool stuff btw, looking forward to seeing it.

An important aspect of the December release will be the ability to export content and then import it back in. So you'll be able to create Realm1 as effectively a "master" realm. Then you can export it and import it into Realm2. You can then modify Realm2 independently of Realm1. You can also give your exported content to other users, and they can import it into their own realms. This approach becomes similar to you example of having a Hero Lab ".user" file that gets created and then used by others within Hero Lab.

(also, i got to ask, does LWD plan on creating future RW content that they acquire licenses for such as Golarion or Shadowrun world setting, etc? that one can purchase, intergrate into one's master-realm file and then customize?)

Absolutely! When we launch the Content Market in December, we'll have an assortment of material from a variety of publishers. We have a license in place with Paizo, so we'll definitely be releasing Pathfinder material. We're working on a license with other publishers, as well.

And briefly, I'd heartily welcome color coding to link, while custom coloring would of course be nice, I'd be happy with just general colors such as Blue leads to the World Almanac, Green = Story Almanac, Red = Mechanic Ref, just so that with a mere glance you know where those links have their containers.

Just in case there's any confusion, any content that exists within the Story Almanac automatically exists within the World Almanac. The World Almanac is ALL of your story content, while the Story Almanac is a subset of that material. :)

I'll tackle the linking issues in a separate reply, since this will otherwise be an overly big reply. :)
 
My assumption is that every character in the topic title helps make it a unique thing. I.E. Terrestrial vs Terrestrial-, vs Terrestrial-Breeding. Each as a separate topic title/article will have the auto-link detection pick up on the differences. But this is turning out not to be the case, or perhaps it would be but I'm not using the settings correctly.

Right now, if I let the links create by themselves, RW makes no distinction between them, all 3 point at the same thing and it doesn't even offer me a choice of which container to choose from, it points at the alias of "Terrestrial" es the only option. I have to create a custom link to the article I want the link pointing to.

So my question would be this: Does RW notice the difference in link detection with certain characters or even letter casing within a topic as separate thinks to link to?

A current example:
Topic Title = "Terrestrial" (used as an alias to the topic Dragon-Blooded, case matching = sensitive, Priority = normal)
Any text that uses "Terestrial" links to the Dragon-Blooded topic automatically upon approval (this is as I wish it to).​
Topic Title = "Terrestrial-" (with the hyphen)
Is desired to link to a different topic containing the hypen in the topic title, but instead links to article on Dragon-Blooded, the link created sees and marks as blue the word "Terrestrial" but ignores the hyphen forcing me to customize where it points at​
Topic Title = "TerrestrialX"
Is desired to auto-link to a yet another different topic containing the capital X on the end, instead it connects to the topic Dragon-Blooded just like it does with a hyphen on the end. No choices pop up to choose between "Terrestrial" or "TerrestrialX"​

Up till now, I thought case sensitive assigned via F7 "Manage Names would do the trick, for both the use of a hyphen (or any other symbol for that matter) or using upper case characters in the topic title, but this doesn't seem to be the case. What would be the recommend best practice for handling something like this?

Quick Note: My use of these terms is based on the desire to have Dragon-Blooded as a topic, Terrestrial as an alias to Dragon-Blooded, and a merit that a given Dragon-Blooded can buy called Terrestrial Breeding that grants specific enhancements depending on the investment. I like to keep all the merits of the game, regardless of race, under the topic container of "Merits". So putting this under a snippet in the Dragon-Blooded article goes counter to this intent.

There are certain characters that get handled specially by Realm Works. Specifically, these characters are various types of punctuation that get used in complicated ways within content. The hyphen is a perfect example of this, since the use of hyphens is problematic. Periods, commas, quotes, and parenthesis are other prominent examples of punctuation that need special handling.

Publishers are typically pretty consistent about their use of hyphens, but users rarely are. Consequently, the use of hyphens is treated more like a suggestion than a concrete rule. If you put hyphens in a name, then those hyphens will not be required to achieve a match. In general, this works well, since hyphenated terms don't usually appear without the hyphens and mean something different. For example, using the term "Dragon-Blooded", it really doesn't matter whether the text in a snippet is "dragon-blooded" or "dragon blooded". You won't usually find those two words together where they mean something other than the term "dragon-blooded". So this behavior accommodates the occasional imprecision of user-entered text without usually introducing any problems.

Punctuation like quotes, periods, and commas require special handling, as well. Users will frequently type "Dr Brown" when they should have typed "Dr. Brown" (with the period). The same applies for commas, such as "Fred Jones MD" vs. "Fred Jones, MD". Regular quotes are often used within content that comes out of published material and word processors that auto-convert, but users rarely take the time to properly enter them. In addition, we had lots of users treating quotes as more like suggestions, especially when nicknames are involved. So we ultimately decided to treat quotes as optional, matching whether or not the quotes are included, either within the topic name or the snippet text.

Parentheses are another big gotcha, since a fair bit of published content seems to be inconsistent with their handling. Consequently, we also treat parentheses (and square brackets and curly braces) specially. In general, these characters are considered optional for matching.

So that should address the behaviors you're seeing with the hyphen, as well as explain similar non-obvious behaviors you may encounter with further experimentation. But that doesn't explain the "Terrestrial" vs. "TerrestrialX" behavior, which sounds like a bug. In some very quick tests, though, I was not able to reproduce anything like this. So my obligatory question has to be whether you fully saved the name changes before attempting to resolve links to the names. Assuming you did, then I'd need to see your database to figure out what's going sideways. That means you'll need to open a support ticket and then send us your realm database. And it's critical that you include detailed instructions of what topics are involved and what steps you're taking that are yielding wrong results. I don't know what could be going wrong for you, and the only way to figure that out is to actually see the data for myself. :)
 
Read Rob's explanation about the linking and the handling of "odd" situations with interest. Good explanation.

So I went and did a little test.

I am entering the history of my world into RW, using the category "Incident" for each year of interest. My topic names are simply the year in question plus the abbreviation of the calendar system. For example

-64 AII
-24 AII
0 AII
5 AII
10 AII

Now, I also have a topic called AII.

All that is picked up is the AII when scanning for links - I would have expected to be given a choice of - say - "-64 AII" and "AII".

I can understand from Rob's explanation that it might be "by design" that the "-64" is ignored - and for a lot of good reasons.

I was wondering if it could be possible to somehow include years in the linking process, maybe by setting it up specially in the name function (CTRL + SHIFT + A).

If it is already possible to do so, please let me know how as I tried playing around and didn't find a way to do it.

LATER ADDITION:

Well, it seems to work fine if I select Auto Accept - otherwise it doesn't work - a tad odd, but it works :-)
I can live with that :-)

Now, if only we could batch edit things like that - and have RW bring the coffee... :-)
 
Last edited:
For hyphens, you may consider an en-dash or em-dash instead. For an em-dash, hold down ALT and type 0151. If you don't have a lot of the hyphenated words this might be a workaround.
 
An important aspect of the December release will be the ability to export content and then import it back in. So you'll be able to create Realm1 as effectively a "master" realm. Then you can export it and import it into Realm2. You can then modify Realm2 independently of Realm1. You can also give your exported content to other users, and they can import it into their own realms. This approach becomes similar to you example of having a Hero Lab ".user" file that gets created and then used by others within Hero Lab.



Absolutely! When we launch the Content Market in December, we'll have an assortment of material from a variety of publishers. We have a license in place with Paizo, so we'll definitely be releasing Pathfinder material. We're working on a license with other publishers, as well.

Oh my, both of these points have me a bit giddy. While I may not be as into PF as I once was, I still love dinking about with its world/content as well as Shadowrun and your first point gives me a great deal of ideas going forward that I'll be eager to explore once it goes live.

There are certain characters that get handled specially by Realm Works. Specifically, these characters are various types of punctuation that get used in complicated ways within content. The hyphen is a perfect example of this<snip>

Rob, first a hearty a thank you for taking the time to explain how RW handles punctuation, that shed light on a whole host of possible Qs that were floating around in my head and i totally get now why things are coded this way.

As for the possibility of a bug, unfortunately when i ran into the capital letter not being recognized (I.E. TerrestrialX) I dropped it from my data base figuring it didn't make the difference I had hoped. I'll be dinking around with other naming conventions as a alternative to the use of a hyphen or even off capital use.

Now, if only we could batch edit things like that - and have RW bring the coffee... :-)

I think my copy of RW would start telling me I should lighten up on the coffee loads :rolleyes:

For hyphens, you may consider an en-dash or em-dash instead. For an em-dash, hold down ALT and type 0151. If you don't have a lot of the hyphenated words this might be a workaround.

Sadly, because I was under the mistaken impression that a hyphen would be seen as a totally different character I got a bit more than a few. I'm going to clean that up now that I understand more of the effects of punctuation. I tried your code but all I get is Win7 giving me 'don't do that' pings. I've tried highlighting the hyphen and Alt+0151 and at a blinking cursor on a editable field and get the same result. Typically it opens up a set of short cuts using the alt button instead.

However it did give me a idea I got curious to explore when I get more time today. I'm thinking of trying out symbols in the topic titles, specifically using the Tahoma font's symbol collection such as
Ǎ ¦ È Է
among others.​

I'm a bit OCD about consistency so maintaining their use throughout the work wouldn't be a issue for me, but I've noticed that I can't make use of symbols via the create topic button or Cntrl+Q, however I can highlight the text and Cntrl+Q and it'll insert the symbol into the topic title (or at least, it appears to, I haven't tried that and building links yet). I'll experiment with this later on tonight and get back with some results, unless there's some feedback to this idea to discourage its use or any caveats I should be aware of.

Thank you all for your many contributions and answers, you have collectively been a huge asset to me with your replies. :D
 
I tried your code but all I get is Win7 giving me 'don't do that' pings. I've tried highlighting the hyphen and Alt+0151 and at a blinking cursor on a editable field and get the same result. Typically it opens up a set of short cuts using the alt button instead.
You have to type the numbers on the numeric keypad while holding down Alt the entire time: [Hold Alt][Num0][Num1][Num5][Num1][Release Alt] = —.

If you don't have a numeric keypad you can't enter special characters this way. You can still use Format/Symbol in Realm Works to insert special characters in Text Snippets or copy/paste characters out of a Text Snippet, the Character Map (a program that comes with Windows), your favorite word processor (which likely has its own method of inserting special characters), or your chosen browser.

Note that some laptop/compact keyboards provide numeric keypad keys while holding down [Fn], but that may not work for this. All you can do is try it and see. :(
 
Last edited:
Thank you for the clarification, Parody. The secret is to hold the ALT key down while you press the four numbers, then let go and the symbol magically appears. I use 0151, 049 and 076 all the time.

— <-- this is what the em-dash looks like. It's slightly longer (wider?) than a standard dash as it's the size of a capital M. You should be able to copy/paste this to your work if the ALT+0151 isn't possible for you..
 
You cannot use HTML entities for things like the EM Dash or any other special symbol. Just in case anyone else tries.
 
An old application that is still on Windows is "Character Map"

You can use this to find special characters and their codes. You can also use it to copy the selected characer(s) to the clipboard.
 
Read Rob's explanation about the linking and the handling of "odd" situations with interest. Good explanation.

So I went and did a little test.

I am entering the history of my world into RW, using the category "Incident" for each year of interest. My topic names are simply the year in question plus the abbreviation of the calendar system. For example

-64 AII
-24 AII
0 AII
5 AII
10 AII

Now, I also have a topic called AII.

All that is picked up is the AII when scanning for links - I would have expected to be given a choice of - say - "-64 AII" and "AII".

I can understand from Rob's explanation that it might be "by design" that the "-64" is ignored - and for a lot of good reasons.

I was wondering if it could be possible to somehow include years in the linking process, maybe by setting it up specially in the name function (CTRL + SHIFT + A).

If it is already possible to do so, please let me know how as I tried playing around and didn't find a way to do it.

LATER ADDITION:

Well, it seems to work fine if I select Auto Accept - otherwise it doesn't work - a tad odd, but it works :-)
I can live with that :-)

Now, if only we could batch edit things like that - and have RW bring the coffee... :-)

This sounds like a bug. There should be NO difference between auto-accept and normal link detection, except for not bothering you with the prompt. Please open a support ticket and report this situation with all the details you've provided above (and anything else you think might be helpful).

Beyond that, I have to question whether it's all that useful to have a topic named with a calendar year. With the published content we're entering, we use the actual incident as the name. For example, the topic names would be "Time of Darkness", "Great Flood", "Awakening of the Ancients", etc. Then we assign the calendar year as the prefix. The net result is that the events all get properly shown in chronological order (assuming you're sorting by prefix) and all references to one of the events (e.g. "Great Flood") throughout the text get auto-detected and linked up.

Based on the above usage that we've adopted, I'm honestly not sure if we've ever actually tested with topic names being driven by numbers. So (a) this may be a bug and (b) this may not be the best way of modeling the situation within your realms. :)
 
For hyphens, you may consider an en-dash or em-dash instead. For an em-dash, hold down ALT and type 0151. If you don't have a lot of the hyphenated words this might be a workaround.

I don't remember for sure, but we may treat all three types of "dash" the same during link auto-detection for some of the same reasons cited above. So this suggestion might not yield the desired results.
 
You cannot use HTML entities for things like the EM Dash or any other special symbol. Just in case anyone else tries.

RW is a Windows application, so everything in the UI operates using Rich Text. When the material is saved out, we convert it to HTML, and vice versa. Consequently, anything you enter into the UI is going to be treated as literal text. So entering and HTML entity like ">" will ultimately be saved out as the HTML "&gt;".
 
This sounds like a bug. There should be NO difference between auto-accept and normal link detection, except for not bothering you with the prompt. Please open a support ticket and report this situation with all the details you've provided above (and anything else you think might be helpful).

Beyond that, I have to question whether it's all that useful to have a topic named with a calendar year. With the published content we're entering, we use the actual incident as the name. For example, the topic names would be "Time of Darkness", "Great Flood", "Awakening of the Ancients", etc. Then we assign the calendar year as the prefix. The net result is that the events all get properly shown in chronological order (assuming you're sorting by prefix) and all references to one of the events (e.g. "Great Flood") throughout the text get auto-detected and linked up.

Based on the above usage that we've adopted, I'm honestly not sure if we've ever actually tested with topic names being driven by numbers. So (a) this may be a bug and (b) this may not be the best way of modeling the situation within your realms. :)

Bug report sent in.

I prefer the "by year" approach as most of the entries (topics) does not have names.

If I note for a NPC that he was born in 512 AII the year will be linked and I can go and read what happened that year (be it nation-shattering or just trivia).

Also, one year (topic) might detail many events happening all over the empire and outside of the known world (for the PCs).

From a world creation and management aspect this seems the right approach :-)
 
Bug report sent in.

I prefer the "by year" approach as most of the entries (topics) does not have names.

If I note for a NPC that he was born in 512 AII the year will be linked and I can go and read what happened that year (be it nation-shattering or just trivia).

Also, one year (topic) might detail many events happening all over the empire and outside of the known world (for the PCs).

From a world creation and management aspect this seems the right approach :-)
I will point out that this makes more sense from the way things like Wikipedia does articles on years. Major events in a year may get their own article but the year itself has its own article.
 
Back
Top