Hey! I'm pretty new to the community but I hope to share positive code bits with you guys to make your jobs easier as DMs (and maybe later on Players as well). Origin story of my mod (possibly more mods later on): I was looking for a mod to teleport tokens between maps to setup a new campaign for my future players and I was able to find a few but they were a bit too confusing for me to setup. Luckily I have some experience in coding, and JS is not a new language to me, so based on the amazing solution behind the MapTeleporters I have come up with my own solution and made my version of automated token traveling between points. Name & Link: TokenTraveler v1.4 Commands: !TokenTraveler --notification-off → disables GM whisper notifications !TokenTraveler --notification-on → enables GM whisper notifications Default: notifications ON The way it works (I have also included it in the documentation on my GitHub page in case I'd forget to update it here): You can place down any token on any layer (I recommend the DM layer if you want to keep it hidden but you can also place down a random token on the token layer as well, give it a portal/jump pad/etc. picture to make an interactive object). Give it the following name: Traveler:name:number Example1: Traveler:RavengaardCity:1 Traveler:RavengaardCity:2 Here, RavengaardCity:1 and :2 will be connected and the tokens (any kind of token that steps on it) will travel back and forth between the 2 nodes. Example2: Traveler:RavengaardCity:1 Traveler:RavengaardCity:2 Traveler:RavengaardCity:3 Here, RavengaardCity:1, :2 and :3 will be connected and the tokens (any kind of token that steps on it) will travel in sequence (1>2>3>1>2>3...etc.). When traveling between maps, it clones the triggering token with all of its features (that I know of), creates the clone on the new map and removes the original token. (This is because due to my knowledge, the pageid can't be changed on existing tokens since they are tied to the current map.) When traveling between 2 points on the same map , it moves the tokens with roll20's original token moving function/animation. Planned updates: Add options for changing teleportation sequence pattern (ascending, descending, random, odd-even(1>3>5, 2>4>6) [Done] Add multiple entry points to 1 endpoint version (like teleportation circle) [Done] Add multiple selectable endpoints with 1 entry point Add optional sound options to play a sound effect when teleporting If you have any suggestions on what I could add next, how to optimize it more or what other project/idea I should tackle next, feel free to leave a message. Take care, Roharx. Important info (I will take a look at these requirements so they will not be necessary in the future): Make sure the tokens you want to teleport (eg.: player tokens) have a name in their name field (Token Settings > General > Name). Make sure the tokens you want to teleport (eg.: player tokens) have a picture, otherwise roll20 will not create the new token on the next map and the original token will still be removed from the map Updates: v1.0 sequence pattern system update:
Now supports an optional pattern parameter in Traveler names:
Traveler:<GroupName>:<NodeId>:<Mode>
Example: Traveler:RavengaardCity:1:odd-even Modes: ascending - (default) 1→2→3→1→... descending - reverse 3→2→1→3→... random - teleport to a random node (not self) odd-even - 1→3→5→1, 2→4→6→2... Notes:
You can put these options into any of the Traveler nodes in any form and they will work accodringly.
Example:
Traveler:RavengaardCity:1:odd-even
Traveler:RavengaardCity:3:descending
Traveler:RavengaardCity:2:random
Example's sequence: 1>3>2>random(1 or 2) v1.1 cooldown bugfix :
Fixed bug that wanted to reference the global teleportation cooldown before initializing it. v1.2 teleportation circle mode:
Added new teleportation circle mode: Usage: Traveler:RavengaardCity:1:circle-entry Traveler:RavengaardCity:2:circle-entry Traveler:RavengaardCity:3:circle-exit In this example: 1 →3, 2 →3, 3 never teleports These entries will never be teleported to and exits will never teleport you away. Notes:
You can also link them together: Traveler:RavengaardCity:1:circle-entry Traveler:RavengaardCity:1:circle-exit Traveler:RavengaardCity:2:circle-entry Traveler:RavengaardCity:2:circle-exit In this example: 1:entry →1:exit, 2:entry →2:exit As long as exits for the specific number exist, they will always teleport to that exit. If there is no exit for the specific number (example: no 2:circle-exit),
it will always teleport to the lowest numbered exit (example: 1:circle-exit) v1.3 Better Messages:
Updated teleportation messages to look nicer and easier to read.
Exiting a portal on a different map now sends the map's new name as well.
Player cameras now follow the tokens both on the same map and across other maps v1.4 Camera Follow: Requirements: The Controlled By (Token Settings > Details) field needs to contain the player .
Notes: The GM map will not move to let them stay with the other players on the same map
