[Help]!teleport API still fails to function across maps with newest version.

A single player can walk onto a cross map teleporter and it works perfectly.  The second another player repeats the process, regardless of waiting a long time or doing it rapidly in succession, the first players token on the new page immediately goes into the GM layer and they load back to the player ribbon page.  Maybe I am misunderstanding the purpose of this script.  Is this what is suppose to happen?  Can more than one player be on a different map than the ribbon?  

That's a new behavior I haven't heard of before - it shouldn't do that, no. The behavior should be each player going to wherever they are supposed to go and staying there. The current (1.2) script has a side effect of if a player on a two-way teleport token rotates or has any other graphic change event, it will trigger a teleport. This is corrected in 1.2.1 (and 1.2.2) . I'm not familiar with one teleport triggering another for another token, no. This works the same way every time? 

This happened repeatedly to every player last night in our session and I personally watched them move 7 spaces out into the map, then when I told the next player to come over their token immediately went to Gm layer and the new players token showed up on the map at the teleporter, he walked off, when I told the next player to come over, same thing.  And when the players get reverted, they no longer had a token on previous page so all they see is a mapload to black till I put the token back in token layer in the player ribbon page.  I'm migrating to dev to play on in my next session so I will have a fully reset setup but I do not think its something on my end as I removed the script and used the one click install and the players have token art that is stored in my quota and I was watching both sides of the teleport as they occurred.  

Could it have anything to do with their names having (Playing) in their token names?  Do the parenthesis effect the syntax somewhere or having so many similar characters in their names cause the api to effect them all?  The players themselves also have | in their names.  All of the tokens are set to be controlled by each individual player.  

DM Eddie said: Could it have anything to do with their names having (Playing) in their token names?  Do the parenthesis effect the syntax somewhere or having so many similar characters in their names cause the api to effect them all?  The players themselves also have | in their names.  All of the tokens are set to be controlled by each individual player.   I've confirmed it fails just as you said, I'll be looking deeper into the algorithm and trying to figure out what went wrong. It shouldn't be trying to teleport when there is no lastmove - and it shouldn't be pushing you back to the page if it was a one-way teleport (that's what my player saw).  My apologies - the cross-page API and methods for trying to maintain it don't appear to work as expected - this algorithm behaving this way is most unexpected. I will try and have a fix out for this before Monday. Failing that, I'll put a warning in that it's being worked on but unfortunately only supports party splits of one at this time, so most games rogues will be happy at least. Edited to add : It should not have anything to do with player names, as I deal almost exclusively in token id's and token associations (determining if something is supposed to represent the same token by checking its represents id against each other which should be the same id for the same character sheet object for example)- so player token names only come into play during text messages with [target] attributes... that's it. 

May have figured it out - updated gist 1.2.3 - can you give this one a try? (If you're not sure how to use a non-one-click, I can walk you through it) <a href="https://gist.github.com/Gritmonger/20d1c165a886eba6d46458316260c715" rel="nofollow">https://gist.github.com/Gritmonger/20d1c165a886eba6d46458316260c715</a> Please give it a shot - I apologize again for the error.&nbsp; I've confirmed this version works as expected with multiple players teleporting to different pages or the same page - I apologize again for the broken version. Version 1.2.1 will be up in one-click on Tuesday.&nbsp;

Yep, my next session with multiple players will be this wednesday.&nbsp; I'm familiar with manual installs.&nbsp;&nbsp;

DM Eddie said: Yep, my next session with multiple players will be this wednesday.&nbsp; I'm familiar with manual installs.&nbsp;&nbsp; It will be the latest version in one-click (this gist) by Tuesday which should auto-update.&nbsp; Again, my apologies for the issues.&nbsp;