APIs and macros that change multi-sided tokens don't work

APIs Not Cycling Multi-Sided Tokens I am having an issue cycling through a multi-sided token. The token was created from a rollable table containing eight images. The intended behavior is to advance through sides 1–8 and then return to side 1. I tested TokenMod using: !token-mod --set currentside|+ !token-mod --set currentside|- !token-mod --set currentside|2 TokenMod responds to other commands, but none of the currentside commands change the token image. The original table used Marketplace images, so I downloaded the images, uploaded them to My Library, created a new rollable table, and generated a new multi-sided token. This did not fix the issue. I also tested the Clock Tokens API, which is designed to advance multi-sided tokens, but it also failed to change the token image. Currently, multi-sided token cycling does not work for me in Jumpgate using either: TokenMod Clock Tokens Marketplace images Re-uploaded My Library images Newly created rollable tables and tokens Has anyone successfully used TokenMod or Clock Tokens to cycle a multi-sided token lately?

I noticed two days ago when I was setting up a multi-sided token to use as a background image, that the image change was taking a long time. The image would change but appear "out of focus" for 10 - 15 seconds before resolving. I was intending to run  !token-mod --set currentside|+   four or five time in a row to switch between the two images, making the map background rapidly change appearance during part of an encounter. The amount of time that the image change was taking made me scrap that plan. I'm instead going to use two separate images superimposed, and trust my fingers to Select -> Right-click -> Send to back several times in a row without messing up. (I've been practicing)

I am seeing no delays or issues while using the Faces script. Using the token mod command !token-mod --set currentside|<number> also had no issues. This was true of both token-sized images, as well as huge images that span the entirety of a very large map. This was on the regular VTT, not the legacy engine, as well as on the Experimental API server. After manually confirming that the actual token selected does have multiple sides, you could try running under those conditions, as well as try clearing cache and cookies.

I tried it again a just now with the same results I had two days ago - about a 25 second delay. I clear cache & cookies at the start of every game session, even when it's only me working in the game. The two original images are jpg, 960px x 570px, 300 dpi, 24bit, on a 25 x 14 grid. It may be connectivity issues in my local area - we've been having some "large" weather.

Ok I know what I did wrong. So apparently right clicking a marketplace item to add to your library doesn't place the item in the same category as "uploaded assets". Seems only uploaded assets can be used as multi-sided tokens that APIs can interact with. edit: The Clock Tokens API works but not the token-mod version.

Interesting. Does the Clock tokens API reference marketplace graphics? You are correct; marketplace graphics cannot be placed on the VTT by the API. There have been requests in the past to change this, allowing graphics to be placed so long as the are covered by the user's permissions, but it's apparently a complicated lift. The other reports (i.e. Rick's) still concern me though. Marketplace graphics are a binary choice. They either work or they don't. I am at a loss to explain a 25 second delay. Rick, can you test with a different browser, perhaps? Do you use a VPN?

Ihad the same results with Firefox, and I don't use a VPN. I still think it may be a local issue. The particular situation worked out last night doing "manualy" :) keithcurtis said: Interesting. Does the Clock tokens API reference marketplace graphics? You are correct; marketplace graphics cannot be placed on the VTT by the API. There have been requests in the past to change this, allowing graphics to be placed so long as the are covered by the user's permissions, but it's apparently a complicated lift. The other reports (i.e. Rick's) still concern me though. Marketplace graphics are a binary choice. They either work or they don't. I am at a loss to explain a 25 second delay. Rick, can you test with a different browser, perhaps? Do you use a VPN?

keithcurtis said: Interesting. Does the Clock tokens API reference marketplace graphics? It does not. Uploaded images work with Clock tokens though but tokenmod doesn't with uploaded images