HELP! @{target|token_id} not working in Jumpgate

I've been moving some of my campaigns to Jumpgate, but during game-play my players have been experiencing issues running macros and API calls that use the @{target|token_id} command.  This does not happen immediately, and during the first 15 to 30 minutes of game-play all seems OK, but after some time using @{target|token_id} stops returning the ID of a targeted token: it still returns an ID but it is not for any valid "graphic" object. Not only that, but the same ID is returned whatever token is targeted.   Here's a video demonstrating the problem, which is still happening:  Roll20 Jumpgate @{target|token_id} does not work It is not only @{target|token_id} that does not work - @{target|token_name} or any other @{target|...} variant also fail. I have raised this with the Roll20 help desk several times over the last 6 months, but nothing has been fixed by them.  I believe they did see something similar with the D&D 5e character sheet when Jumpgate was first released, and fixed that.  But it is still happening for the Advanced D&D 2nd edition character sheet. At the moment the Legacy tabletop works fine, but that is not being developed any more... Is anyone else getting this issue?  Is it just those of us using Peter B.'s exellent "Advaned 2nd Edition" character sheet?  Or can anyone tell me what I am doing that is causing this that I can correct and get everything working fine? I am the author of the RPGMaster suite of APIs for playing AD&D2e, which use the @{target|token_id} command alot for targeting spells, powers, magial effects, looting, picking pockets, etc, etc.  None of this works when @{target|token_id} stops working.  It all still works on the Legacy desktop, but more and more development is going into Jumpgate, Legacy is being left behind, and I fear Legacy being turned off before this is fixed! I am thinking of seeing if I can create a new #{target|...} syntax in my API code to replace @{target|...}, but given I have over 3,000 database definitions and over 50,000 lines of code to check for errors caused by making such a change, that is a daunting task. HELP!

I thought the issue was whether the token was from a pre-conversion source (i.e. existed in a classic game before being converted to Jumpgate) vs. a token that was created within the Jumpgate environment.

It's also happening to me, using a different sheet. I opened a ticket a bit more than a month ago, but didn't receive any answer, except the automated response. I  mentioned the issue  in the Jumpgate thread, and the answer was that it was investigated with high priority. I  proposed to share a link  with a game where I could definitely reproduce the issue, but didn't get any answer. The issue also appears when I'm the only player connected to the game. It happens in games created as Jumpgate. When the issue occurs for a page, it concerns all tokens, but sometimes not when they are on top (one needs to push them to the back to see the bug). It happens also when I de-activate all API scripts. It also happens in private browsers and without any extension.

Something I noticed on all pages with the issue : on these page, when resolving @{target|token_id}, we get the cross pointer everywhere on the map, and not just over tokens. And when we click outside of a token, we do get a result.

