Group Check acting strange

 does anyone know why some of these numbers are coming up non bold and can't be hovered over to show a formula.

It also seems to be causing an issue with average rolls.

Have you run the config to properly set it for your chosen sheet?

keithcurtis said: Have you run the config to properly set it for your chosen sheet? Yes I have it set up for the 5e OGL sheet.

I can take a look if you invite me to the game and make me a GM.

It is actually happening in all my games.

I can confirm, it is also happening in all of my games as well - this is in several long term 5e campaigns that I have been using the script in for months without issue, configured for the official 5e sheet (the oldest one is well over a year old).

I can see the problem, though I don't know yet what is causing it. There has been a recent change to the 5E-OGL roll formula, this may be the cause of the problem. I'm going to investigate when I have time.

What seems to be happening is that once the complexity of a sent message, in terms of a large number of (nested?) inline rolls, is too large, the API will randomly stop sending results as inline rolls in the result message if the sendChat callback is being used (this behaviour seems to be nondeterministic). This only occurs with --process, since GroupCheck sends a direct message otherwise. The reason that this is showing up now is that I recently made the formula more complex (=added nested inline rolls) to deal with the OGL sheet's nonsensical treatment of proficiency dice and general bugs in the API roll parser. I know how to fix this, but it may be a bit before I can test this properly.

Jakob said: What seems to be happening is that once the complexity of a sent message, in terms of a large number of (nested?) inline rolls, is too large, the API will randomly stop sending results as inline rolls in the result message if the sendChat callback is being used (this behaviour seems to be nondeterministic). This only occurs with --process, since GroupCheck sends a direct message otherwise. The reason that this is showing up now is that I recently made the formula more complex (=added nested inline rolls) to deal with the OGL sheet's nonsensical treatment of proficiency dice and general bugs in the API roll parser. I know how to fix this, but it may be a bit before I can test this properly. Thank you for giving us the update! Appreciate your work as always!

Thanks for the update Jakob! I'll look forward to the eventual update. :)

Might be related to this?&nbsp; <a href="https://app.roll20.net/forum/post/6778746/slug%7D" rel="nofollow">https://app.roll20.net/forum/post/6778746/slug%7D</a>

It looks similar, except that Group B+C were empty and the rolls are replaced by some number that looks like it might be the result of the roll. I haven't checked if all the subrolls were assigned the correct index ... In any case, it was relatively simple to work around it by sending all of the rolls in parallel instead of sending them in one large message (+1 for Promise.all :) ).