Macro suddenly produces 2 lines per result

I have a macro that rolls Spot for each of the PCs and whispers them to the GM (me). Suddenly, it is producing 2 lines per roll as shown below. It never used to, so I'm guessing something has changed in the backend somewhere  /w gm &{template:default} {{name=Spot}} {{baylock=[[1d20+@{Baylock|Spot}]] }} {{chambu=[[1d20+@{Chambu|Spot}]] }} {{Baggy=[[1d20+@{Baggy Sackdottir|Spot}]] }} {{Talian=[[1d20+@{Talian|Spot}]] }} {{Nazariel=[[1d20+@{Nazariel|Spot}]] }} Normally it should show the plain lines; but this "computed::lower case name" line is new 

This is a bug related to a feature that went live today, that I reported here <a href="https://app.roll20.net/forum/permalink/10226883/" rel="nofollow">https://app.roll20.net/forum/permalink/10226883/</a> during its testing phase and my report was apparently ignored. Yet another example of roll20 releasing stuff on the Dev server for feedback, and then ignoring that feedback. Now that it's live for everyone, I expect it'll be fixed fairly quickly.

Oh, yeah, so I see. So the Admin on discovering that the bug has been moved live rather than fixed, closes the thread reporting it?&nbsp;

It was hotfixed yesterday.&nbsp; Not as good as fixing it before public release, but at least it is fixed. It is pretty common for them to close a thread that was for dev server testing feedback once the feature is released live to everyone.

No, I think they closed the thread before they realised the bug was a problem (they didn't investigate my report). They close those Dev Threads pretty quickly as soon as things go from Dev to Production (always too quickly iMO). They weren't trying to suppress discussion of a problem, they just didn't realise there was a problem yet. Edit: Ninja'd!

Ah, OK. And Shazam! Problem is gone! Pretty good turnaround from my perspective :)

If this was hotfixed, how come it is still happening? (specifically in every macro I have that involves a roll query with a drop-down prompt). Is there any way I can report that as a bug?

Can you post the name of the character sheet you are using, and the text of any macro that produces this error. Is it the exact same error, with a "computed:" value? If not, please post a screenshot.

I set up a very simple example case: the following set up as a macro in the collection, so with no character sheet involved at all: &amp;{template:default} {{name=test}} {{= ?{option | d6, d6 [[1d6 ]] | d20, d20 [[1d6]] } }} result:

Hmm, doesn't look like the picture posted, results copied as text: Mark F.: test d6&nbsp;<span class="inlinerollresult showtip tipsy-n-right" original-title=" Rolling 1d6 = ( 3 )" style="box-sizing: content-box; background-color: rgb(254, 246, 142); border: 2px solid rgb(254, 246, 142); padding: 0px 3px; font-weight: bold; cursor: help; font-size: 1.1em;">3 Computed:: d6&nbsp;<span class="inlinerollresult showtip tipsy-n-right" original-title=" Rolling 1d6 = ( 3 )" style="box-sizing: content-box; background-color: rgb(254, 246, 142); border: 2px solid rgb(254, 246, 142); padding: 0px 3px; font-weight: bold; cursor: help; font-size: 1.1em;">3

Further info: if I actually name the selection the issue does not occur. Like &amp;{template:default} {{name=test}} {{test= ?{option | d6, d6 [[1d6 ]] | d20, d20 [[1d6]] } }} shows as&nbsp; test Test d20&nbsp;<span class="inlinerollresult showtip tipsy-n-right" original-title=" Rolling 1d6 = ( 4 )" style="box-sizing: content-box; background-color: rgb(254, 246, 142); border: 2px solid rgb(254, 246, 142); padding: 0px 3px; font-weight: bold; cursor: help; font-size: 1.1em;">4 This is not a solution however as I often really want to not have a key name appear on the left since in&nbsp; various macros the nature of the roll can vary wildly depending on the selection made so a generic name would be confusing. Hope that helps.

It looks like you've found a bug, and the way to replicate it. Based on my tests, if you remove the = sign, you should get back the old behavior, like &amp;{template:default} {{name=test}} {{?{option | d6, d6 [[1d6 ]] | d20, d20 [[1d6]] } }}

The "allprops() computed bug" cropped up in tonight's game as well ;-(&nbsp; Wasn't this fixed on the Live servers last week? &amp;{template:pf_generic} {{color=darkred}} {{header_image=[x](<a href="https://raw.githubusercontent.com/Roll20/roll20-character-sheets/master/Pathfinder%20Community/Images/pf_generic.png" rel="nofollow">https://raw.githubusercontent.com/Roll20/roll20-character-sheets/master/Pathfinder%20Community/Images/pf_generic.png</a>)}} {{name=Random Direction Roll}}{{subtitle=Direction (1d8) : [[1d8]]}}{{=[[4]][[5]][[6]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [[3]][[ 1-1d1cf&lt;1cs&gt;0 ]][[7]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [[2]][[1]][[8]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }} GiGs said: It looks like you've found a bug, and the way to replicate it. Based on my tests, if you remove the = sign, you should get back the old behavior, like &amp;{template:default} {{name=test}} {{?{option | d6, d6 [[1d6 ]] | d20, d20 [[1d6]] } }} Removing the = prevented the error, but seems to also change the intended output... The directional grid should be centered. But, it looks like you can use " =" (space before the equal sign) the intended allprops formatting and avoid the extra computed line. &nbsp;&amp;{template:pf_generic} {{color=darkred}} {{header_image=[x](<a href="https://raw.githubusercontent.com/Roll20/roll20-character-sheets/master/Pathfinder%20Community/Images/pf_generic.png" rel="nofollow">https://raw.githubusercontent.com/Roll20/roll20-character-sheets/master/Pathfinder%20Community/Images/pf_generic.png</a>)}} {{name=Random Direction Roll}}{{subtitle=Direction (1d8) : [[1d8]]}}{{ =[[4]][[5]][[6]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [[3]][[ 1-1d1cf&lt;1cs&gt;0 ]][[7]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [[2]][[1]][[8]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }}