Skip to content

V13.8.0 Import Comparison & SPell Import Bug FIx

Choose a tag to compare

@GnollStack GnollStack released this 03 Mar 20:18

5e Item Importer v13.8.0

Foundry VTT Compatibility: v13.351+
D&D 5e System: 5.1.10+, verified 5.2.5

This release introduces a powerful post-import comparison view to verify parsed data and fixes a long-standing logic bug regarding item usage tracking. It also standardizes field names across templates to reduce ambiguity while maintaining full backward compatibility.

What's New

Import Comparison Window

A new "Compare after import" checkbox now appears next to the Auto-parse toggle. When checked, importing an item opens a separate side-by-side window showing your original template data vs. the created Foundry item.

  • Visual Diff: Mismatched fields are highlighted in red, missing fields in orange, and extra fields in blue.
  • Detailed Breakdown: Each discrepancy lists the expected value and the actual Foundry value side-by-side.
  • Summary Banner: Displays the total count of matched, mismatched, missing, and extra fields.
  • Full Support: Covers all item types including weapons, equipment, consumables, tools, containers, loot, and spells.
  • Batch Support: Batch imports display a compact per-item summary instead of full side-by-side cards.
  • Non-Blocking: The comparison window is resizable and independent; the main importer resets normally so you can continue working while reviewing results.

Improvements

  • Renamed Uses CurrentUses Spent: Updated all templates and parsers to use Uses Spent. The old name was ambiguous (unclear if "current" meant "remaining" or "consumed"). The new name matches Foundry's internal data model (system.uses.spent).
  • Backwards Compatibility: Legacy templates using Uses Current continue to work without changes. The parser now reads both fields, preferring Uses Spent if available.
  • USAGE fields now accept n/a: All templates now show Uses Spent and Uses Max as [integer|n/a], making it clear that items without limited uses can use n/a instead of forcing 0.
  • Clearer RECOVERY defaults: All templates now default to `RECOVERY: