Also known MATT; a module for doing things as simple as setting up simple triggers to pause the game if your players try to run around when you're not looking, or creating an interactive and immersive environment for your players.

Install the module via Foundry's Add-on Modules screen.

PF2's 5.15.2 update caused MATT's Remove Item action to soft brick the token and actors it triggered on; in MATT 11.27, there is a macro in the module compendium called Remove Corrupted Conditions that has instructions on using it to restore bricked actors.

MATT's Attack action currently does not work with MIDI's combat workflow modifications; any Attacks ran will not auto-roll damage, and possibly other issues. There is no ETA. Please log any issues that occur with using them both here.

• Hurt/Heal will be updated at some point and no longer work if there is a space between the operator and the value. Please delete the space in any actions you may have with it.

You're going to need a Gamemaster logged in to utilize some of MATT's functionality. There is no way around this due to the way Foundry handles permissions. In general, if its something a player cannot do on their own, it's going to require a GM as MATT just routes things players lack permission for through the GM.

^GM next to an action means it requires a Gamemaster level user to be logged in on Foundry. Some other actions may require a GM for secondary options; please double-check an action's notes if you have issues (these may not be 100% up to date in this area, and can depend on your player settings as well).

Just like links everywhere else in Foundry, tile actions will break when cloned/copied because the IDs are not the same as the original. Either Use Tagger for the actions that Tagger works with and fix the ones that don't, or use core Foundry's Adventure Document's ability to maintain IDs.

• Actions with text fields, such as Chat Message & Notification continue to store their text data when swapped into another action. While not a big deal, this could still add up in your data. I recommend just deleting these actions if you decide you need to replace them with a different one.
• You can duplicate actions in the list by right-clicking on them.
• When setting up complex tiles involving landings & redirects, it is recommended to add "feedback" actions; IE, a chat message to show where the thread went. This makes it much easier to diagnose problems. You'll see these in some of the Sample Tiles.
• There is no limit on the number of actions per tile; though the more you add, the more data it adds to your tile and scene. Our currently known record is 600 separate actions on one tile.
• You can drag & drop an action from one tile to another tile.
• You can insert actions above or below another action by right-clicking.
• Adds the Trigger Tile behavior to core regions.
  • $\color{green}{\textsf{New}}$ 12.02 Now passes data such as trigger method to the tile.
• $\color{green}{\textsf{New}}$ 12.02 Tile caching; instead of having to search through all tiles every time a trigger is requested, the tiles are already cached and the trigger knows exactly which tiles would apply.

1. Frequently Asked Questions
2. Sample Tiles Check here for working examples of various functions.
3. Tile Templates Monk's Active Tile Triggers adds a Tile Directory for storing your favorite tiles.
4. Tile Configuration Window covers the various configuration options.
5. Trigger Methods
6. MATT Targeting
7. Space is Important goes over when to use or not use a space.
8. Token Sizes and Tiles
9. MATT Module Settings
10. Hiding Tiles

1. Action Flow & Action Threads ^{WIP -Crow}
2. Filters & Current Action Collection ^{WIP -Crow}
3. Triggering a Tile via Door
4. Triggering a Tile via Journal
5. Triggering a Tile via Macro

1. Infinite Loops
2. Batching
3. MATT Macro Arguments
4. Handlebar Expressions
5. MATT Variables

This module deserves it's own section here; it allows for actions to target multiple entities at once without having to duplicate and manually target each one.

• Having it installed adds the Use Tagger targeting option to most actions.
• In a tile's action list, a directly targeted entity's ID will be replaced with the first Tag on that entity to make identification easier.
• Using Tags will allow action targets to still work after copying a scene or moving it between worlds. Any actions that don't accept Tags, unfortunately, will still need to be manually fixed unless you use Scene Packer.
• When used in conjunction with Token Attacher, it allows for prefabs to be made of multi-entity objects, such as a building complete with lights, sounds, and working trigger-able tiles. See Baileywiki's video here.

These modules don't directly add additional functions to MATT, but they can still be useful for various reasons.

