• 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

Replacing thing by preexisting thing

F

frumple

Well-known member
Is there a way for a thing I create (thing #1) to be replaced by a thing that already exists (thing #2) if the user has the source for thing #2 selected? (Kind of reverse replace thing id... a replace by thing id)

For example, a race in one of the APs being replaced by a later version that appears in one of the Bestiaries? If they have the AP selected but not the particular Bestiary HL uses the AP version. If they have the Bestiary and AP sources selected the Bestiary version is used.

I guess what I am asking is it possible to script the replaces="" attribute in a thing. (I tried amendthing, but that only works for name and description).

If not, can we get this as a feature? It will be very useful for the purposes of things being replaced and updated as time goes on.
 
If a bestiary was published after the AP, then the AP version is obsolete, and should be replaced by the bestiary version all the time. Hardcovers trump softcovers, and later publishings trump earlier publishings.
 
Yep. That is what I am trying to do. However, you cannot just delete the previous instance. It will break the por files. I figured if we can do above, it allows a way to keep files up to date without breaking any existing por files.
 
If you have two different 'sources' why not just have two different Races? It sounds like you have Race1 come out in book1. They re-print the race in book2 with different stats. I would think that you would simply want two different races tagged to two different sources.

Then it is up to the DM to decide which version they want.

What Mathias is talking about is similar to the Psionics stuff. So we originally had Psion in Psionics Unleashed. Then the new Psion comes out in Ultimate Psionics. So we simply updated the Psion class to the latest book rules. Everyone gets the latest rules than.
 
If this is a race you added to the community files, and since then there's been a bestiary version, I'd just add the Helper.Obsolete tag to that race - that way, existing portfolios with the old one will still be usable, and new portfolios with this monster can be created using the current version.
 
Mathias said:
If this is a race you added to the community files, and since then there's been a bestiary version, I'd just add the Helper.Obsolete tag to that race - that way, existing portfolios with the old one will still be usable, and new portfolios with this monster can be created using the current version.
Click to expand...
Currently I have been using *HIDDEN to deprecate stuff. How is "Helper.Obsolete" different? Currently with *HIDDEN the "Thing" does not toss an Error but it shows in "RED" on the character. Then I change its name to be "DEPRECATED" with an FYI how to remove and what "to" re-add.

Will do some testing of Helper.Obsolete to see how it works.

Update: So Helper.Obsolete simply prevents "new" stuff from being created with the Thing. I sort of like *HIDDEN as it allows me to bring to the attention that the Thing is in red and needs to be removed.
 
Last edited:
Mathias said:
We don't use *Hidden in our own files - that's why I think first of Helper.Obsolete.
Click to expand...
Always good information and "may" use that for somethings. But just have a preference of the way *HIDDEN makes it more "obvious" to a gamer is all.

As always thanks for the info and knowing is half the battle! :)
 
You must log in or register to reply here.
Back
Top