Create working door and window tokens when using Dungeon Draft dd2vtt import

[melek]

Is your feature request related to a problem? Please describe.
When importing universal tabletop format maps into MapTool, doors in the import JSON are ignored. Sometimes, I miss a door when setting up the map, affecting gameplay.

Since this data is available in the JSON, it would be nice to use it!

Describe the solution you'd like
I would like to add a token added for each portal with the following attributes:

• Appearance: I like 50% opacity icons from game-icons.net half a cell ("tiny" size), positioned on the center of the portal.
• Image: In DungeonDraft, windows are also portals, but unlike doors they are not a full grid cell wide.
  • A 'Door' icon for portals about full cell width wide or wider.
  • A 'Window' icon for portals smaller than that (in DungeonDraft, it appears windows are ~0.777344 cells wide). The cutoff could be arbitrary, something like .78 or 85 cells.
• Layer: Placed on the Hidden layer, like the light tokens.
• Properties: These properties pre-populated would be valuable for macros.
  • dd2vtt.portal.json - The initial imported JSON without changes. (Light tokens could have a similar property, dd2vtt.light.json). This would be very useful for library add-ons to detect and replace/update/use these doors with all the initial information (such as perfectly placing a 'Smart' door on thresholds automatically).
  • dd2vtt.portal.closed - Begins with the 'closed' value of the initial JSON. Intended to be toggled by macros.
  • dd2vtt.portal.shapeList - The VBL shape for the door, in absolute pixel coordinates.
• Macros: A few lightweight macros to use the door effectively, without overloading the user:
  • Reset Position: Move the door icon to the center of the portal. Good if it got moved by accident.
  • Open / Close: One macro to toggle the exact line of VBL/MBL over the door, the image, and the dd2vtt.portal.closed property. Use the 'Handout' image to swap the icon with an 'open' or 'closed' icon. Alternatively, embed consistent asset IDs for closed/open images in MapTool so they can't be mixed up by accident/error. I'd like the macro to behave differently for Doors and Windows, where windows can either toggle vision or movement instead of both. (This could also be up to the GM to edit, and instructions could be in the macro as a comment)

In my testing, I was able to achieve something like this where all the auto-imported door VBL/MBL toggled perfectly with a token just using the JSON for data:

Describe alternatives you've considered

• Carefully adding doors manually.
• Removing VBL/MBL manually.
• Not adding doors to my maps.

Additional context
One issue with this is that windows and doors are indistinguishible in the format, so a generic icon might be better than a door if we want to be unopinionated - though I think making a call that follows DungeonDraft's conventions would be fine.

Sample Token
This token approximates what I'm hoping for on import:
dd2vtt Door.rptok.zip - Remove .zip extension. This sample uses the GM Notes to store the portal JSON. To use:

• Create a .dd2vtt map with a portal.
• Import it into maptool.
• Bring this token onto the map.
• With a text editor, copy and paste the Portal object for the door into the GM notes. No need to reformat it, MT will remove the whitespace.
• Click 'Reset Position' to place the door correctly.
• Click 'Open / Close' to toggle the door state.

Some images
These images are completely free and usable made from Game-icons.net by myself (Door is better than the window, which could be improved):

window-closed - window-open
door-white - door-white-open

[cwisniew]

We should probably add door support in general with no macros/lib:tokens required and this could then be tied in with that.

[melek]

I agree! However, since we don't have "walls" exactly it is definitely tough too decide how doors ought to work by default. For instance, our community doors library has both "vbl toggle" doors, and "object vbl" doors, and numerous icons for each.

I think this request may be worthwhile for the moment; if it isn't hard to add a token with macros, maybe it would be worth adding this functionality now, then converting it to a baked in door solution when that comes.

Of course, if the feature is complex and would create too much development overhead for a temporary feature, or if a built in door solution is in the pipeline, I can satisfy myself with a library to populate these tokens from a json file pasted in.

Edit: just clarifying I love the idea of built in doors :)

[melek]

Adding some discussion links here to document the conversation:

• MapTool Discord discussion
• DungeonDraft feature request to accommodate differentiating portal types in the export format. Go thumbs-up this if you like the idea!

[kwvanderlinde]

Now that we do have walls, things have changed. I plan to tackle #5182 in the 1.18 timeframe. And parallel to that will be refining & implementing #5288.

With both of those in, it would be trivial to include doors / windows in UVTT import.