• Find the Culprit This doesn't interact with MATT in any way, but its still probably the most useful module in Foundry for troubleshooting.
• Token Attacher allows you to attach anything on the canvas to a single token, save that token to an actor, and then you can drag & drop that token onto the scene with new copies of all the attached objects. Check out Baileywiki's video here.

The action list is extremely long and can be scrolled through.

Actions added by modules are grouped by module at the bottom of the action list.

• Activate/Deactivate ^GM
• Active Effect
• Add Item
• Add to Combat
• Alter ^GM
• Attack
• Change Permissions ^GM
• Change Scene
• Change Wall/Door
• Chat Message - this action has additional functionality with the Polyglot module.
• Close Dialog
• Create Journal Note
• Create Token
• Delay Actions
• Delete Entities
• Elevation
• Game Time
• Global Volume
• Hurt/Heal
• Move
• Open a Journal
• Open an Actor Sheet
• Open URL
• Pan Canvas
• Pause Game
• Ping
• Play Sound File
• Playlist
• Preload Scene
• Preload Tile Images
• Remove Item
• Reset Fog of War
• Reset Tile Trigger History
• Roll Table
• Rotation
• Run Code
• Run Macro
• Scene Background
• Scene Lighting
• Scrolling Text
• Send Notification
• Set Active Tiles Current Collection
• Set Active Tiles Variable
• Show Dialog
• Show Image
• Show/Hide ^GM
• Shuffle Collection
• Stop Sounds
• Stop Token Movement
• Switch Tile Image ^GM
• Target
• Temporary Tile Image
• Teleport
• Tile Animation ^GM
• Trigger Tile
• Write to Journal

• Check Entity Count
• Check Tile Trigger Count
• Check Value
• Check Variable
• Filter by Attributes
• Filter by Condition
• Filter by Items in Inventory
• Filter by Token Trigger Count
• Filter by Visibility ^{This action has been removed until an issue with Foundry can be worked around.}
• Filter Tokens by Distance
• Position in the List
• Random Number

• Check Data
• Jump to Landing
• Landing
• Loop Through Entities
• Redirect Based on Method
• Redirect Based on Player Type
• Run All Batch Actions
• Stop Additional Tiles Triggering
• Stop Remaining Actions

These all require their respective module to be installed and active in order to use these functions.

• Open Book

• Filter by Lock State
• Lock
• Loot Inventory
• Toggle Lock
• Unlock

• Open FQL Quest
• Open FQL Quest Log

• Execute Effect ^{This link isn't being added until the module is updated.}

• Alter Tag

• Open Party Inventory

• Convenient Effect
• Filter by Convenient Effect

• Shoot Confetti

• Shoot Confetti

• Clear All Effects
• Weather Effects

• Chat Timer

• Add Combat Placeholder

• Change Quest Status
• Select Monsters From Encounter
• Start Encounter

• Play Actor Sound

• Assign XP
• Change Movement Mode
• Redirect Request Results
• Request Contested Roll
• Request Roll

• Filter Objects Spotted By
• Filter Tokens Having Spotted
• Spot Object

• Filter Ridden
• Filter Riders
• Filter Riders of Mount
• Mount
• Mount to This Tile
• Toggle Mount
• Unmount
• Unmount Riders

Please feel free to contact me on Discord if you have any questions or concerns. ironmonk88#4075

If submitting a ticket, the proper place to log it will depend on what the issue is.

• Core actions, functions, and UI: please do so on MATT's GitHub here.
• Integrated modules issues: varies depending on the module.
  • If the issue is with an action provided by one of Monk's modules, that should be logged on that module's GitHub.
  • If the issue is with an action provided by one of Saibot's modules, that should be logged on that module's GitHub.
  • If the issue is with an action provided by any other module, that should be logged on MATT's GitHub here.

This Foundry VTT module, written by Ironmonk, is licensed under GNU GPLv3.0, supplemented by Commons Clause.

This work is licensed under Foundry Virtual Tabletop EULA - Limited License Agreement for module development v 0.1.6.