Difference between revisions of "Linking Tokens to Journals"
From Roll20 Wiki
(→How to set up tokens properly!) |
m (formatting) |
||
Line 5: | Line 5: | ||
This is how to do it: | This is how to do it: | ||
− | First, decide if your token represents a CHARACTER or a MOOK. | + | First, decide if your token represents a CHARACTER or a MOOK. |
A CHARACTER is a unique being. This token represents one, and only one, Journal Entry, and this Journal Entry represents one, and only one, token. Player characters are Characters. So are most NPCs (those with names). Some 'monsters' can be Characters as well; if there's only one instance of this being, ever, it's a Character. | A CHARACTER is a unique being. This token represents one, and only one, Journal Entry, and this Journal Entry represents one, and only one, token. Player characters are Characters. So are most NPCs (those with names). Some 'monsters' can be Characters as well; if there's only one instance of this being, ever, it's a Character. | ||
Line 26: | Line 26: | ||
# Save your work | # Save your work | ||
| | ||
− | Test by dragging multiple copies from the Journal onto the map. Change Hit Points on one copy; if the others change, it's done right! | + | Test by dragging multiple copies from the Journal onto the map. Change Hit Points on one copy; if the others change, it's done right! (Unless it's a Mook... if the others do not change, it's done right!) |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
+ | PC tokens will always carry over changes to new maps. Mook tokens will never carry over changes; each new token is unique. | ||
[[Category:Tips]] | [[Category:Tips]] |
Revision as of 03:33, 17 June 2014
How to set up tokens properly!
It seems a lot of people are having trouble getting their tokens set up properly, to work with Journal entries.
This is how to do it:
First, decide if your token represents a CHARACTER or a MOOK.
A CHARACTER is a unique being. This token represents one, and only one, Journal Entry, and this Journal Entry represents one, and only one, token. Player characters are Characters. So are most NPCs (those with names). Some 'monsters' can be Characters as well; if there's only one instance of this being, ever, it's a Character.
A MOOK is not a unique being; this token represents one of many similar or identical creatures. A horde of goblins is made up of mooks, for example. A leader goblin may or may not be a character, depending on the situation. The Goblin King is a Character, not a mook, as there is only one Goblin King. Some NPCs may be mooks: generic townspeople, for example, are mooks until and unless they are given a specific personality, name, or other reason to identify them differently than others; in this rare case, create them anew as Character tokens.
If your token is neither a Character nor a Mook, do none of these; it's just an item!
Now the tricky part; this needs to be done exactly in this order to work properly:
- Set up Journal entry with HP and other vital stats (Such as Hit Points, Armor Class, Movement, etc.)
- Create token to represent creature (Find one that looks like what you want, and place it on the board.)
- In the token's tools, link token to journal entry (Represents Character dropdown menu)
- Link token's bars to journal's Attributes (Bar 1,2,3 dropdown menu) (By general consensus, Bar 1 usually represents Hit Points. 2 and 3 often indicate Armor Class and Movement.)
- If "Mook", UNLINK token's Bar 1,2,3 dropdown from stats (numbers will stay but will no longer be linked)
- Make 100% sure token is set up the way you want it (Character bars are linked; Mook bars are NOT linked)
- Open Journal entry for that Token
- Select Token on map (token must be highlighted)
- In Journal Entry, click Use Selected Token
- Save your work
Test by dragging multiple copies from the Journal onto the map. Change Hit Points on one copy; if the others change, it's done right! (Unless it's a Mook... if the others do not change, it's done right!)
PC tokens will always carry over changes to new maps. Mook tokens will never carry over changes; each new token is unique.