Riley D. said: However, some properties are changing from read-only to read/write, such as the "represents" property on Graphic objects. That means your scripts that previously used .get("_represents") need to be updated to .get("represents"). However, to ease the transition I've put a shim in place so that existing scripts should keep working properly. I'd like to make a point: It's probably a good idea for us coders to drop the leading underscore on calls to get , as that method is already prepending the underscore if necessary. Then, if a property changes like it is here, the code doesn't need alteration. The only "exception" I know of at the moment is the msg.selected array, the elements of which have the properties _id and _type; this is only sort of an exception to the above rule, since you're not using get to access them (the array elements are normal JS objects, not Roll20 objects).