Hi Nic. Answers in-line below Nic B. said: Hi Richard, Sorry it's taken so much effort to get a response on this. I don't have insight into your communications with the Helpdesk, but I reached out to the Jumpgate team and verified that they are aware of this issue and are actively investigating it. However, I think reproduction may be proving troubling here. Apologies if you've already communicated answers to these questions, but to help triage this issue, would you mind providing answers to the following questions: Does this issue only occur if there are multiple players concurrently in the game? Or do you also encounter the issue when you are the sole occupant of the game?&nbsp; No, I can reproduce it with just me in the game.&nbsp; Indeed, the video is taken with just me in as GM at that point, even though it is a multi-player campaign which is normally played by my group.&nbsp; I have also recreated the issue with a brand new campaign that only I have accessed.&nbsp; The problem does seem to occur more quickly the more actions that are being taken and thus more quickly with multiple players. Do you only encounter this issue in certain campaigns? Or in any campaigns you use? Every I campaign I have created in, or &nbsp;converted to Jumpgate with the "Advanced 2nd Edition" character sheet has eventually had this problem.&nbsp; I've not tried campaigns with any other character sheet. If this is only certain campaigns, are they campaigns that have been converted from Legacy to Jumpgate? Or, are they only experienced in games that have active API scripts? Or, perhaps, only games using that specific ADnD sheet?&nbsp; It happens in both converted and new campaigns (just reconfirmed this last week). I have recreated it in a newly created game in Jumpgate without any APIs loaded. I have only tried it with the "Advanced 2nd Edition" sheet by Peter B.&nbsp; Our group play AD&amp;D2e exclusively. Is there anything specific about these tokens that are unusual? Do they have dynamic lighting configured? Are their images straight from your library or a marketplace set?&nbsp; I am not aware of anything different about these tokens. All of them will have Dynamic Lighting vision, and some of them will have dark vision The images are a mixture of ones from my library and marketplace. I noticed in the video that there is sometimes behavior when you mouse over tokens displaying one of the token bars (Bar 3). Is this a glitch, or have you configured this behavior in some way?&nbsp; This is how my APIs configure the tokens by default.&nbsp; Our group use Bar 1 as AC, Bar 2 as Thac0, and Bar 3 as HP (the red one!).&nbsp; Bar 3 always shows to give an idea of health. Bars 1 &amp; 2 only show if the RPGMaster APIs detect a difference between the AC or Thac0 they calculate should be current and what the Token Bar value field is set to (the APIs know the effect of magic items, armour &amp; spells etc on these values and make the calculation).&nbsp; This helps the GM and Players and keeps the playing surface clear of unnecessary clutter.&nbsp; So this is working as it should. Are you using any extensions in your browser that might interact with the VTT? Sometimes even Password Managers and Spell Check extensions can interact in a quite deleterious way.&nbsp; I keep the Chrome space pretty clean.&nbsp; I have " Google Docs Offline", "Adobe Acrobat PDF edit, convert, sign tools", "Beyond 20", and &nbsp;" Microsoft Editor, Spelling &amp; Grammar Checker" &nbsp;running, and that's it.&nbsp; None of these cause a problem in Legacy, but perhaps they do in Jumpgate?&nbsp; Next time I investigate this issue, I'll try it with them turned off, but not sure it will have an impact... Is the following an accurate list of the scripts you're using: libTokenMarkers, TokenMod, ChatSetAttr, CommandMaster, MagicMaster, AttackMaster, InitMaster, RoundMaster, RPGMaster Suite&nbsp; Yes, that is the complete set for the campaign in the video, but as I state above, I have recreated the problem without any APIs loaded. Again, apologies if you've already answered these questions; but I'll pass them on to the Jumpgate team and hopefully it will help them identify a root cause. When recreating this problem, you have to be patient.&nbsp; I can take more than 30 to 45 minutes of active game play to appear.&nbsp; It makes me think there is a memory or stack leak somewhere (Not sure it can happen these days... I am an old school games programmer - I used to write 6502 assembler for the Commodore 64 and Z80 assembler for the Sinclair Spectrum back in my day! You may have come across "Valhalla" which won the BMA Game of the Year award in 1984 - I was part of the 4 man team who devised and programmed that!). Here's a link to the latest campaign it has occurred in for me - brand new, never played by my group, just me trying to set up the next module in my long-running saga:&nbsp; <a href="https://app.roll20.net/join/19615263/6vHP2g" rel="nofollow">https://app.roll20.net/join/19615263/6vHP2g</a> I've now changed the Player page to be the correct map page - and given access to the tokens mentioned to All Players. Try this: I have just recreated this issue in 1 step this morning (not guaranteed to do it again as the problem does seem to sometimes appear soon, and other times takes 30 minutes or more).&nbsp; Open the campaign linked to above as GM (or even better as me, if you can...). Wait for the APIs to load and tell you they are ready in the chat window Go to the "Hermitage 2nd Floor" map if not already shown Find the two tokens just south of tower room 16 and corridor 17 &nbsp; [steps deleted - they are not needed] Select the little dwarf token, then type @{selected|token_id} = @{target|token_id} &nbsp;in the chat box. When asked select the dwarf as the target. Two token_ids appear, and they are not the same, even though the target was the same token as that selected. Select the Snake token, then type @{selected|token_id} = @{target|token_id}&nbsp; &nbsp;in the chat box. Select the Snake when prompted for the target. Again, two different token_ids appear.&nbsp; Note that the target|token_id is the same for both the dwarf &amp; the snake! I hope this helps! Best regards, Richard @ Damery

