Party Split API.....

Think about leveraging the split the party feature.... The demo puzzle (can't find the video) was slick... Anyone played around with this much?

What I am thinking is having player tokens on the "off map" be shown on the GM layer of the main map.

It might be doable. I'm curious if you're able to get the characters position on a relative page, and have it auto update on change:token... Any idea how that information is coded? And if players on another screen trigger API events through changing graphics?

_id A unique ID for this object. Globally unique across all objects in this campaign. Read-only. represents ID of the character this token represents. Read-only. _pageid ID of the page the object is in. Read-only. left Number of pixels from the left edge of the map to the center of the graphic. top Number of pixels from the top edge of the map to the center of the graphic. There seems to be all the information needed.... its just keeping the "shadow" token in parity.

Hmmm, that brings the last question is if the pageid of the gm has a funtion *edit* I'm on a phone so my answeres are kind of short. You could try locating tokens based on control by, but if you can't cross reference them to the same page as the GM, it'd shift them campaign wide.

Good point.... Add a GM token... only keep it on one page?

Eh, or even place a map onto the GM layer beneath the moved token. It'll keep both semi transparent over the active map that you're watching. I'm assuming this is a round about way of forcing the "multiple layer" property that's yet to be implemented?

I see it more as being able to see where characters on another map are moving around, and where they are in relation to the people on the other layers. of course, this script would benefit greatly from being 'activated' through the use of a status icon that lets the API know to create a mirror image on the GM layer of all other active maps in the game. I would use the bleeding eye myself, but its personal preference (and I know I dont use the bleeding eye for anything else :P)

Eh, my biggest concern is isolating the page the GM is on to only update that page. Also create an array of characters on the same pages, so that if a graphic ID is the same on both, regardless of layer it updates. That way a campaign on 2 different floors allow players to interact, while shielding them from viewing each other.

playerpageid in the campaign object... the page the player bookmark is set to.. that is where the GM is assumed to be. Edit... and playerspecificpages An object (NOT JSON STRING) of the format: {"player1_id": "page_id", "player2_id": "page_id" ... } Any player set to a page in this object will override the playerpageid. And yes... something like the bleeding eye works. I think everything is here to do this fairly easily.... except the default token and associated settings :(

I don't think you need to isolate the page the GM is on, as he can be on any page as well. what I think we need is an across the board copy of tokens and their relative postions. so every character on whatever layer they are on are duplicated on every other page so that no matter what page the GM is on he can easily see locations. I often DM from a separate page entirely, and only switch back once something important needs my attention(traps, combat, etc) as I use tokens with names and target macros for my whispers, emas, and as so that I can easily have a multi-npc conversation with the players, or with themselves in fact. easiest place to hide them is on a separate page called... well, npcs, in my case. My point, which I almost lost there, is that DM's are not always on the playerpageid, but still need to keep an eye on it from time to time.

Right... but its easy enough to assume the playerpageid is the "main" page and everything else is a "one off" from the page. Whether or not the GM cares about that is up to the GM. The issue of "their relative positions" is just a variation of what HoneyBadger did here (it will even size the the token.) Coping the token shouldn't be a problem, you have the path from the main token to the image source, all all the settings. This should be straight forward.....