Skip to content

V13.8.2 Item Comparison Overhaul

Choose a tag to compare

View all tags
@GnollStack GnollStack released this 06 Mar 06:04
V13.8.2
daa80c7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

5e Item Importer v13.8.2

Foundry VTT Compatibility: v13
D&D 5e System: 5.2.x+

Item Import Comparison overhaul — fixes three bugs in the diagnostic comparison sheet and adds full coverage for inventory, description, and recovery fields.

Bug Fixes

  • Uses Display: Fixed display showing 0/5 on the expected side vs 5/5 on the actual side. Uses Spent stores consumed charges, not remaining — the expected side now correctly calculates remaining as max - spent.
  • Cost: Fixed Cost showing as "(not in template)" even when the template defines a price. The extractor was checking the wrong field (cost in copper instead of costDisplay).
  • Attunement Req: Fixed mismatch where the expected side showed full requirement text (e.g., "a character with a Strength of 15 or higher") while the actual side showed "Required". Both sides now display the normalized attunement value.
  • Reach: Fixed display issues where reach-only weapons showed a bare Range: ft on the expected side vs Range: 10 ft. on the actual side. Reach and Range are now extracted as separate rows; empty ranges are no longer shown.
  • Description: Fixed comparison producing false mismatches due to HTML entity differences and invisible unicode characters between template and Foundry-stored values.

Improvements

  • Inventory Section: New comparison added for Identified and Proficient fields.
  • Description Section: New comparison for Description, Chat Description, Unidentified Name, and Unidentified Description, with HTML stripped for clean text comparison.
  • Recovery Display: Enhanced to show full recovery details (e.g., dawn (formula: 1d4+1)) instead of just the period name.
  • Text Normalization: Improved comparison engine to handle non-breaking spaces, zero-width characters, and HTML entities for more reliable matching.
  • Template Documentation: All USAGE sections across templates and README now include a clarifying comment explaining that Uses Spent is the number of charges already consumed, not remaining. This assists LLMs in generating correct values.
Assets 4
Loading