keithcurtis said: I thought the issue was whether the token was from a pre-conversion source (i.e. existed in a classic game before being converted to Jumpgate) vs. a token that was created within the Jumpgate environment. No. The problem happens for both converted campaigns and for brand new ones created in Jumpgate.&nbsp; E.g. see my reply to Nic B. above

I added a little command to my MagicMaster APIs with the following code: case 'testid': &nbsp;&nbsp;&nbsp;&nbsp; let token = getObj('graphic',arg[0]); &nbsp;&nbsp;&nbsp;&nbsp; log('token_id is '+arg[0]+', and getObj() returns '+token+'. Type = '+(!!token ? token.get('_type') : 'undefined')); break; I called it with !magic --testid @{selected|token_id} with a token selected, and it returned this to the console: "token_id is -OQZ26erjG8Tb-i2tiSS, and getObj() returns [object Object]. Type = graphic" I then called it with&nbsp; !magic --testid @{target|token_id} and targeted the same token when asked, and it returned the following to the console: "token_id is -OQm9FaBfy4S-deapmUB, and getObj() returns undefined. Type = undefined"

Are @target and @select returning the correct information? That's the problem I saw back in October . If you run this simple template command, you should get the token ID duplicated in both the selected and targeted returns, and the character ID similarly duplicated: &amp;{template:default}{{name=Proof}}{{Selected TID=@{selected|token_id} }} {{Selected CID=@{selected|character_id} }} {{Targeted TID=@{target|token_id} }} {{Targeted CID=@{target|character_id}}} Also, if you install the Inspector script, you can crawl the selected token's properties like this: !inspect --selected ...and flow from there to the token, then the represented character... to see if the information matches. If you get a *wrong* ID anywhere, you can inspect *that* ID in a similar fashion to see what is ACTUALLY being returned to your message: !inspect ---OQm9FaBfy4S-deapmUB EDIT: What I mean to say is that your getObj() is specifically looking for a graphic. Chances are good that it is returning the WRONG ID, and it's actually a character ID you're handling at that point. The Inspector script will tell you that.

