The Jumpgate Beta for Pro Users Has Arrived!

Andrew W. said: 3d Dice and chat dice result do not match. This happens in my normal game all the time (see bug forums for more screen shots) but just so you know, I got the same problem with jumpgate. This screen from new Jumpgate game; Yeah this is an inherent issue that sometimes occurs with the 3D Dice engine and it's not something we've addressed in Jumpgate (yet) but we are aware of it and have a plan for it. Stay tuned!

Julia S. said: Hello, guys! Really appreciate all the quick fixes and looking forward to another go this weekend. Meanwhile I have a bug that is still an issue and I wanted to expand a bit on it - tooltips/nameplates problem. I've taken two examplary bugbears to test it out - one has a tooltip on ("Furry"), another - nameplate ("Big guy"). As a GM I see both the tooltip and the nameplate and I have all the settings on to show it to the players as well. The settings are: for the tooltip nameplate: general game settings for the nameplates to be shown: But when I reload as a player I see neither: Futhermore, in the turn order I also don't see either name even though at least for the bugbear with the nameplate on it usually meant that I was going to see the name in the initiative tracker. Turn order for GM: Turn order for the player: Okay thanks for the report we'll get this logged!

Hey folks, We just put out a quick update for Jumpgate that: Cleans up a bunch of old code that you all don't care about but makes our devs very, very happy Adds back in support for the "numbers" on the status markers! Thanks!

I think the issue with Julia's problem above is that Jumpgate games aren't obeying the Default Game Settings campaign-wide settings for the "See/Edit" values for Nameplates. So if you just drag and drop something from the sidebar, it's still being setup with Player's permissions to just "Edit" when it should be "See".

Alexander said: Riley D. said: Adds back in support for the "numbers" on the status markers! Unfortunately, the numbers still seem to be broken, just in a different way. When I use just the standard color dots, the numbers work. As soon as I try to use numbers on anything besides the colored dots, the whole thing breaks. As in, I largely lose the ability to put any marker on the token. The symbol will still highlight, as though it were selected, but nothing will appear on the token. What's more, this affect persists for that token forever, at least as far as I can tell so far. Even reloading only partially fixed it, causing some markers that were not showing to then appear. Attempting to put new ones on, however, still results in it being broken. Copying and pasting the token resets it for the new copy, but the problem quickly reappears if I try to put numbers on non-colored dot statuses. Okay noted! Let me pass that along.

keithcurtis said: Further, setting the campaign settings will not affect any token that has already been created and saved as a default before making the setting. Just new ones. To apply to existing tokens, you need to "Apply Defaults" under the Miscellaneous menu in the settings tab of the game. Also noting that I did test the Apply Defaults button and that _does_ seem to be working, it's just totally new tokens don't seem to be respecting the defaults the first time.

Midnite Oil said: I made a copy of my Chains of Asmodeus game and gave the JumpGate version a try. It was a disaster. So many issues. One player could not get any of the maps to load. Issues with several of my API Mod scripts.  Dragging tokens would sometimes appear to duplicate them on my DM page, had to refresh to often to see the updated position on the map.  The worst part is I added several pages and other things to prep for this session. After the session I went to transmogrify my additions to the old game only to discover that the copy does not show up in the list of games :(  Since I have no choice but to go back to the non-JumpGate version that means I have to redo a ton of prep in the old version :( Major disappointment. I usually wait until things have stabilized before I adopt a new feature. I should have known better than to be an early adopter.  Oh well, lesson learned. Hey there!  We do appreciate you giving it a try. Would you have any info to share on what API Scripts specifically weren't working? And then when you say dragging tokens would appear to duplicate them, what do you mean by that? Like just dragging the token around the map would...leave a copy behind that was semi-transparent permanently you couldn't get rid of?

Riley D. said: Alexander said: Riley D. said: Adds back in support for the "numbers" on the status markers! Unfortunately, the numbers still seem to be broken, just in a different way. When I use just the standard color dots, the numbers work. As soon as I try to use numbers on anything besides the colored dots, the whole thing breaks. As in, I largely lose the ability to put any marker on the token. The symbol will still highlight, as though it were selected, but nothing will appear on the token. What's more, this affect persists for that token forever, at least as far as I can tell so far. Even reloading only partially fixed it, causing some markers that were not showing to then appear. Attempting to put new ones on, however, still results in it being broken. Copying and pasting the token resets it for the new copy, but the problem quickly reappears if I try to put numbers on non-colored dot statuses. Okay noted! Let me pass that along. Hey there -- we think we just pushed out a quick fix for this, can you let us know if it's still happening to you? Thanks!

keithcurtis said: Riley D. said: Hey there -- we think we just pushed out a quick fix for this, can you let us know if it's still happening to you? Thanks! I can confirm that this token marker behavior was working broken as reported before the fix. It's better after the fix, there are still some existing issues: Token Marker placement is still too far into the token area Custom token markers still cannot receive numbers. Dots yes, custom, no. Okay so what I'm seeing is, dots + the built-in library of token marker images can get numbers applied. Custom token marker images cannot (although they don't break, just no number shows up). Is that what you're seeing?

Alexander said: Riley D. said: Hey there -- we think we just pushed out a quick fix for this, can you let us know if it's still happening to you? Thanks! As a previous poster mentioned, it is better now, but still not 100%. The token markers no longer seem to break, no matter what combination of them I click. The numbers themselves only work on the colored dots, however. I still cannot use them on custom status markers. When I try, the marker will appear, it just won't have a number on it. Edit: I also just tested, and the numbers do work on the built-in library of marker images. It just seems to be custom token marker images where they don't work at the moment. Also, I greatly appreciate the speed of fixes (or attempted fixes, as the case may be). Very helpful for me, since I am already trying to run my games in Jumpgate exclusively (no choice if I want to use dynamic lighting due to players with potato computers). We had actually stopped for several months because I wanted to hold out for Jumpgate in hopes the performance improvements would allow me to use dynamic lighting again.  That said, is there any news on the @{target} bug? Specifically, where players cannot use @{target} on a token they do not have control of? I know that target functionality is probably less widely used than other issues, but this is an extremely painful problem for my games, as my system is almost 100% reliant on @{target} functionality. Having to hand out control of everything to do anything is extremely painful for many reasons. It isn't quite game breaking, if only because we can technically work around it, but it introduces many difficulties and trade offs.  The @target bug is definitely a priority for us, I'll see what movement we can get on that this week. We really appreciate you taking the plunge with us and using Jumpgate for your games!

keithcurtis said: Is the list of known issues being updated? I can see a number of reports above that are not reflected there. Posting new issues and using strikethru on fixes would help beta testers see the progress, and test fixes as they are made. I will do a pass and update that on Monday, thanks for the reminder. Been focused more on the forums and all that but it's important to keep that up to date as well.