Version 11 Patreon Community Vote

Vote Overview

1. Advanced Measured Templates

Expand upon the existing Measured Templates system and add new features like template animation support, improved customization for template shapes, and the ability to link Templates to a Token.

Why you might want it

If you've ever wanted to visually see the arc of your lightning or the blast of a fireball, animations are for you. For the more defensively minded, linking a template lets you walk around with auras. Combat can be not only more exciting but sped up with accurate template-zones based on walls, allowing you to easily target (and blow up) the right people.

Things we'll do before we call it done

1. Add the ability to link a Template to a Token so that the Template moves when the Token does.
2. Improve integration with the targeting system so the placement of Templates will auto-target Tokens within its area of effect.
3. Add an API framework for rendering beautiful animations inside of Template shapes.
4. Add an option that will constrain the area of Measured Templates according to nearby walls.
5. Add support for video textures to be used for Template fills.

Stretch goals we would like to accomplish if possible

6. Include built-in animations for common spell types like Fireballs, Ice Blasts, Lighting Bolts, and more.
7. Add a framework to apply a visual filter or animation onto Tokens inside the Template area.
8. Other improvements related to Measured Templates and their interaction with other software components.

2. Compendium Improvements

Expand the functionality of Compendiums packs to add new organizational tools and quality-of-life improvements for both Gamemasters and content creators.

Why you might want it

We want to make it easier for users to create their own Compendium packs and organize their content in a way that is accessible across all the Worlds that they play. We can improve the organization of compendium packs by adding support for Folders. Further improvements to the Adventure document type and its associated Compendium packs can make it easier to import only a subset of specific content into your World.

Things we'll do before we call it done

1. Provide a user-friendly workflow to create a Compendium pack that is shared across multiple Worlds.
2. Add support for Folder organization of the Compendium Packs sidebar tab.
3. Add support for Folder organization of Documents inside a Compendium pack.
4. Make it easier for package developers to define a custom UI component for a browsing the contents of a Compendium pack.

Stretch goals we would like to accomplish if possible

5. Provide a workflow for packaging a created Adventure compendium pack as a distributable Module.
6. Add more granular import options to Adventures, allowing you to import or update only some Documents
7. Other improvements related to Compendium packs and their interaction with other software components.

3. Event Triggers

A new system which provides the possibility for defining scripted events that occur dynamically when Tokens interact with a certain area of a Scene.

Why you might want it

If you've ever wanted to have a pressure-plate trap trigger a boulder showing up at the end of the hallway, this is the feature for you.

There are a huge number of use cases for Event Triggers ranging from activating a trap, revealing a hidden passageway, initiating a combat encounter, turning lights on or off, or transitioning Tokens from one area to another. The Event Triggers system will allow you to make your Scenes more immersive and engaging by adding new ways for players to interact with the environment.

Things we'll do before we call it done

1. Define a new Embedded Document type inside a Scene which allows the definition of Event regions.
2. Each Event region will have its own triggering logic and scripted functionality when activated.
3. Some Event trigger types will be provided out-of-the-box, but Events can trigger Macros for almost limitless possibilities.
4. Support player-interactive control icons associated with Event regions. For example an area transition icon that - when clicked - transports a Token to a different region, or a lever control icon which - when clicked - transforms the Scene by activating certain Tiles.

Stretch goals we would like to accomplish if possible

5. Support "trap" type triggers to be revealed and visualized for players, allowing them to discover the location of dangerous traps.
6. Provide an advanced API framework which allows modules and systems to fine-tune the triggering conditions for an Event area.
7. Provide a way to link to Events in a Journal Entry, allowing activation of triggered Events by clicking a button in the Journal.

4. Improved Fog of War

Expand upon the existing Fog of War system to add improved tools for Gamemasters and a better user experience for players.

Why you might want it

Dynamic fog-of-war is gorgeous but can feel a bit out of place when playing old-school RPG's or using black-and-white maps. The addition of tools for manual management of Fog-of-War exploration would make it easy for a GM to reveal an entire room to all players or to hide a specific area that was previously discovered. Under-the-hood performance improvements to the way we store and save Fog exploration data will improve performance across the board.

Things we'll do before we call it done

1. Redesign the way that Fog of War exploration is computed and stored to improve performance with a geometry-based approach.
2. Add drawing tools which allow the Gamemaster to manually reveal or conceal parts of the Scene.
3. Further expand support for customizing the appearance of Fog of War with improvements to using custom textures and colors.

Stretch goals we would like to accomplish if possible

4. Add new advanced options for Fog of War exploration like blend mode, explored alpha, and other options.
5. Add support for Fog of War animation which can display the unexplored region visually like actual dense fog.
6. Add custom rendering for the edges of Fog of War which add some procedural noise to the explored region for a more organic aesthetic.

5. Placeable Items

Allow Items to be placed directly into a Scene, unlocking the ability for Players to find and acquire treasure or plot-advancing items by interacting directly with the game Canvas.

Why you might want it

The party enters a room dominated by a statue clutching a gleaming red gem, the legendary artifact they've been searching for. With placeable items, that gem can now exist on the map for your players to loot directly into their inventory. If your players are motivated by exploration, discovery, and the pursuit of treasure - the Placeable Items system will allow you to provide deeper engagement and immersion for the environments you create.

