[GroupCheck] Incorrect Result; NPC = 1 is seen as NPC = 0 in GroupCheck output

Reposting this from original post:&nbsp; <a href="https://app.roll20.net/forum/post/12223260/groupcheck-incorrect-result" rel="nofollow">https://app.roll20.net/forum/post/12223260/groupcheck-incorrect-result</a> Having calculation issues with GroupCheck. Configuration: 1 – Jumpgate 2 – Using D&amp;D 5E 2014 by Roll20 sheet AND 2024 Beacon sheets 3 – GroupCheck “latest” version from the Roll20 Mod Library 4 – GroupCheck configured for 5e-OGL Issue: For 2014 sheets, GroupCheck is calculating the wrong result no matter which check I choose. Example: Strength check The picture below shows the results from the “Strength Check” formula shown below: FORMULA = [[d20 + ([[d0 + @{strength_save_bonus}@{pbd_safe}]]*(1-@{npc})) [PC] + (@{npc_str_save}*@{npc}) [NPC]]] It’s getting the @{strength_save_bonus} correct (3) Not getting correct value for @{npc} (1). The value for the “npc” attribute on the character sheet is 0, not 1.&nbsp; Even if I change “npc” value to 2000, it still shows (1). Still get a 1 if I delete the “npc” attribute. Not getting correct value for @{npc_str_save}. It shows (2), which matches my strength modifier, but I can’t find @{npc_str_save} anywhere on the character sheet attributes. Is anyone else seeing a similar issue? ***************************************************************************** The PRIMARY issue is GroupCheck is seeing @{npc}=1 when it should be "0" ***************************************************************************** For 2024 sheets, the result seems to work, BUT, it's working out of sheer luck... For the 2024 PC sheet, when I type&nbsp;@{selected|npc}, the chat shows "on". Which is wrong... Shouldn't be equal to 0? When GroupCheck is initiated, it sees NPC=1 and uses the [NPC] section of the formula. This yields the correct value in GroupCheck but its using the [NPC] side of the equation. For the 2024 NPC sheet, when I type&nbsp;@{selected|npc}, the chat shows 0. Which is wrong... Shouldn't be equal to 1, not 0? Nonetheless, GroupCheck still yields a correct result because now its using the [PC} side of the formula sine (1-0)=1

I certain that this is related to the @{npc} attribute&nbsp; being switched &nbsp;between the 2014 and 2024 sheets. I hope that devs decide to fix the attribute now, which will definitely take a bit of adjusting a lot of sheet dependencies, but will ultimately be easier to fix the sooner it happens.&nbsp; The values for @{npc} are not consistent between the 2014 sheet and the 2024 sheet.&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;2014 PC @{npc} value is &nbsp;'0' &nbsp; &nbsp; 2024 PC&nbsp; @{npc} value is ' on' &nbsp;&nbsp;&nbsp;&nbsp;2014 NPC&nbsp; @{npc} value is ' 1' &nbsp; &nbsp;&nbsp; 2024 NPC @{npc value is '0'

Hi Jaren. I didn't realize the @{npc} attribute topic was brought up on another forum. Thanks for linking me to that one. But it doesn't explain why GroupCheck is calculating the 2014 PC sheets incorrectly.&nbsp; The 2014 PC sheets show value '0' for @{npc}. BUT GroupCheck interprets it as a '1'...? You can see this in the picture I posted above. It has a '(1-1)' value in the [PC] section of the formula even after I verify the 2014 PC sheet is showing a '0'.

My guess is because if both sheets are used in a game, how the Beacon architecture deals with the initial command parses it through the 2024 sheet first or something. Because it doesn’t happen when there’s only the 2014 sheet. Or the other possibility is that GroupCheck is checking to see which sheets are in a game and somehow getting a bad reference when the 2024 sheet is present.&nbsp; I honestly have no idea why the 2014 and 2024 sheet use different/ opposite values for the @{npc} attribute.&nbsp;