Hi,
Errata changes can and should be implemented. However, it is not always as simple as people think.
We have a notes/comments in the pcc to track such things. I also think infotext should include the errata update notification.
Keeping "multiple" copies of sets is not feasible. Keeping two copies up to speed (6.06.x and master) is bad enough. Keeping bug fixes correct by errata would be a logistics nightmare.
As far as a JIRA. A single Data Feature Request for the errata update would be sufficient for EACH book that has an errata update.
Cheers,
Andrew
On 1/26/2016 2:26 PM, Doug Limmer adventure@mailworks.org [pcgen] wrote:
On 01/26/2016 04:16 PM, Saxum Caribetum saxum.caribetum@ntlworld.com [pcgen] wrote:
On 2016-01-26 21:44, Doug Limmer adventure@mailworks.org [pcgen] wrote:
Often times, what looks simple on the outside is nothing but on the inside.Ought to be simple: [...]In the specific case of the Scarred Witch Doctor, it sounds like it may require a somewhat major overhaul in how not only the data are set up, but how the code works. That will take ... a while.
DS/DL
__._,_.___
Posted by: Andrew <drew0500@yahoo.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (7) |
PCGen's Mailing Lists and Links: http://wiki.pcgen.org/Mailing_Lists_and_PCGen_Links
.
__,_._,___
No comments:
Post a Comment