Summary: 23 instances, 20 unique

Text	Count
// TODO: Add in MRE ID's to help identify whether the new parent is in our MRE or not, not just	1
* TODO: Remove after a few releases.	1
// TODO @tombu, @eanders - We need to decide on the correct cleanup timing here for multiplayer, as this could cause a potential	1
// TODO: Report this error up to the app, once we have implemented error logging payloads.	1
// TODO: Write user changes to the patch.	1
// TODO: Make X, Y, Z, and W fields non-optional, since you can't just specify one and maintain a valid unit quaternion	1
// TODO: Send this update if actor is set to "high-frequency" updates	1
// TODO: verbose log the message, once MREAPI global logger exists	1
// TODO: We shouldn't need to do this check. The engine shouldn't try to send	2
// TODO: Objects should not be visible until synchronization is complete.	2
// TODO @tombu - This will be added to allow for a more override model for high level behaviors.	1
// TODO: Log the error, once MREAPI global logger exists	1
// TODO: other compound types (color3, color4)	2
// TODO @tombu - Re-visit this with the upcoming user design and implementation.	1
// TODO @tombu - Determine if the new parent is an actor in OUR MRE.	1
// TODO: Add ability to flag an actor for "high-frequency" updates	1
// TODO @tombu - Wait for the app to send back a success for join?	1
// TODO: Log the exception, once the global MREAPI logger exists.	1
// so this could be generating garbage. TODO: Investigate this implementation.	1
/* TODO @tombu - Re-vist this with the upcoming user design and implementation.	1