timmaugh said: Are @target and @select returning the correct information? That's the problem I saw back in October . If you run this simple template command, you should get the token ID duplicated in both the selected and targeted returns, and the character ID similarly duplicated: &amp;{template:default}{{name=Proof}}{{Token ID=@{selected|token_id} }} {{Character ID=@{selected|character_id} }} {{Targeting}} {{TID=@{target|token_id} }} {{CID=@{target|character_id}}} Also, if you install the Inspector script, you can crawl the selected token's properties like this: !inspect --selected ...and flow from there to the token, then the represented character... to see if the information matches. If you get a *wrong* ID anywhere, you can inspect *that* ID in a similar fashion to see what is ACTUALLY being returned to your message: !inspect ---OQm9FaBfy4S-deapmUB EDIT: What I mean to say is that your getObj() is specifically looking for a graphic. Chances are good that it is returning the WRONG ID, and it's actually a character ID you're handling at that point. The Inspector script will tell you that. Interesting! OK, I loaded "Inspector" as an API.&nbsp; Using the help that appeared, the command I actually used is "!about". I used @{selected|token_id} = @{target|token_id} to check I was getting the issue (it seems that I now have a game that has the issue right from the point of loading!). This returned: Richard (GM): -OQZ26erjG8Tb-i2tiSS = -OQnG7SDv0hDFNa5BBpZ Having confirmed that @{target was indeed returning an incorrect ID, I typed in !about -- OQnG7SDv0hDFNa5BBpZ Now that returned the message: (From Inspector): Inspection Failed Unable to find an object using the parameters supplied. Please try again. But, checking a valid token_id found by using @{selected|token_id}, this error was due to my error in what I typed.&nbsp; It should have been tripple dash before the object id. That returned lots and lots of info about the object that had the valid id returned by @{select&nbsp; &nbsp; So I tried typing this (with 3 dashes at the start, 2 for the command initiator, then the one starting the object id): !about --- OQnG7SDv0hDFNa5BBpZ But it came up with the same error message as above. So @{target really is returning rubbish.&nbsp; It is not an ID of anything "Inspector" can find.

Just in case it's useful, this is what !about returned when the valid id provided by @{select|token_id} was used: -OQZ26erjG8Tb-i2tiSS { _id: <span class="userscript-userscript-showtip userscript-tipsy-n-right" title=" TOKEN • Name : Giant Coral Snake • Page : Hermitage Second Floor • Layer : objects • Position : (595, 980) • Control : Unknown, Unknown " style="display: inline-block">-OQZ26erjG8Tb-i2tiSS s , _pageid: -Ldxi8qGOUayStKEthP- s , left: 595 , top: 980 , width: 70 , height: 70 , rotation: 0 , layer: objects , isdrawing: false , disableSnapping: false , disableTokenMenu: false , flipv: false , fliph: false , imgsrc: <a href="https://s3.amazonaws.com/files.d20.io/images/441469549/gMB4-XYI2UshPyzmeFzV_Q/med.png?1747582722" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/441469549/gMB4-XYI2UshPyzmeFzV_Q/med.png?1747582722</a> , name: Giant Coral Snake , undefined , controlledby: , bar1_value: 5 , bar1_max: , bar1_link: -OQZ48ZIeFN6f5au1QM9 s , bar1_num_permission: , bar2_value: 15 , bar2_max: , bar2_link: <span class="userscript-userscript-showtip userscript-tipsy-n-right" title=" ATTRIBUTE • Name : thac0-base • Character : Giant Coral Snake • Current : 15 • Max : " style="display: inline-block">-OQZ485m1U2Tb7Z2AhTg s , bar2_num_permission: , bar3_value: 47 , bar3_max: 47 , bar3_link: <span class="userscript-userscript-showtip userscript-tipsy-n-right" title=" ATTRIBUTE • Name : HP • Character : Giant Coral Snake • Current : 47 • Max : 47 " style="display: inline-block">-OQZ48AbhrlipRNuxmVo s , bar3_num_permission: , represents: <span class="userscript-userscript-showtip userscript-tipsy-n-right" title=" CHARACTER • Name : Giant Coral Snake • Journals : Unknown • Control : Unknown " style="display: inline-block">-OQZ1Z6DK36X9skjNtO3 s , aura1_radius: , aura1_color: <span class="userscript-userscript-showtip userscript-tipsy-n-right" title=" #FFFF99 " style="display: inline-block">#FFFF99 , aura1_square: false , aura2_radius: , aura2_color: <span class="userscript-userscript-showtip userscript-tipsy-n-right" title=" #59E594 " style="display: inline-block">#59E594 , aura2_square: false , tint_color: transparent , statusmarkers: <span class="userscript-userscript-showtip userscript-tipsy-n-right" title=" " style="display: inline-block"> , showname: false , showplayers_name: false , showplayers_bar1: false , showplayers_bar2: false , showplayers_bar3: false , showplayers_aura1: false , showplayers_aura2: false , playersedit_name: true , playersedit_bar1: true , playersedit_bar2: true , playersedit_bar3: true , playersedit_aura1: true , playersedit_aura2: true , light_radius: , light_dimradius: , light_otherplayers: false , light_hassight: false , light_angle: , light_losangle: , light_multiplier: 1 , adv_fow_view_distance: , sides: , currentSide: 0 , lastmove: 578,962 , _type: graphic , _subtype: token , _cardid: , has_bright_light_vision: false , has_night_vision: false , night_vision_tint: null , night_vision_distance: 0 , emits_bright_light: false , bright_light_distance: 0 , emits_low_light: false , low_light_distance: 0 , has_limit_field_of_vision: false , limit_field_of_vision_center: 0 , limit_field_of_vision_total: 0 , has_limit_field_of_night_vision: false , limit_field_of_night_vision_center: 0 , limit_field_of_night_vision_total: 0 , has_directional_bright_light: false , directional_bright_light_total: 0 , directional_bright_light_center: 0 , has_directional_dim_light: false , directional_dim_light_total: 0 , directional_dim_light_center: 0 , light_sensitivity_multiplier: 100 , tooltip: , show_tooltip: false , night_vision_effect: null , dim_light_opacity: 0 , bar_location: null , compact_bar: null , lightColor: transparent , lockMovement: false , fadeOnOverlap: true , fadeOpacity: 0.3 , renderAsScenery: false , baseOpacity: 1 }

Richard @ Damery said: Using the help that appeared, the command I actually used is "!about". Yeah, the "inspect" handle was a later suggestion from Keith, since the script was called "Inspector". =D Anyway, the fact that Inspector isn't finding the object, either, is interesting. Your command line does look like it is missing a hyphen, however. Are you sure you ran it with 3 hyphens? There should be this formation: !about -- ...following by the ID you are looking up, which itself starts with another hyphen: -OQnG7SDv0hDFNa5BBpZ So there should be 3 hyphens in there. If, after all of that, Inspector still doesn't find it, that's... odd... because when I run a temporal recomposition on the UUID, it comes out to have a birthdate of (roughly): Wed May 21 2025 10:34:36 GMT-0400 (Eastern Daylight Time) So that definitely isn't something that was a part of any conversion of this game, or a legacy object that was once a part of the game but no longer is, now. That's a TODAY date from less than an hour ago.

OK, I see you'd already spotted the 3-hyphen problem. (Incidentally, if you hadn't noticed, those little "magnifying glass" icons in the returned panel are all, themselves, links to other items in your game.) Does the rough timeframe of the creation of this ID correlate to anything you were doing in the game?

timmaugh said: OK, I see you'd already spotted the 3-hyphen problem. (Incidentally, if you hadn't noticed, those little "magnifying glass" icons in the returned panel are all, themselves, links to other items in your game.) Does the rough timeframe of the creation of this ID correlate to anything you were doing in the game? I can reproduce the problem at will in this game:&nbsp; <a href="https://app.roll20.net/join/19615263/6vHP2g" rel="nofollow">https://app.roll20.net/join/19615263/6vHP2g</a> All I need to do is go in as a player following the link, then: Join as a Player T he "Hermitage 2nd Floor" map should already be shown Find the two tokens just south of tower room 16 and corridor 17 (you can't see the numbers as a player - just find the only tokens you can select down the bottom left) Select the Giant Coral Snake token, the larger of the two (selectable by anyone) Type @{selected|token_id} = @{target|token_id} and when prompted target the same Giant Coral Snake token Check the two returned IDs are different (i.e. the problem has occurred) Do the same for the other token you can see - called Guerk Note that while the selected token_ids are different, the targeted token_ids are the same! This is currently working every time for me - totally and immediately repeatable.&nbsp; Other players have also repeated it using these instructions - see rest of the thread.

We can't change maps if we're not GMs, and we won't be able to select tokens if we're not GMs or you haven't set the token to be able to be controlledby "all". &nbsp;I jumped in, but I can't change maps, and I only see one token on the page I land in, and I can't select that token.

OK, so I decided to check if others could see the same problem in the game, so I went in on another of my player logins that I use for testing.&nbsp; I sent the game link to that player and I entered the game using it on a different machine (my laptop, as opposed to my gaming PC).&nbsp; I stayed on my gaming PC as myself as GM, and allocated control of the Giant Coral Snake to the test player. The test player could then select the Giant Coral Snake token and then type @{selected|token_id} = @{target|token_id} in the chat window.&nbsp; Targeting the Giant Coral Snake when prompted by the target command, it returned the same error - but with a different token_id from the one I was getting on my gaming PC! On the gaming PC as GM, @{selected|token_id} = @{target|token_id} returned:&nbsp; &nbsp; Richard (GM): -OQZ26erjG8Tb-i2tiSS = -OQnWHGSkuIW_8frmQmc On the laptop as my test player,&nbsp; @{selected|token_id} = @{target|token_id} returned:&nbsp;&nbsp; Simon B.: -OQZ26erjG8Tb-i2tiSS = -OQnWKnhipT67fihDgES Note: I was able to go straight in as this test player and get the error immediately in this game.

timmaugh said: We can't change maps if we're not GMs, and we won't be able to select tokens if we're not GMs or you haven't set the token to be able to be controlledby "all". &nbsp;I jumped in, but I can't change maps, and I only see one token on the page I land in, and I can't select that token. Let me give you access to those tokens... I'll do it now... OK, players are on the correct page, and I've set the Giant Coral Snake and Guerk to be available to ALL Players.&nbsp; I've checked, and the error is still happening for me and for the test player on my laptop Note: &nbsp;I have disabled all APIs in this game except &nbsp;Inspector, Messenger &amp; libTokenMarkers, so my RPGMaster APIs are not running, and the action buttons will not work for you, even though they appear when tokens are selected.

OK, here are results of my testing with the 2 tokens that I could reach. I selected each of them individually then ran the command: &amp;{template:default}{{name=Proof}}{{Selected TID=@{selected|token_id} }} {{Selected CID=@{selected|character_id} }} {{Targeted TID=@{target|token_id} }} {{Targeted CID=@{target|character_id}}} ...and I *targeted* the same token (e.g., the token I had selected was the same token I targeted for that run of the command). Here is the report: You can see that even though I got a "correct" set of Token ID &amp; Character ID for each token as the "selected" token, I did NOT get a Character ID for the token via targeting. What's more, I got the SAME Token ID from targeting the second token as I did for targeting the first, and they are both wrong! I tested this in a game of my own (using The Aaron's proposed nomenclature, a JDLC game: Jumpgate Default-Sandbox Legacy Converted), and it works just fine as a GM/owner:

