• 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

Realm preferences

kbs666

Well-known member
In doing data entry for one of the publishers for the Content Market I came across an issue that will probably come up again and again.

Prefix sorting is not enabled by default but if the realm is meant to be viewed that way it should be on when the realm is acquired.
 
That's a good point, are preferences being kept from development of realm to passing it on through market place.

Mine are sorted same way.
 
Preferences are the domain of the user, not the content sellers. If your realm uses prefixes heavily you should mention that in the intro Topic and in the Market blurb, but you can't force your purchasers to use them.
 
Since each realm has its own setting for this I do not see why the setting cannot be part of the package when a realm is purchased.

I am a very knowledgeable user and know how to set up prefixes so they appear in front of topics and get sorted but a new user wouldn't. Shouldn't that less knowledgeable user simply be able to buy a package and have it work and look as the author intended?
 
Good point, but what if that user has things how they like and the Realm setting messes that up? I bet LW are giving this some serious consideration.
 
Since each realm has its own setting for this I do not see why the setting cannot be part of the package when a realm is purchased.

I am a very knowledgeable user and know how to set up prefixes so they appear in front of topics and get sorted but a new user wouldn't. Shouldn't that less knowledgeable user simply be able to buy a package and have it work and look as the author intended?

Yes, each realm has its own realm preferences. But what should be done when someone imports a package into an existing realm? Overwrite the user's own preferences with what the package author deemed ideal?
 
"Shouldn't that less knowledgeable user simply be able to buy a package and have it work and look as the author intended? "

As a writer/maker-of-school-handouts keen on the perfect appearance for the perfect understanding, I strongly sympathyse with this idea.

But the fact is, I would go berserk if I imported something into my realm that changed MY settings. (Even if I later do come to the conclusion the author is right!)

Like Parody said "mention that in the intro Topic and in the Market blurb", add instructions on how to do it (step-by-step pictures if need be) in the intro Topic. I don't usually get lost in instructions, but everyone loves step-by-step pictures - me included on my brain-dead days.

So yes, give detailed instructions on how to achieve the author's idea of perfect preferences for his/her material. But give the purchaser the choice to not reset his/her native preferences every time s/he buys something new.
 
Last edited:
Yes, each realm has its own realm preferences. But what should be done when someone imports a package into an existing realm? Overwrite the user's own preferences with what the package author deemed ideal?

Good point, I had only considered it from the idea that if I "passed" on my personal realm of Daede to another, it should come with "my" preset preferences. As there would be no user preferences to change.

If you are speaking of a "add-on" to a realm, like say buying Rise of the RuneLords AP that installs into the Golarion realm. Then yeah I would think the preferences that are present in Golarion realm should take precedent over what was in RotR.

This is where a product like RW gets very complex very fast.
 
This is the kind of thing I was thinking about in a previous post, when I mentioned that publishers may have some unworkable expectations about their control over the appearance of the Realms. I was thinking then more specifically of fonts and styles, but this fits the same mold.

In the end, it may be advisable to match the default settings of a new installation or RealmWorks. It may not be the "best" standard, but it is "a" standard that can be defined and adhered to.

I am reminded of Windows software development and monitors... although monitors supporting resolutions higher than VGA (640x480) have been around for some time, software developers (especially in corporate teams) had to assume VGA as the lowest-common-denominator for their applications...it had to be usable and have an acceptable appearance based on that, because that was the only thing you could assume (because Windows itself required VGA or better).
 
Yes, each realm has its own realm preferences. But what should be done when someone imports a package into an existing realm? Overwrite the user's own preferences with what the package author deemed ideal?
No. But this shouldn't be that complicated.

If a realm is bought and is not inserted into an existing realm then its settings should hold but if it is added to an existing realm then the settings should be compared and if there is a conflict the end user should get a popup asking them what they want to do.
 
If you always want something to appear at the front of the topic name, then put it at the front of the topic name (not as a prefix).

Then if you want the topic name without the "bit in front" to match up using auto-indexing, then create an alias name with just the basic part of the topic name to achieve this.

Then the user can use the preferences however he likes.
 
If you always want something to appear at the front of the topic name, then put it at the front of the topic name (not as a prefix).

Then if you want the topic name without the "bit in front" to match up using auto-indexing, then create an alias name with just the basic part of the topic name to achieve this.

Then the user can use the preferences however he likes.
You miss the point of prefixes.
 
Back
Top