v13.0.0beta9, requesting help with transcribing Magic Item, and good news from Avast/AVG (Patreon)
Downloads
Content
I haven’t had a chance to say, even though it has already been 2019 for more than a week...
Happy New Year Everybody!
Now that’s out of the way, I present you with the next beta, v13.0.0beta9. This beta introduces nothing new, but fixes the numerous issues that were present with beta8.
I haven’t actually spent that much time working on this new beta, as I have mostly been spending my time with writing up the syntax for magic items and all ‘common attributes’ that are shared between class features, races, racial features, backgrounds, feats, and magic items.
With the syntax explanation now finished, I can finally call on all of you to help me with transcribing the magic items for use with the sheets! There are a crazy number of magic items to be found in the DMG and other sources, so help is much appreciated. For information on how to help, see below.
>> Find v13.0.0beta9 here <<
( https://www.patreon.com/posts/19406992 )
I would like to ask anybody who is willing, to help with transcribing the magic items for use with the sheet. This doesn’t have to include writing any JavaScript! What takes the most time is re-writing the descriptions of magic items in such a way that they fit on the sheets.
Attached to this post you will find a PDF that should help you with making the descriptions of magic items fit in the sheet. Note that there is no hard character limit on how long a description can be, but that you have to test the description out on the sheets to see if it fits. The attached PDF makes that easier by combining all different Magic Item description fields on one page, in a single file.
It also includes some tips on what to look out for when writing the descriptions, such as the fact that it should be written in the first person and ability scores should always be capitalised.
For the people who do want to help with the coding, the PDF in the attachment also contains links to my GitHub for the MagicItemsList syntax, as well as the common attributes syntax, and the work-in-progress file for all the magic items from the SRD.
Changes since the previous beta:
Fix for spellcasters with a spellbook not working;
Fix for spellcasters not getting the correct number of spells known;
Fix for feats not working;
Fix for armour not using ability score modifier correctly (e.g. Unarmored Defense);
Fix for Mage Armor not showing up in the drop-down box;
Fix for “Changes” dialog not always prompting to generate a new spell sheet;
Fix for skill proficiencies not being added to the correct skill when they are sorted by ability;
Fixed the ability scores override code not working properly;
Added some more Magic Items to the automation
Added support for the description of class’ features to be an array and be joined by line breaks and three spaces. For this to work, the array has to be enclosed in an array, e.g. [[“”, “”, “”]].
Beta7 and beta8 had some issues with core features of the sheet. I can imagine that after seeing the feats not working, armours not being available, or spellbooks not having any options, some people stopped testing and I can’t blame you.
All these issues have now been resolved with beta9 and I once again implore you to test if creating your character works as well (and hopefully better) than before!
Just like v13.0.0beta8 and the betas before it, this beta can't import a character from one of the previous betas (v13.0.0beta - v13.0.0beta8). This is a precaution, not a bug! This is done because the sheet can't accommodate all the intermediary changes that I had implemented in the other betas without being too convoluted. You will be able to import from v12.999 and older sheets, as well as from another v13.0.0beta9 pdf.
Great news from Avast/AVG for a change! Both Avast and AVG should no longer flag the betas as a virus. It took a lot of back-and-forth, but their virus experts were able to make the inspections of AcroForm PDFs work better.
If you still get a false positive from Avast or AVG, please make sure you have updated its virus database. If updating the virus database still causes false positives, please let me know.