Bump API and Transparent Token Movement Problem [Jumpgate]

Hi all. Has anyone had any issues using the mouse to drag/move a transparent token on the virtual table top? I tried using the Bump API in Jumpgate. It works as expected on the token I "bumped". The problem arises when I attempt to select and move the transparent token representing the "bumped" token. I'm able to select the token. The borders light up, and I'm also able to drag rotate the transparent token with the mouse using the rotation handle. I can resize the token using the mouse.  But I can't use the mouse to drag the token to a new spot on the map. I'm able to use the arrow keys to move the token, but mouse dragging isn't working. I verified the token is on the token layer and not locked. I don't think this is a bump API issue, so I added my own transparent token to the token layer, and it had the same exact issue. I'm able to select it, rotate it, assign a character sheet, adjust token settings, etc... but there is no movement on the token grid using the mouse. I can only use keyboard arrows. Is this a known Jumpgate issue? If yes, can someone share the forum thread link for the topic?

Hi Pak! I just tried bumping a token and then moving the slave token (the transparent one on the token layer). I am able to move it without issue. This is on the current VTT (used to be called Jumpgate). The fact that you can resize and rotate it eliminates a lot of locking behaviors from the VTT or from a script. So let's explore some other possibilities. What browser are you using? Can you move the token from a different machine if you have such available to you? Are you by any chance on a mobile device?

Hi Keith! Yes, I'm using current VTT (formally known as Jumpgate). Looks like the issue occurs on Chrome browser. I just verified the issue goes away using Firefox. I'm able to mouse drag transparent tokens within Firefox ***Separate but maybe related issue???*** I'm having an issue with TokenMod where I can't set 2024 Beacon token bar links using token mod commands. It worked on 2014 tokens but not 2024. I just verified that the tokenmod command works in Firefox but not in Chrome. !token-mod  --set  bar1_link|hp  bar2_link|ac

I would check for extension interference, maybe. I only run firefox once in a blue moon, and am not seeing the issues on my own install of Chrome. Try running your game in an Incognito window.

I ran Chrome in incognito mode and I can now mouse drag the tokens. So I got out of incognito mode and turned off ALL extensions in chrome, and it still doesn't allow for mouse grab and drag. Do I need to remove extensions or is turning them off just as effective.

Very strange. I see two paths: 1) Roll20 in incognito (some folks do this on purpose anyway for a cleaner experience) 2) Grab ca Console Log ( Chrome , Firefox ) and file a  Help Center Request . And see if a dev can't figure it out.

Hi Keith. I cleared chrome browsing data (cached images and files and Cookies and other site data). That seems to have done the trick! Thanks for helping me narrow the issue down to the browser! While debugging all this stuff, I ran into another bug. I'm seeing this new bug on chrome, firefox, chrome incognito, new roll20 games with no API's installed. While in Jumpgate, using 2024 sheets, I try to adjust the HP on a PC token that is already linked to the character sheet. I do this by clicking on the token, then choosing the appropriate bar bubble (bar 1 in my case) and then attempt to either increment the HP up or down or just change it to a new number and nothing happens. I'm not seeing this issue on 2024 NPC tokens. Can you confirm if you're seeing the same bug on your end?  I can always open up another forum question if needed. But figured I could just verify with you firstly. Which forum should I post this question too or should I submit this one to help center as well? Picture below showing what I'm doing

Can you post the token setup screen?

Is that the Fred Strong from the pre-builts? If so, I would strongly advise against testing anything against those. They were created in the earliest days of the sheet's development. IMHO, they should be removed entirely. Id suggest just building a quick PC, and not worry about the choices, just bull your way through to something that is a valid build.

Yes, that is Fred the pre-built. I didn't realize he was a problem child  Below is a grounds up 6th level paladin: And, tokenmod isn't working on the bar links again. I tried, Firefox, Chrome, Chrome incognito. It worked in Firefox this morning. UPDATE on tokenmod... Somehow, the sandbox switched back to default instead of experimental... WHY?!?!? After switching back, tokenmod bar linking works.

It still does that from time to time. If you want, here is a "Sandbox Watchdog" script that will prompt you if your game's sandbox ever reverts to default mode: /* */ var API_Meta = API_Meta || {}; API_Meta.SandboxWatchdog = { offset: Number.MAX_SAFE_INTEGER, lineCount: -1 }; { try { throw new Error(''); } catch (e) { API_Meta.SandboxWatchdog.offset = (parseInt(e.stack.split(/\n/)[1].replace(/^.*:(\d+):.*$/, '$1'), 10) - (4)); } } const SandboxWatchdog = (() =&gt; { &nbsp; &nbsp; &nbsp; &nbsp; const alertDefault = () =&gt; { &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; let contents = `The sandbox has reverted to default mode.`; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; let msg = `&lt;div style="width: 100%;border: none;border-radius: 0px;min-height: 60px;display: block;text-align: left;` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `white-space: pre-wrap;overflow: hidden"&gt;&lt;div style="font-size: 14px;font-family: &amp;quot;Segoe UI&amp;quot;, Roboto, Ubuntu, sans-serif"&gt;` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `&lt;div style="background-color: #000000;border-radius: 6px 6px 0px 0px;position: relative;border-width: 2px 2px 0px 2px;` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `border-style: solid;border-color: black;"&gt;&lt;div style="border-radius: 18px;width: 35px;height: 35px;position: absolute;` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `left: 3px;top: 2px;"&gt;&lt;img style="background-color: transparent ; float: left ; border: none ; max-height: 40px;"` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `src="<a href="https://i.imgur.com/kiUf3UC.png&quot;&gt;&lt;/div&gt;&lt;div" rel="nofollow">https://i.imgur.com/kiUf3UC.png"&gt;&lt;/div&gt;&lt;div</a> style="background-color: #c94d4d;font-weight: bold;font-size: 18px;` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `line-height: 36px;border-radius: 6px 6px 0px 0px;padding: 4px 4px 0px 43px;color: #ffffff;min-height: 38px;"&gt;` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `ALERT: Default Sandbox&lt;/div&gt;&lt;/div&gt;&lt;div style="background-color: white;padding: 4px 8px;border: 2px solid #000000;` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `border-bottom-style: none;color: #404040;"&gt;${contents}&lt;/div&gt;&lt;div style="background-color: white;text-align: right;` + &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; `padding: 4px 8px;border: 2px solid #000000;border-top-style: none;border-radius: 0px 0px 6px 6px"&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;`; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; sendChat('SandboxWatchdog', `/w gm ${msg}`); &nbsp; &nbsp; &nbsp; &nbsp; } &nbsp; &nbsp; on('ready', function() { &nbsp; &nbsp; &nbsp; &nbsp; if (Campaign().sandboxVersion.toLowerCase() === 'default') { alertDefault(); } &nbsp; &nbsp; }); })(); { try { throw new Error(''); } catch (e) { API_Meta.SandboxWatchdog.lineCount = (parseInt(e.stack.split(/\n/)[1].replace(/^.*:(\d+):.*$/, '$1'), 10) - API_Meta.SandboxWatchdog.offset); } } /* */ Upon rebooting your sandbox, you'll get a message like this if it is in "default" mode:

That's one handy watchdog for sure timmaugh! Thanks for sharing!