Make text object editable by all players

Hello Roll20 API brain-trust! I'm running a MONSTER OF THE WEEK game, and I'm hoping to make some text objects on the tabletop editable by all players for note taking purposes. I like the idea of having them displayed on a "paper" on the tabletop, rather than living in a shared handout. I know there is a `controlledby` attribute for all text objects, but I can't wrap my brain around how to set that attribute using API scripting. I found this post and this post , but my brain is still unable to make heads or tails of it. Any advice would be greatly appreciated!

Hi L.B.! Try this script Controllers A small GM-only utility script for quickly adding or removing the special "all" controller from selected objects. This works on: Paths and Pathv2 objects (This does not yet work, and is likely a Roll20 bug. I am investigating) Text objects Graphics that do not represent a character Opening the Menu Command: !controllers This opens a whispered chat menu with buttons for each supported object type.The buttons in the menu modifiy the controlledby property on supported objects. all  Adds "all" to the object's controller list if it is not already present. This allows all players to interact with that object. none  Removes "all" from the object's controller list. Menu Options Paths  Processes selected path and pathv2 objects. (Roll20 bugged) Texts  Processes selected text objects. Graphics  Processes selected graphics and cards, but only if the object does not represent a character. Selected  Processes all supported selected object types at once. If you do not wish to use the menu, here are some sample commands. You can always discover a command by pressing the button and using the up arrow in chat to see what was issued.: !controllers --paths --all Adds "all" control to selected paths. !controllers --graphics --none Removes "all" control from selected graphics/cards. !controllers --selected --all Adds "all" control to all supported selected object types at once. Notes The script only affects currently selected objects. If no objects are selected, the script whispers a warning to the GM. Supplying an object type without --all or --none will generate an error message.

AMAZING, Keith, thank you so much for sharing this!!!

I'll post an update if I get a favorable answer on handling paths.