d20 Release 1.4 Testing and Intergration...
Release 1.4 - ?/??/????
Enhancements & Changes
Bug Fixes
Data File Authoring
|
Quote:
|
Quote:
P.S. - I added your Pathfinder Improved Natural Attack feat to my house rules file and it works great. Thanks much for that. |
Quote:
I'm busy this week installing a VM for the Wiki, and I should have that upgraded/installed/ready by Sat. Your welcome on the INA edit. I'm not sure if it will get integrated, but if not we can keep it in the user mods section. I'm very detail oriented, like the Dawnflower edit, I made that because a Player added both to a PC and I needed to make sure that presented an error. I guess Mathis is not inclined to add if checks in non stacking things checking for their non stacking brothers? I can understand why. You would need to add more if's whenever new non-stacking things are created. |
This may not be for 1.4, but do we want to consider cleaning up names that have the book title? For instance, all the feats from RoS have (RoS) in the name of the feat. This appears to be fairly standard practice, but I wonder if its necessary.
I only bring this up because I was going to start working on the CPsi feats. The first one (Deep Vision) is also in Races of Stone. The easiest thing to do here is modify the RoS - Feats file to allow this feat with either source. Then I thought this might be confusing if someone had Complete Psionics selected, but not Races of Stone and sees a feat from RoS. I suppose I could just create a new feat and stop over-thinking it, but I wanted to get opinions from other developers on how to handle stuff like this. Any thoughts? |
Quote:
So in the scenario where a DM is using a book printed in 2002 and the feat was updated in a book printed in 2005 that the DM isn't using. The feat from the unused book in 2005 is the one by RAW the DM should be using. Anyway, I think we should use the newest version of the feat and tag them to both books. Then whichever book is enabled, they will get the same feat. Now, that being said. I'm not sure I like the book in the feat/feature like "(RoS)" unless there are multiple items that shouldn't be combined (not sure of why they wouldn't be combined based on the above "newest printing is only printing" rules.) So I'm in favor of removing the "(RoS)" tags. |
I agree with removing the book name from the feats. As is noted here updated feats overrule earlier versions.
When I added the complete warrior data I tagged the name CWar as a reminder of the source. However since more custom data has been added then duplicates have been uncovered. I think the replace Id mechanism is the best method to deal with older duplication, Users that don't have both sources flagged would only see the newer data. On a side note ETA on the MIC - Specific Weapons data, Friday 25th February. All weapons from Magic item compendium have been entered only the relic weapons need to be fully coded. I'm grinding through the deities and the respective abilities. Hopefully it should be in the 1.4 release. |
Yes, updated feats do over-rule earlier ones. In this case, the feats are the same though the wording in Complete Psionics is slightly different. I'm not sure that's a big deal, but what I will do is create a new feat that over-writes the old one and sources both books (since Complete Psionics is the "newer" version).
I would be happy to do some clean-up of the feat names as well if that's the general consensus. |
Quote:
Why not do as I suggest? Update the feat as printed in the newer book. Tag the feat as available in both sources. Done. |
Quote:
What if a DM wants to have this Feat work in a different way. The proper way is that they simply can do New(Copy) and a Replace Thing ID. The community should be able to treat our data set the same way they would the official version. So something else to keep in mind. I know at least for the Pathfinder stuff that is officially being added if a Thing is in two books the latest text is used and is Source marked to both books. |
All times are GMT -8. The time now is 04:49 PM. |
Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.