1. Open the Items Directory dropdown and choose Add Activity or Add Effect.
2. Drop the target Item into the window.
3. Paste YAML or insert a quick-start template.
4. Parse it and review the preview cards. Resolve required document links.
5. Use Dry Run to check the import without changing the Item, then add the parsed activities or effects.

Auto-parse is enabled by default. Ctrl+Enter parses; Ctrl+Shift+Enter adds the current results.

Each activity starts with a top-level key such as ACTIVITY_ATTACK:; a standalone effect starts with EFFECT:. Raw YAML and one enclosing YAML code fence are accepted. Separate repeated top-level types with --- inside the fence; duplicate keys in one YAML mapping are invalid. Different types can share a document. Legacy ===ACTIVITY_*=== markers are not supported.

Start with the generation guide (templates/README.md in the installed module), authoring guide (docs/template-authoring.md in the installed module), and concrete examples (docs/examples/README.md in the installed module). Full references are in Base Activity Templates (templates/Base Activity Templates/ in the installed module) and Midi QOL Activity Templates (templates/Midi QOL Activity Templates/ in the installed module). Replace bracket placeholders before importing. Supply the actual reference files to an LLM; a link alone does not provide their contents.

The native dnd5e Order activity is not supported for import. Loot and Container Items can receive passive effects but cannot host activities.

Full templates document shared activation, duration, consumption, scaling, uses, recovery, range, targeting, and visibility fields, plus the fields specific to each type. The field coverage reference (docs/explicit-yaml-v2.md in the installed module) explains supported mappings and compatibility aliases. Use Active Effect Keys V2.txt (templates/Active Effect Keys V2.txt in the installed module) as an effect-key reference; a key’s behavior still depends on the system or integration that handles it.

Authored activation and duration use their own timing by default. Set the corresponding override to false when inheriting from the parent Item. The YAML controls are Override Activation, Override Duration, Override Range, and Override Target. Supported inactive values remain stored where documented.

Check skill/tool choices share one ability override and DC; use separate activities for different overrides or DCs. Foundry 14 Active Effects use one duration unit at a time. Cast needs a spell Item UUID; direct-link Summon and Transform need Actor UUIDs. A name used for lookup is not itself a resolved document link.

Dry Run checks the planned data without writing documents. Review any fields that were removed or converted, inaccessible links, and icon warnings before importing. A successful dry run does not execute activities, macros, resource consumption, MIDI workflows, or effect application.

Comparison displays the values the module knows how to extract. Some MIDI fields are missing from previews and comparisons; check those fields on the imported activity or effect sheet.

If an import fails partway through creation, the module attempts to remove the documents it created and reports recovery failures. A comparison or callback failure after a successful import does not roll that import back.

History retains up to 25 imports in the current client session. Undo removes the activities/effects created by that import; it is not a full Item snapshot. It checks the target Item, permissions, compendium lock, import fingerprints, and deletion results. Keep world backups for changes that import undo cannot restore.

Open Configure Settings → 5e Activity Importer.

Presets use a hidden client setting and stay with the current browser profile. Export them before moving to another browser. Import history is memory-only and clears on reload.

Confirm the world uses a supported dnd5e version and that Activity Importer is enabled, then reload. The Items Directory controls require Create Items permission; the target Item must also be editable. Locked compendia cannot be updated.

If parsing fails, check YAML indentation, replace reference placeholders, and separate repeated roots with ---. Review each error before importing. For unresolved Cast, Summon, or Transform links, search for or drag the actual document; Resolve All leaves a name unresolved if more than one document matches.

For more detail, enable Debug Logging (Advanced) and inspect the browser console. Test suspected integration conflicts in a separate test world with only the modules needed for the workflow.

The native catalog guide (docs/native-field-catalog.md in the installed module) and MIDI catalog guide (docs/midi-field-catalog.md in the installed module) describe field discovery and coverage. Discovery does not add import or export support.

The 14.1.2 release candidate was tested in Foundry 14.367 / dnd5e 5.3.3. For 14.1.3, read-only checks covered parsing, validation, the Item Importer handoff, and served assets on the same platform. These checks did not execute gameplay automation.

MIDI-QOL 14.0.9 and DAE 14.0.12 appear in recorded integration checks. A template passing validation does not prove that its automation works during play. The recorded tests cover specific workflows and settings on those versions.

Strict activity/effect export supports the documented native fields and rejects unsupported saved data from third-party modules. An active integration can add such data even to an activity created from a base template. Some inactive MIDI overtime values are omitted by import; consult the authoring and coverage guides when preserving existing data.

The importers can work together at different versions when both provide the features needed for the import or export. Other sheet replacements and module combinations may require separate testing. A declared minimum does not establish compatibility with all future releases.

The optional free 5e Item Importer is the supported companion for creating complete Items with activities and effects. The internal interfaces used by that integration are not offered as a supported public API for third-party modules or macros.

For other integration requests, describe the workflow you want to support on the Bakshi’s Bazaar Discord.