Tideturner
February 11th, 2021, 14:06
Hi,
in FGU setting string values that can be represented as numbers ("10","20","30" etc.) are stored as number between sessions. At least this is the case for the options cycler.
This results in the setting displaying the base value on next load, instead of the actual stored value. Probably because 10 and "10" f.ex. are not exact matches.
In FGC the value was store as a string.
I've attached a small extension that illustrates this. I've also attached a CoreRPG campaign with the extension enabled. Campaign and extension was made in the current Test channel and not the live if that matters.
Both the extension and the setting it adds are called "A Baboon Settings Bug", to display at the top of the extension- and settings list respectively. I'm very sorry.
In this first picture, you can see the options cycler displaying the value "1".
I've then clicked on the /whats_in_the_bug slash command that outputs the value in chat. Here you can see the actual value is 2 and a number. That's what I set it to before a /reload.
https://www.fantasygrounds.com/forums/attachment.php?attachmentid=43633&d=1613051219
In this next picture I've advanced the cycler to the value "3".
I've again clicked the slash command and you can see the new value now is "3" and a string.
https://www.fantasygrounds.com/forums/attachment.php?attachmentid=43634&d=1613051245
I don't know if this is an issue at all for other stuff, but it was my NPC flavors extension. I've worked around it, so I'm personally good with this just being a FGU quirk to be aware of.
But since it might affect other parts of the rulesets or other extensions, I thought I'd report it.
Regards,
Tideturner
in FGU setting string values that can be represented as numbers ("10","20","30" etc.) are stored as number between sessions. At least this is the case for the options cycler.
This results in the setting displaying the base value on next load, instead of the actual stored value. Probably because 10 and "10" f.ex. are not exact matches.
In FGC the value was store as a string.
I've attached a small extension that illustrates this. I've also attached a CoreRPG campaign with the extension enabled. Campaign and extension was made in the current Test channel and not the live if that matters.
Both the extension and the setting it adds are called "A Baboon Settings Bug", to display at the top of the extension- and settings list respectively. I'm very sorry.
In this first picture, you can see the options cycler displaying the value "1".
I've then clicked on the /whats_in_the_bug slash command that outputs the value in chat. Here you can see the actual value is 2 and a number. That's what I set it to before a /reload.
https://www.fantasygrounds.com/forums/attachment.php?attachmentid=43633&d=1613051219
In this next picture I've advanced the cycler to the value "3".
I've again clicked the slash command and you can see the new value now is "3" and a string.
https://www.fantasygrounds.com/forums/attachment.php?attachmentid=43634&d=1613051245
I don't know if this is an issue at all for other stuff, but it was my NPC flavors extension. I've worked around it, so I'm personally good with this just being a FGU quirk to be aware of.
But since it might affect other parts of the rulesets or other extensions, I thought I'd report it.
Regards,
Tideturner