Releases: GnollStack/5e-Item-Importer
Release list
V14.1.0 Auto-Animations Bug Fix
5e Item Importer v14.1.0
Foundry VTT Compatibility: v14 (verified 14.363)
System Compatibility: D&D 5e 5.3.3+
This release focuses on weapon imports: better Automated Animations coverage, smarter projectile and thrown-weapon handling, and more accurate icon matching for spears, pikes, and other polearms.
What's New
- Wider Automated Animations coverage: Many more base weapons now get animation flags on import, including sickle, whip, morningstar, war pick, light hammer, javelin, lance, blowgun, and net. Each weapon falls back through related animations (for example, a pike prefers a spear animation and falls back to glaive) so it lands on something sensible.
- Animations that actually exist get picked: When your Sequencer/JB2A database is available, the importer now checks each candidate animation and selects the first one that's installed instead of assigning a missing one.
- Thrown and returning weapons: Thrown melee weapons (dagger, handaxe, spear, javelin, trident) get a proper melee-to-ranged switch with the correct projectile, and weapons with the Returning property now fly back to the hand.
Improvements
- Smarter weapon icon matching: Spears, pikes, and sarissas now select spear/polearm icons and avoid grabbing unrelated halberd, glaive, or axe art. Javelins now pull from polearm icons, and icon scoring uses keyword aliases for closer matches.
- More reliable on browser-hosted worlds: Animation flag IDs now generate correctly even when the browser doesn't expose
crypto.randomUUID(common on non-secure-origin or self-hosted setups). - Firearm and crossbow ranged fallbacks: Guns fall back to a bullet animation and crossbows to a bolt, instead of a generic arrow.
Bug Fixes
- Fixed thrown weapons defaulting to a generic dagger projectile and not respecting return behavior.
- Fixed weapon icon selection occasionally choosing unrelated art (such as a halberd icon for a spear).
- Fixed issues with weapons not able to have auto animations put upon them.
Manifest URL: https://github.com/GnollStack/5e-Item-Importer/releases/latest/download/module.json
V14.0.0 Version 14 Jump
5e Item Importer v14.0.0
Foundry VTT Compatibility: v14+ verified through v14.363
System Compatibility: D&D 5e v5.3.3+ verified through v5.3.3
Safe to update mid-campaign: yes, if your world is already on Foundry v14 and dnd5e v5.3.3+
This release starts the V14-only line for 5e Item Importer. If your table has moved to Foundry VTT v14 and the current dnd5e system, this is the release to use; if you are staying on Foundry v13, remain on the last stable v13-compatible releases.
What's New
- Foundry V14 support: The module manifest now targets Foundry VTT v14 and is verified against v14.363.
- dnd5e 5.3.3 support: The dnd5e system requirement has been updated and verified for v5.3.3.
- V14-only release line: Future releases in this line will target Foundry v14 rather than trying to maintain dual v13/v14 compatibility.
Improvements
- Updated the README compatibility badge, requirements table, and footer compatibility text for the V14 release line.
- Refreshed maintainer documentation and source-reference notes for Foundry v14.363 and dnd5e v5.3.3.
- Replaced stale V13-specific wording in item data comments with generation-neutral dnd5e wording.
Bug Fixes
- Fixed an advanced validation check that could incorrectly report valid internal settings as invalid.
Migration & Save Safety
- Back up your world before updating.
- Migration steps: No manual item or world-data migration is required.
- Existing module settings, imported items, flags, URLs, and public integration contracts are preserved.
- Foundry v13 users should not install this release line; use the last stable v13-compatible release instead.
Tested in Foundry v14.363 with dnd5e v5.3.3; local maintenance checks and live module validation passed.
Manifest URL: https://github.com/GnollStack/5e-Item-Importer/releases/latest/download/module.json
V13.9.1 Further debug and Readme Changes
5e Item Importer v13.9.1
Foundry VTT Compatibility: v13+
System Compatibility: D&D 5e 5.1.10+; verified with dnd5e 5.2.5
v13.9.1 focuses on making Strict Format imports easier to trust, especially when text comes from LLMs, copied docs, or messy paste sources. It also refreshes the README, examples, and template guidance around current dnd5e text features.
What's New
- LLM-tolerant Strict YAML parsing: Strict imports now correct common paste and generation issues before parsing, including UTF-8 BOMs, smart quotes, leading tabs, and missing spaces after colons.
- Typed damage formulas: Weapon and ammunition imports can use dnd5e bracketed damage formulas like
1d8[piercing] + 1d6[lightning], making mixed damage clearer. - Validated custom examples: The README now includes tested custom YAML examples for every supported item type, plus mixed-batch and same-type batch examples.
- Template download links: The README now points to the actual strict template files as the source of truth, with raw download links for each template.
Improvements
- Reworked the README with a Quick Start, Feature Index, Preview, Compatibility table, Common Issues, and cleaner navigation.
- Updated strict templates and quick snippets with dnd5e enrichers, roll formulas, System HTML guidance, and
[[lookup @name]]examples for active narration. - Improved tool imports for current dnd5e tool IDs while keeping legacy short IDs accepted.
- Made container imports more forgiving: currency contents can be omitted, and volume/weight units normalize more reliably.
- Added GitHub issue templates for bug reports, parser/template issues, feature ideas, and localization ideas.
Bug Fixes
- Fixed strict YAML imports that failed because pasted text contained a leading BOM, smart quotes, leading tabs, or
Key:valueformatting. - Fixed strict parser defaults so the module’s Create Items as Identified setting is respected.
- Fixed damage validation so fully typed formulas do not require a separate damage type field.
- Fixed spell preparation handling to map current dnd5e values correctly.
- Fixed README links, anchors, support/license text, and old copied template sections that could drift out of sync.
Settings Changes
- Show YAML Normalization Warnings: Shows warnings when the parser auto-fixes common YAML issues. Default:
false. - Replace Generated Default Activities: When importing inline activities with 5e Activity Importer active, prevents dnd5e from adding a duplicate generated default activity when the imported activity already covers it. Default:
true.
V13.9.0 Reliability Fixes
5e Item Importer v13.9.0
Foundry VTT Compatibility: v13+
D&D 5e System: 5.1.10+ (verified through 5.2.5)
This combined release focuses on parser reliability, dnd5e 5.2.x compatibility, safer import previews, more reliable YAML handling, and cleaner fallback behavior. The goal is simple: imported items should behave more like native current-system items, require fewer manual fixes after importing, and process data more safely when optional modules are unavailable.
What's New
- Current dnd5e schema alignment: Spell, tool, container, and siege-weapon imports now map more cleanly to the current dnd5e item model.
- YAML template refresh: The built-in YAML examples and strict template files were updated to match the current parser behavior and recommended field values.
- Default item type fallback: Natural-language imports now honor the configured default item type when the parser cannot infer one.
- Bare YAML fence support: Imports now handle plain triple-backtick fenced blocks, not only language-tagged fences like
yamlormarkdown.
Improvements
- Tool imports now use current artisan base item IDs like
alchemist,calligrapher, andwoodcarver, while still accepting legacy short IDs for older content. - Container parsing now supports current unit values like
MgandcubicFoot, and no longer assumes every container needs aCURRENCY_CONTENTSsection. - Safer preview rendering: Item comparison and preview output now escapes user-controlled values before display.
- Safer folder rendering: Folder names are rendered through DOM text nodes instead of injected innerHTML.
- Optional Activity Importer handling: Integration now validates expected helper exports and falls back gracefully when the optional module is missing or incompatible.
- Clearer preview messaging: The preview now accurately states when inline activities and effects will be skipped because
5e-activity-importeris inactive. - Setting respected: The "Create Items as Identified" setting is respected again in generated YAML and natural-language import flows.
Bug Fixes
- Fixed standard spell imports so they use the current spell preparation method instead of the legacy
preparedvalue. - Fixed batch item selection toggling twice in the import window.
- Fixed import summaries counting failed item creation as successful imports.
- Fixed siege weapon cover importing as text labels instead of the numeric values dnd5e expects.
- Fixed the built-in tool template so its example item, ability, and description now match each other.
- Fixed imported item names and properties being rendered as HTML in the comparison window.
- Fixed folder names being inserted through innerHTML.
- Fixed activity helper export drift causing parsing failures.
- Fixed fallback activity parser handling when the expected export is unavailable.
- Fixed negative weight validation by checking the correct D&D 5e weight path.
- Fixed bare fenced YAML blocks not being stripped before parsing.
- Fixed the unused
defaultItemTypesetting and removed the unsupportedbackpackoption.
V13.8.4 Improved Templates
5e Item Importer v13.8.4
Foundry VTT Compatibility: v13+
D&D 5e System: 5.2.x+
This release is a documentation and template pass — no code changes. All seven strict YAML templates have been improved for LLM generation accuracy, and the README has been synced to match.
Improvements
- Stronger LLM instructions across all templates: Added an explicit rule that conditional sections (
ATTUNEMENT,MATERIALS,AREA,ARMOR, etc.) must be omitted entirely when their condition isn't met — not filled withn/a. Also clarified thatn/aapplies only to scalar field values, and addedeffects:to the list of sections to omit unless explicitly requested. SPELLadded to supported batch keys in all non-spell templates: You can now batch aSPELLtogether with aWEAPON,LOOT,EQUIPMENT, etc., in a single YAML block without switching templates. The batch key documentation in all six non-spell templates now lists all seven types.effects:section added to all templates: Each template now has an expliciteffects:section (distinct fromActivities:) with comments describing its purpose — passive Active Effects that are always-on mechanical modifications. Makes theSPELL/LOOT/WEAPONetc. templates compatible with the 5e-activity-importereffects:workflow without ambiguity.RECOVERYformat standardized (Weapon, Equipment, Consumable, Tool): TheRECOVERYblock now usesRECOVERY:[]with commented-out entries in all templates, matching the Spell template's established format. The previous dash-list format implied there was always a recovery entry;[]clearly signals the default empty state to LLMs.- README synced: The README's embedded template copies now match all of the above changes, plus previously missed additions from the prior release — the Loot template's
tradeloot type and the Spell template's spellcasting Ability override field and advancedAREAfields (Count,Width,Height,Contiguous).
Bug Fixes
- Fixed the README embedding for the Loot template missing the
tradetype from the Loot Type field options. - Fixed the README embedding for the Spell template missing the Ability override field in the ITEM section, and the
Count/Width/Height/Contiguousfields in theAREAsection. - Fixed
USAGEfields in Weapon/Equipment/Consumable/Tool README embeds showing[integer]instead of the correct[integer|n/a]with explanatory comments.
V13.8.3 Bug Fixes
5e Item Importer v13.8.3
Foundry VTT: v13 (verified 13.351)
D&D 5e System: 5.1.10+ (verified 5.2.5)
Maintenance release focused on reliability. No new features — just fixes for bugs that could cause silent failures or unexpected behavior.
Bug Fixes
- Fixed spell items not being recognized when using the programmatic API (
api.parse()andapi.import()).SPELLwas missing from the API's type key list, so YAML spell blocks were being routed to the natural language parser instead of the strict YAML parser. - Fixed a crash-loop when importing a single item fails — the import button would stay stuck showing a spinner with no way to recover. Errors now show a notification and reset the form properly.
- Fixed the "Export to Text" option appearing in the item right-click context menu. The feature isn't implemented yet, so it's been hidden until it's ready.
- Fixed a ghost timer that could fire after the import window was closed, causing a harmless but noisy error in the console.
- Fixed module settings being registered across two separate init hooks, which could cause ordering issues depending on Foundry internals.
Improvements
- The programmatic API (
api.parse()andapi.import()) now returns structured error objects instead of throwing unhandled exceptions when something goes wrong — easier to handle in macros and other modules. - YAML format detection no longer recompiles regex patterns on every parse call.
V13.8.2 Item Comparison Overhaul
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 (
costin copper instead ofcostDisplay). - 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: fton the expected side vsRange: 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
IdentifiedandProficientfields. - Description Section: New comparison for
Description,Chat Description,Unidentified Name, andUnidentified 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
USAGEsections 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.
V13.8.1 Proficiency Bug Fix
5e Item Importer v13.8.1
Foundry VTT Compatibility: v13+
D&D 5e System: dnd5e 5.2.x+ Verified
Bug fix release correcting how proficiency is set on imported weapons, equipment, and tools.
Bug Fixes
- Fixed proficiency field using incorrect keys and values for weapons, equipment, and tools. The importer now uses the correct Foundry data model values:
Automatic— lets the game auto-detect proficiency from the character (default)0— not proficient1— proficient
- Previously, items were being set with text-based proficiency values (
proficient,notProficient,automatic) that Foundry didn't recognize, causing proficiency to behave incorrectly on imported items. - Tools no longer hardcode proficiency to
1— they now respect the parsed value and default toAutomaticlike weapons and equipment. - Fixed tool expertise mapping — the natural parser was incorrectly mapping "expert" to
1(proficient) instead of2(expertise). - Tools now support the full range of Foundry proficiency levels:
Automatic,0(not proficient),0.5(half proficiency),1(proficient),2(expertise).
Improvements
- Updated all strict YAML templates (Weapon, Equipment, Tool) with a Proficiency field reference table so LLMs generating items know exactly which values to use.
- Template field renamed from
ProficiencytoProficientto match Foundry's internal key.
V13.8.0 Import Comparison & SPell Import Bug FIx
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 Current→Uses Spent: Updated all templates and parsers to useUses 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 Currentcontinue to work without changes. The parser now reads both fields, preferringUses Spentif available. USAGEfields now acceptn/a: All templates now showUses SpentandUses Maxas[integer|n/a], making it clear that items without limited uses can usen/ainstead of forcing0.- Clearer
RECOVERYdefaults: All templates now default to `RECOVERY:
V13.7.2 Property and Attunement Fixes
5e Item Importer v13.7.2
Foundry VTT Compatibility: v13 (verified 13.351)
D&D 5e System: 5.1.10+ (verified 5.2.5)
This release addresses compatibility bugs regarding magic item properties and attunement in dnd5e 5.x, and adds proper support for passive effects and extra activities directly in item templates for the upcoming release of the activity importer.
What's New
Passive Effects Support
- Separate
effects:section: Passive Active Effects (always-on modifiers like an AC bonus while attuned) now have their own dedicatedeffects:section in the item templates, distinct from theActivities:section. This mirrors the dnd5e data model where effects are distinct from activities. - Case-insensitive keys: The parser now recognizes
effects,Effects, orEFFECTSto handle LLM casing variations.
LLM Parser Resilience
- Activity Dictionary Recovery: If an LLM outputs
Activities:as a dictionary instead of an array, the parser now auto-converts it and logs a warning rather than silently dropping the data. This is for the upcoming release of the activity importer.
Bug Fixes
- Magical Property (
mgc) Tag: Fixed an issue where magical properties failed silently on import. The dnd5e 5.x system expects item properties to be aSet, but they were being written as plain objects or arrays. This fix ensures.add("mgc")is called correctly for Weapons, Tools, Containers, and Loot. - Magic Weapon Bonuses: Fixed the field used for magic bonuses. Previously,
system.bonuswas being set; this has been corrected tosystem.magicalBonus. Weapons with +1/+2/+3 bonuses will now correctly apply them to attack and damage rolls. - Attunement Status: Fixed attunement not being set on Tools, Weapons, Consumables, and Loot. The YAML parser previously stored attunement as a boolean (
true/false), but Foundry requires specific strings ("required"/"optional"). Items will now import with the correct attunement state.
Improvements
- Template Updates: All seven strict templates (Weapon, Equipment, Consumable, Tool, Loot, Container, Spell) have been updated to clearly document the difference between
effects:andActivities:, including examples for the upcoming release of the activity importer. - Weapon Template Logic: The Weapon template now explicitly notes that dnd5e auto-generates the default attack activity, clarifying that the
Activities:section should only be used for extra capabilities.