Library Token: Difference between revisions
(New page: Introduced in MapTool version b46, the Library Token is a special token type that acts as a library of properties and trusted macros that may be accessed and called by other macros. ==Li...) |
|||
| Line 22: | Line 22: | ||
==Library Token Macros== | ==Library Token Macros== | ||
Library token macros are created and edited like macros on any token. Macros on a library token may be called using the MACRO roll option. Since Library token macros are trusted, they may perform operations not available to regular tokens. | Library token macros are created and edited like macros on any token. Macros on a library token may be called using the [[Macros:Branching_and_Looping#MACRO_Option| [MACRO(): ]]] roll option. Since Library token macros are trusted, they may perform operations not available to regular tokens. | ||
Revision as of 04:16, 29 December 2008
Introduced in MapTool version b46, the Library Token is a special token type that acts as a library of properties and trusted macros that may be accessed and called by other macros.
Library Token Naming
All library tokens must have a name in the format "Lib:name", to indicate that they are to serve as a Library Token and not a "normal" token. Example library token names might be:
- Lib:test
- Lib:combat
- Lib:gamemaster
Library Token Requirements
For library tokens to be usable by player and NPC tokens, as well as global or campaign macros, they must meet the following requirements:
- The library token must be visible to players (make sure Visible to Players is set in the right-click context menu)
- The library token must have a name in the format "Lib:name"
- The library token must not be owned by any players (in the Ownership tab of the Edit Token dialog, make sure that no boxes are checked)
- The library token must be present on only one map in the campaign file.
Multiple library tokens may exist in the same campaign provided no two library tokens have the same token name.
Library Token Macros
Library token macros are created and edited like macros on any token. Macros on a library token may be called using the [MACRO(): ] roll option. Since Library token macros are trusted, they may perform operations not available to regular tokens.