Nazamura said: late in the past, when we wrote macros, there was no need to use html markup, it worked, but now, it doesn't, you need to pay extra attention to html markup and it become confusing and complicated to give maintenance to old macros You do not need to use HTML replacement unless you are putting things inside queries (see Nesting Queries ). This really isn't a case of Roll20 changing anything. Based on your other thread you opened the Collection tab macro, and that broke it because Collection tab macros break HTML Entities. There is a known issue that when you put HTML entities in a Collection tab macro and then open it later it resolves all the HTML Entities. This is why it is recommended to NOT use Collection tab macros for macros that contain HTML Entities. Use Ability macros instead.