Nesting Roll Queries not working

Nesting Roll Queries is not possible anymore : I can't save a macro with HTML entities : ---->

Nesting using HTML Entities is an unsupported hack that happily works.  I tried typing your action in and it worked for me in a character ability: ?{name of Query|Label1, ?{value1|Label 1A,value1A|Label 1B,value1B}|Label 2,?{value2|value2}} The unfortunate thing about websites is that the inputs may get modified by your browser before going to the site.  You might try double encoding the entities: ?{name of Query|Label1, ?{value1|Label 1A,value1A|Label 1B,value1B}|Label 2,?{value2|value2}} by replacing all the & with & What browser are you using?

Chrome. It work great for a character ability, but it seems that Roll20 modifies the input for the macro when I save them : I can still write the code (found in the macro wiki btw) in a macro and test it, it will work. But if I try to save the macro, and open it again, I will see the macro without the HTML (does not happen with abilities) . Since all was working fine 2 weeks ago, maybe the last update changes something ? Anyway, if it's an unsupported hack, I doubt we can treat this as a bug...

It indeed would be nice if General Macros preserved HTML entities as Ability Macros do. You could opt to save your macros which contain HTML entities as Abilities and call them from General Macros.

Yes, I'm gonna do that for now, but the fact is that general macros preserved HTML entities two weeks ago, so it's a little bit annoying ^^ EDIT : Well, I'm not sure anymore, but I think it was working good before...

Alzam said: Yes, I'm gonna do that for now, but the fact is that general macros preserved HTML entities two weeks ago, so it's a little bit annoying ^^ EDIT : Well, I'm not sure anymore, but I think it was working good before... The way I understand it is that they will stay until you open it a second time, then they stop working. So if you put them in there and never edit it again the HTML entities will work in a general macro. Not the best thing to go with though, that's for sure.

Using Aaron's workaround should work. I replicated this on my end with Google Chrome and had the same results. Aaron's or Silvyre's work-around should work but I'll look into this to see if there is anything we can do to make this easier so you don't need to use a work-around.

Ryan H. said: I'll look into this to see if there is anything we can do to make this easier so you don't need to use a work-around. Wow, that would be awesome. Thanks!