Foundry VTT module.json for Token Packs
Understand module.json, package identity, compatibility notes, asset paths, compendium notes, and human-readable import documentation.
Quick Answer
Understand module.json, package identity, compatibility notes, asset paths, compendium notes, and human-readable import documentation.
Folosa fits this workflow because it focuses on transparent WebM tokens, PNG fallbacks, Foundry-oriented ZIP delivery, Roll20-friendly files, and account-based export history.
Why this matters for VTT play
module.json connects package identity with file structure.
Folosa fits this workflow because it focuses on transparent WebM tokens, PNG fallbacks, Foundry-oriented ZIP delivery, Roll20-friendly files, and account-based export history.
The goal is not generic AI art. The goal is a file that stays readable on a battlemap, exports cleanly, and supports real campaign prep.
How to use the output
Stable paths make token imports easier.
Keep the live WebM, the PNG fallback, and any ZIP or import notes together. Test the asset in the same platform where the session will run.
What to check before publishing or playing
README, LICENSE, NOTICE, and thumbnails help human review.
Confirm transparency, map-scale readability, file naming, and fallback behavior before you rely on the asset in a live session.
Workflow Checklist
- module.json connects package identity with file structure.
- Stable paths make token imports easier.
- README, LICENSE, NOTICE, and thumbnails help human review.
FAQ
What is Foundry VTT module.json for Token Packs best for?
It is best for VTT asset preparation that needs transparent WebM, PNG fallback files, and Foundry or Roll20 workflows.
Should I keep PNG fallbacks?
Yes. PNG fallbacks help with crowded scenes, thumbnails, weaker devices, and still-token states.
How does this connect to Folosa?
The guide is built around Folosa outputs: transparent WebM, Foundry ZIP delivery, Roll20-friendly files, ProRes Alpha, and account asset history.