timmaugh said: I tested this in a game of my own (using The Aaron's proposed nomenclature, a JDLC game: Jumpgate Default-Sandbox Legacy Converted), and it works just fine as a GM/owner: I've not come across this JDLC nomenclature.&nbsp; Can you send me a link to it's desription? Do you think this is the reason for a problem occurring? How long did you test this in your game? I have often needed active game play for more than 30 minutes to get it to occur - this game doing it every time immediately is incredibly rare! I use lots of marketplace D&amp;D5e campaigns, which I convert to AD&amp;D2e. How will that work with JDLC&nbsp; nomenclature?

It's more just a way of classifying the important elements of the game for troubleshooting/comparison purposes (what engine, what sandbox, what sheet, etc.), since some quirks/bugs are going to be specific to the answers to some of those configurations. Let me see if I can summon Aaron...

Ah, get the JDLC meaning.&nbsp; Mine is a Jumpgate Default-Sandbox Legacy-charater-sheet Original (? does that make sense?) game, never been Legacy (though I do now have a Legacy version of it so I can start to play it with my group onec I've finished setting it up). The Legacy-charater-sheet is Peter B.'s "Advaned 2nd Edition" sheet.

Yeah, it's just a shorthand we've been using informally (nothing Roll20-sanctioned about it). Aaron dubbed it "The MAGE System". Here's the write-up he did for it:&nbsp;<a href="https://docs.google.com/document/d/19ZWhNxbjxpRRcWu4TX-Yhn6jVX-LeEkb4CJY7GXmZJM/edit?usp=drivesdk" rel="nofollow">https://docs.google.com/document/d/19ZWhNxbjxpRRcWu4TX-Yhn6jVX-LeEkb4CJY7GXmZJM/edit?usp=drivesdk</a>

Hi Richard! Unless that game is built to be trashed, I would suggest removing the join link. Open join links allow anyone to come in and vandalize your campaign. Team members (not Forum Champs) can get in with just the game id, but the safest practice is to PM join links directly.

keithcurtis said: Hi Richard! Unless that game is built to be trashed, I would suggest removing the join link. Open join links allow anyone to come in and vandalize your campaign. Team members (not Forum Champs) can get in with just the game id, but the safest practice is to PM join links directly. Hi Keith, That game is isolated and does not work for me - because of the @{target problem.&nbsp; It is not part of anything my group are doing.&nbsp; The version we are playing is a Legacy version of it. (By the way, the Jumpgate version is not &nbsp;a conversion of the Legacy game - I created the Jumpgate version first to see if the bug had been fixed, found it had not, and then created the Legacy version from scratch). I want this solved as soon as possible, so I and my group can start playing in Jumpgate (my group can't yet) and use some of the great features being developed there.&nbsp; So I'm happy for others to do whatever helps in this game that I've shared so that this gets solved: the evidence that this helps is above. If anyone starts trashing it in such a way as that it ruins it for others to solve this problem, that would be a shame. Does that seem sensible?

timmaugh said: Yeah, it's just a shorthand we've been using informally (nothing Roll20-sanctioned about it). Aaron dubbed it "The MAGE System". Here's the write-up he did for it:&nbsp; <a href="https://docs.google.com/document/d/19ZWhNxbjxpRRcWu4TX-Yhn6jVX-LeEkb4CJY7GXmZJM/edit?usp=drivesdk" rel="nofollow">https://docs.google.com/document/d/19ZWhNxbjxpRRcWu4TX-Yhn6jVX-LeEkb4CJY7GXmZJM/edit?usp=drivesdk</a> So in The Aaron's MAGE codification, mine is a JDLO game, where the Legacy-Character-Sheet is Peter B.'s "Advanced 2nd Edition" sheet.

Just to verify, anyone (or at least everyone so far) can repeat this Jumpgate bug test using the instructions in this post .&nbsp; <a href="https://app.roll20.net/forum/permalink/12369318/" rel="nofollow">https://app.roll20.net/forum/permalink/12369318/</a> As GM, I have put the player map page to the correct page, and made the only two tokens players can see selectable by anyone, so that you should be able to reproduce the Jumpgate @{target bug every time. If you think you might be able to help identify the issue, do go in and take a look but don't alter anything.&nbsp; Just follow the instructions in the post to view the issue. This game is not part of any of my campaigns, so no one need worry about accessing it or mucking it up.&nbsp; However: &nbsp;please don't change anything in it (even if you can): e.g. don't move the tokens around or change them in any way, at least not until the Dev team have looked at it and been able to reproduce the issue themselves.&nbsp; I worry doing so may make the bug non-repeatable, as it is a very elusive one, and this is the first time in many months I've been able to make it easily repeatable.

Update: something has changed - a clue? I went into the game that demonstrates this bug today. The little dwarf token is still there and demonstrates the problem as described (the @{selected|token_id} is correct but the @{target|token_id} is wrong, as before). However, the Giant Coral Snake token graphic is not displayed: it is still there - the red bar and the token name are displayed, but the graphic is missing and the token is not selectable by clicking on it. You can select the Giant Coral Snake token by dragging a selection box over it - the token circles then appear. Using the gear icon opens the token, and it is possible to go to the character sheet via the token settings - the graphics are there on the Character Sheet Edit dialog. With the Giant Coral Snake token selected using the dragged selection box approach, @{selected|token_id} still returns its correct ID, and as usual @{target|token_id} returns the wrong ID - which is the same ID you get wherever you click when asked for a target. Not sure if the disappearance of the token graphic is related to the @{target|token_id} problem or something else, or perhaps something someone going into the test game has caused - but I can't seem to restore the graphic, and I don't want to play with it too much in case the @{target|token_id} problem demonstration disappears before the devs can take a look.

Hello, have you received any answer form the team on a fix ? I encounter the same issue on one of my game

David M. said: Hello, have you received any answer form the team on a fix ? I encounter the same issue on one of my game No fix as yet. I'm having a fact sharing and exploring session with the Jumpgate dev team this afternoon.&nbsp; We'll see what comes out of it.

Hi, any news after the exploring session ? my next game is sunday and the game is still broken&nbsp;

David M. said: Hi, any news after the exploring session ? my next game is sunday and the game is still broken&nbsp; It was really good to share with Hales and Corey the game in which I can easliy demonstrate this issue.&nbsp; Corey is one of the senior Jumpgate devs, and he saw that the game was not behaving as it should.&nbsp; He could look "under the cover" and he saw things that shouldn't be happening, but could not at that point figure out why.&nbsp; Targetting in my example game is still not working, so clearly the fix is not there yet, and Hales has not contacted me with a progress update yet. I'm sticking with Legacy for now.&nbsp; I know you can't transmogrify backwards from Jumpgate to Legacy, but I've had to recreate games in the past 3 months in Legacy when this targetting problem first occurred - a major piece of work, but it had to be done.

Thank for you answer. Fortunately I had just split the game between my 2 groups so I can continue the adventure on the same game (wich wroks for now). The stranged thing is 2 weeks ago we play the game without any issue

My game is broken too, what can i do please?

I encounter the same issue with my two games now (but for the main game I still have correct target id only my players haven't. Could you help me please ?

I really wish I could help.&nbsp; Your best bet is to go to the Help Center, use the "Send a Request" button, and each of you log a call.&nbsp; The more calls, the more likely the devs are to focus on the issue - though I think they are now fully aware this is a major problem for several GMs.&nbsp; Raise it as a Jumpgate bug.

Two of my servers are unusable due to this bug. I've raised it through help center but it is stuck in "we're working on it" mode (still). BTW both servers that failed are new (past 2-3 weeks) and, in each case, they failed after two to three days. My older JG servers remain unaffected. This does mean, I cannot create any new games which is a serious issue when you are paying subscription fees for ("out of beta") products that don't work (in a pinch I will try going back to legacy but I'll lose access to all my recent work/resources). We really should get an update from R20 staff please (and yes, I'll post this request in other spots too).

DaemonSlye said: Two of my servers are unusable due to this bug. I've raised it through help center but it is stuck in "we're working on it" mode (still). BTW both servers that failed are new (past 2-3 weeks) and, in each case, they failed after two to three days. My older JG servers remain unaffected. This does mean, I cannot create any new games which is a serious issue when you are paying subscription fees for ("out of beta") products that don't work (in a pinch I will try going back to legacy but I'll lose access to all my recent work/resources). We really should get an update from R20 staff please (and yes, I'll post this request in other spots too). Well said!&nbsp; Fully agree.&nbsp; There are lots of cool things coming out in Jumpgate that I'd love to use, but I and my players are stuck in Legacy because of this bug, and I'm getting a little frustrated... The devs should stop creating new stuff and all work on getting this fixed!

Uh oh! Following this as a supporter of Peter B's AD&amp;D 2E character sheet and RIchard's supporting API Mods

Gold said: Uh oh! Following this as a supporter of Peter B's AD&amp;D 2E character sheet and RIchard's supporting API Mods Gold, if you look through this thread you'll see I've been raising this since before December 2024.&nbsp; Several bug reports from me, with examples of repeatable instances.&nbsp; I've even had a session with Hales of the support team and Corey of the Jumpgate devs, but still no joy... I've PMed The Aaron too so he is aware.

FYI - Hales responded to the other thread that they implemented a change to address. Not sure if it covers all of the connected issues, but in a very quick/smoke test, my two servers appear to be functional again. I'll need to test them tomorrow in more detail, but the targeting is now returning the proper value. Cheers!!

DaemonSlye said: FYI - Hales responded to the other thread that they implemented a change to address. Not sure if it covers all of the connected issues, but in a very quick/smoke test, my two servers appear to be functional again. I'll need to test them tomorrow in more detail, but the targeting is now returning the proper value. Cheers!! Certainly the demo game which I created that had a reliable and immediate example of the @{target issue seems to have been fixed.&nbsp; So now the fix needs extensive play testing because, as Hales says, there could be multiple issues with some remaining. Unfortunately, this being holiday time, my group aren't coming together again until August.&nbsp; We'll try a bar-room brawl with the RPGM APIs in JumpGate and see how it all works (the advantage of a bar-room brawl being I'm not doing loads of work and game play in an on-going campaign, with the risk of being disappointed...). Until then, it would be great to see what experiences others have, and if @{target now works reliably for a ccomplete game session in JumpGate. Exciting times!