Things we'll do before we call it done

1. Implement a new embedded Document type which allows Items to be placed within a Scene.
2. Add a new Canvas layer that contains and displays Items which are present within a Scene.
3. Placed Items can be viewed and added to Actor inventories.
4. Placed Items can have a customized appearance similar to the features offered for Tokens.

Stretch goals we would like to accomplish if possible

5. Provide a mechanism for a defeated Token to be "looted", thereby acquiring the items that it previously possessed.
6. Support bundles of Items together which can support cases like a Treasure Chest that contains multiple things.

6. Standalone Player Client

A new installable version of the software which allows users to connect to remote Foundry instances in a client optimized specifically for Foundry VTT. The Player Client would be provided free of charge.

Why you might want it

Connecting to Foundry via a browser can often have various browser-discrepancies that cause visual or performance issues. A dedicated client would give you an optimized way to connect to a Foundry instance, removing the need for common troubleshooting steps such as enabling Hardware acceleration. Controlling the connection also allows us to add additional guidance, such as pages that help you diagnose why you can't connect to your friend's server. As a full Application, the Player Client would have more permissions and would be able to be granted access to your microphone without need for complicated SSL setups, and would enable us to invest work into things like Discord integrations that we previously couldn't do in a browser.

Although we will have more control than in the browser, a Player Client would not solve networking issues such as connectivity, it will only give better information about why a connection failed.

Things we'll do before we call it done

1. Offer an installable version of the Foundry Virtual Tabletop application which can be downloaded for free and provide a way to connect to game sessions hosted by other users.
2. Allow players to bookmark game servers, keeping a list of games to easily and conveniently connect to.

Stretch goals we would like to accomplish if possible

3. Provide a "one-click-launch" link which can be given to players to launch the Foundry Virtual Tabletop client application (if installed) and connect to a game session.
4. Allow users to store character data locally, making it easier to reuse the same character between multiple game worlds.
5. Add support for Discord Rich Presence to enable audio-only voice calls inside the Foundry VTT application using the underlying Discord GameSDK. This option would enable voice communication for self-hosted users who are not otherwise running with SSL certificates.

7. Touch/Tablet Support

Add support for touch and gesture interactions in addition to clicks. Work to make Foundry Virtual Tabletop look and feel good to use on devices with lower resolutions than are currently supported.

Why you might want it

With more people using Foundry to play in-person, the desire to connect via a tablet or touch-enabled laptop has become more pressing. Supporting full touch would enable fingers and pens to interact with UI elements, and gesture support would enable familiar actions such as pinching to zoom. Improving how the Foundry UI scales down to smaller devices would help support this workflow as well, although it will be up to System developers to ensure their Character sheets are responsive as well. The addition of this feature would also improve the usability of Foundry VTT on touch-based devices like Gameboard.

Although this work will be a good stepping-stone towards mobile support, it will not bring a mobile-friendly UI and Foundry will still be difficult to use on phone-sized devices.

Things we'll do before we call it done

1. Refactor our codebase to support Pointer events for interactions rather than just Click events.
2. Directly support certain multi-touch gestures like using two fingers to pan or pinch to zoom.
3. Improve the responsive design of our user interface to effectively scale down to support tablet-sized devices.

Stretch goals we would like to accomplish if possible

4. Explore options to vend Foundry Virtual Tabletop as a progressive web app that would run like a native application on tablets or other devices.

8. UI/UX Focus

Many of you have expressed feedback that you would value greater refinement, polish, and stability of existing features more than you would value new features. Instead of a major feature addition, we would devote significant effort towards refinement of the UI and UX of our existing software to deliver as many small improvements to interface and user experience as possible. Please note that we will absolutely work to improve UI/UX in Version 11 even if this option is not chosen, but if this option is chosen that work will receive significantly greater investment.

Why you might want it

If you enjoy and are excited by our recent website redesign, you may be equally excited for us to begin work on refining the UI of the core Foundry VTT application. In addition to improvements to the interface, there are a huge number of enhancements that can refine and enhance the user experience of working with the software for both Gamemasters and Players. Investments here range from improving clarity regarding how functionalities work, reducing the number of clicks to perform certain workflows, and changing our interface to be more intuitive for new and existing users.

Things we'll do before we call it done

1. An overall streamlining of workflows for interacting with all Document Types and the Canvas, reducing number of clicks required and increasing transparency about what each action does
2. Improve working with forms, particularly for specific input types like range sliders, color input fields, or file pickers.
3. Improve standardization of UI elements and UX workflows so a given action works the same place in every context.
4. Identify opportunities to add or improve keybindings to support keyboard interactions for common workflows.
5. Provide additional Tours and Tooltips to improve New User Experience.
6. Begin work on a next-generation user interface for the software - starting with the Setup and Configuration screen.

Stretch goals we would like to accomplish if possible

Instead of a specific list of stretch goals, we will instead emphasize that there are currently 376 open issues on GitHub tagged with either the UI or UX labels. There is a deep well of ideas which we have for how to improve the experience of using the Foundry Virtual Tabletop software. We would seek to implement a considerable number of these suggestions.