fvtt-mcp-molten5e: Skill for Claude Code

Scene builder

A judgment layer over the scene tools — it maps "here's a map, make it playable" into the right create-scene / update-scene calls with sensible dnd5e defaults and a couple of confirmable mood choices. It adds NO new mechanics; the tools hold all correctness (v14 field paths, fog/grid enum mapping, weather validation against the live CONFIG.weatherEffects, playlist/journal name→id resolution, and auto-detecting scene dimensions from the image).

Tools used: create-scene, update-scene, list-scenes, list-assets, upload-asset, list-playlists, list-journals / search-journals. To build a new playlist or journal to attach, hand off to the playlist-builder / journal-builder skill — scene-builder wires the link onto the scene; those skills author the content.

Regions & teleporters (on an existing scene). To connect two maps — stairs, a cave mouth, a portal — use create-teleporter: give a center point (canvas px, via get-scene-dimensions for the padding math) on each scene and it drops a grid-snapped trigger at each end and cross-links them two-way (or twoWay:false for one-directional). Transitions ask before moving (DM-approved house pattern): the default confirm:true sets core v14's choice flag so the player gets a "Teleport / Do Not Teleport" popup instead of being yanked between maps — pass confirm:false ONLY for traps/plot teleports that should fire silently. The same default applies when wiring a teleportToken via add-region-behavior (system.choice defaults to true; set it false explicitly to opt out). Name the pads (fromName/toName) — never ship default "Region" labels. NOTE: list-regions cannot read choice back and no tool edits a behavior after creation — a wrong teleporter is fixed by delete-region + rebuild. For arbitrary regions/behaviors use create-region (raw v14 shapes + behaviors), and list-regions / update-region (rename, recolor, or the rect reshape/resize) / delete-region to tune them. (remap-teleporters is import-only — it relinks a scene-pack's own teleporters after a Tom Cartos import; those keep whatever choice the pack authored. The create-* tools are for authoring new ones.)

Areas that DO something (dnd5e 6.0). A region can carry the system's own behaviors — the map itself applies the rules, no macro:

• dnd5e.applyActiveEffect — every token that ENTERS gets a copy of the named effects, and loses them on EXIT. create-region the shape (a rectangle / ellipse / polygon over the pool, the cloud, the altar), then add-region-behavior with effects: ["Poisoned"] — names come from the stock dnd5e.effects pack (every condition — Poisoned, Prone, Restrained, Blinded, Frightened, Invisible…; every damage Resistance / Immunity / Vulnerability; skill and ability Advantage / Disadvantage; Climb / Swim / Burrow Speed), or from an effect you authored on a world item with manage-effect (by name, or "Item name#Effect name"), or a premium spell's effect ("<Item uuid>#<effect>"). Filter with dispositions (["hostile"] = enemies only, e.g. consecrated ground that burns the undead: add creatureTypes: ["undead"]), sizes. Recipes: a poison pool → effects: ["Poisoned"]; brambles → effects: ["Restrained"]; a fog bank → effects: ["Blinded"]; a shrine → effects: ["Frightened Immunity"] for dispositions: ["friendly"]; lava has no "damage per turn" effect — that is executeMacro or a Battle Flow emanation, not this behavior.
• dnd5e.difficultTerrain — terrainTypes: ["web" | "plants" | "ice" | "mud" | "sand" | "snow" | "rocks" | "slope" | "liquid"] (a creature that ignores that kind — a spider in webs — walks freely), magical: true for a spell's terrain, dispositions = who IGNORES it. Movement cost doubles while the token plans a path through it.
• dnd5e.rotateArea — a turning platform / puzzle room: rotate: {positions: [0, 90, 180, 270], tiles: [...], walls: [...], lights: [...]} (ids from list-tiles / list-walls / list-lights, validated to exist) turns the listed placeables together around the region's first shape, stopping at the angles; direction (short / cw / ccw), timeMs. The DM triggers a turn from the region config (or a macro calling behavior.system.rotate()) — walking in does not turn it. Draw the region centred on the pivot.
• Effects the behavior applies live in a compendium or on a world item — never on an actor; the tool refuses an actor's effect (it would be duplicated on entry and deleted on exit). Wrong behavior = delete-region + rebuild (no behavior editing).