A Potential Workaround I was asked to share a workaround that can help fill the gap while we wait for GroupInitiative to get patched: You can get a bunch of tokens into the Turn Tracker (or update their entry that is already in the Turn Tracker) with *individualized* roll results by using the Metascript Toolbox (available in the 1-click). The following command uses a d20 that will be randomized for each token individually as well as a "modifier" that will be shared by all tokens. In other words, the roll will be individual but the modifier will be the same, so when you choose tokens to enter/update in the Turn Tracker make sure you choose tokens that should all be represented by the same modifier. With the tokens selected, run this command: !forselected(^) /w GM @^(selected.token_name) [^\[^\1d20 +?{modifier} {^&tracker} \^]\^] {^&simple} This will whisper the results to the GM: And it will apply these same numbers to the Turn Tracker for these tokens: Extended: Select Tokens Automatically You can use another feature of the Toolbox to select tokens automatically based on their name, the presence (or value) of a status marker, a bar value, a tag on the character sheet, or something in the gmnotes of the token, among other features... and/or a combination of these. This would mean that you don't have to physically select the tokens on the VTT prior to running the above command. You could, instead, simply run the command and have the Toolbox find and select the tokens for you. For instance, maybe you've set up your encounter to have a group of Night Clan tokens ambush the party. You've named these tokens Night Clan 1, Night Clan 2, etc. That means you select any of the Night Clan tokens on the page by their name: {&select Night Clan*} ...or, if you used bar1 for hp/health and you wanted to only select those tokens who were still on their feet: {&select Night Clan*, +bar1>0} Adding this to the above command would look like this: !forselected(^) /w GM @^(selected.token_name) [^\\[^\\1d20 +?{modifier} {^&tracker} \\^]\\^] {^&simple} {&select Night Clan*, +bar1>0} ...and would create/update an entry in the Turn Tracker for every token whose name began "Night Clan" and who had a bar1 value over 0. (Note, for the meta-curious, that the introduction of the {&select} tag means the metascript loop will do work on the original message, causing another trip through the loop, and for this reason we need another backslash -- ie, another deferral -- on the inline roll to make sure it resolves at the correct point.) The full set of criteria you can use in a {&select} tag is discussed in this post , with the character tag syntax being added in this post . To really make this command flexible, you could include multiple groups in a query that allowed you to choose between them at the point where you need to add/update them in the Turn Tracker: {&select ?{Which group|Night Clan|Baking Club|Town Rotary|Omphaloskepsis Brigade}*, +bar1>0} Note that the above examples use the name of the token as one component of the selection. You could instead use something like an entry in the gmnotes of the token to derive your selections: {&select *, +gmnotes ~ " ?{Which group|Night Clan|Baking Club|Town Rotary|Omphaloskepsis Brigade}", +bar1>0} Extended 2: Use Assemble Script to Build Groups If you use the Assemble script to build your groups, you can refer to the group attribute in a {&select} tag like so: {&select @{Actual Cannibal|Baking Club} } That would use Roll20 syntax to return the "Baking Club" attribute from the character "Actual Cannibal," where you would have instructed the Assemble script to store the tokens that were a part of this foul and loathsome crew. Again, you could use a query to choose between groups, but since your groups probably contain lists delimited by commas, I would suggest using Fetch constructions to return them so that the commas do not break the query syntax: {&select @(Actual Cannibal. ?{Which group|Night Clan|Baking Club|Town Rotary|Omphaloskepsis Brigade}) } As mentioned in the thread for Assemble, this requires a non-Beacon sheet (the 2024 D&D sheet is Beacon, the 2014 D&D sheet is not). If you are running a 2024-sheet game, you will have to enable the 2014 sheet in your game (running both sheets) to make use of Assemble in this way.
