@{character_name|Attribute|Max} now case sensitive.

Bug I've just noticed in Jumpgate games: Legacy is unaffected. When using "Max" to get the maximum value of an Attribute (like @{character_name|Attribute|Max} ), the "Max" is now case sensitive. @{character_name|Attribute|Max} will now return the CURRENT value, not the maximum, while it used to return the maximum (an still does on Legacy).  MAX will also no longer work right. @{character_name|Attribute|max} is now the only case I've found that will still return the maximum value in Jumpgate. Hopefully this is fixed quickly, otherwise I've got a lot of find & replace to do.....  :-(

Hi Kaganis,  I tested and was not able to replicate this. Which character sheet are you using? (It might be character sheet specific)

This is what I'm seeing in non-legacy just using the Attributes tab; created a new attribute called "max_test" and entered a couple values for current and max. Here's a test macro; @{selected|max_test|Max} @{selected|max_test|max} @{selected|max_test_Max} @{selected|max_test_max} @{selected|max_test|Max} seems to the only one that posts anything and it is returning the current value not the max. Here's what I see in a legacy game Seems that something's not working right in non-legacy...

Gauss said: Hi Kaganis,  I tested and was not able to replicate this. Which character sheet are you using? (It might be character sheet specific) I tested in multiple games using different sheets, including one that didn't use a sheet at all.

My partner has told me they had an issue where trying to use "max" in jumpgate was throwing them an "Unknown attribute" error, but I've not looked at that at all yet.  Might find time to do so tomorrow.

Ok, I don't know why I couldn't reproduce it before, I can now.  I have passed this to the Devs.

Kaganis said: My partner has told me they had an issue where trying to use "max" in jumpgate was throwing them an "Unknown attribute" error, but I've not looked at that at all yet.  Might find time to do so tomorrow. That is probably another issue related to their attribute call. Let me know if you need help with it.

Gauss said: Ok, I don't know why I couldn't reproduce it before, I can now.  I have passed this to the Devs. Thank you!  :-) There's clearly something weird about it we've not pinned down, between you not initially being able to replicate, and vÍnce having it go wrong in a slightly different way above.

Gauss said: Ok, I don't know why I couldn't reproduce it before, I can now.  I have passed this to the Devs. Age of game? I.e. works in an older game, not in a newer one?

keithcurtis said: Gauss said: Ok, I don't know why I couldn't reproduce it before, I can now.  I have passed this to the Devs. Age of game? I.e. works in an older game, not in a newer one? I had to restore an older Legacy game to test. Guessing it was created 6+ yr

keithcurtis said: Gauss said: Ok, I don't know why I couldn't reproduce it before, I can now.  I have passed this to the Devs. Age of game? I.e. works in an older game, not in a newer one? Could be possible.....  I don't know how to find the age / creation date of a game.  Can't find it on a quick look.  One game I had the problem in definitely dates back to shortly after Jumpgate's general availability, while I think the other is fairly recent (a few months old), but it's not my game so don't know for sure. Since it's only Jumpgate games affected, I wonder if it might be "was created as a Jumpgate game" vs "Was converted from a Legacy to a Jumpgate game"?  I think both I hit the problem were created directly as Jumpgate games. Don't think it's a Player Vs GM thing, one game I own, the other I'm only a player, had the problem as both.

It's gotten Even Weirder..... So, the test Jumpgate game I have, on the 15th / 16th I ran the following code on a character set up for it: selected|Test|max = @{selected|Test|max} selected|Test|Max = @{selected|Test|Max} Test is 1, Test|Max is 2.  The code returned the following: selected|Test|max = 2 selected|Test|Max = 1 All as reported above.  HOWEVER, I've just re-run it today, in the same game, same browser, same computer, same internet connection, same account, and get the following instead: (Icheerou Ehephu is the name of the test character sheet). This is very similar to what vÍnce got above.  If the nature of the problem isn't stable, it's no surprise Gauss was having problems reproducing it.... Definitely time to make sure I'm only using "max" in all my code....  :-(

Confirmed, where one of them used to call the current value now it doesn't even do that. And to throw one more thing into this, as sometime in the last week @{charactername|attributename|} no longer works Yes, that has a second "|" in it with nothing afterwards, it should call the current value but instead results in an error that gives a text output of Charactername|Attributename.  Unfortunately this has broken a number of my macros which use another attribute to switch between current and max value. (It is a complicated trick but I can explain it sometime if you'd like.)

Confirming here as well that I've been having this issue with the max value. I have a bunch of simple macros with the @{selected|value|Max} code. When Max is capitalized, it couldn't find it - but the lowercase m - max - works fine.  I had a similar issue where @{Selected|character_name} also threw back an error, and changing it to character_name (no capital C or N) fixes it. Like the Max issue, this doesn't seem to be a problem on legacy games. These macros I've had for over 5 years, easily, so it came to such a surprise to see them suddenly break during my previous session. Lucky for me, it's a copy and paste to fix them all, but it's definitely something that would be awesome to fix for those with far more complicated macros.

Should we submit a ticket for this Gauss or are the Devs aware there's an issue?