즈이멍이
If an object with an object sync component is inactive and a user enters the world late and interacts with it (in our case, "activates" it), it will sync in the wrong place: A location that was previously 'deactivated'.
Other objects that were not interacted with in that world will work fine, and users who entered the world earlier will work fine. But users who entered late will be screwed.
Here's how we encountered the problem
  1. a user who has already entered the world grabs the object (owner set)
  2. the object is 'disabled'.
  3. someone enters the world late.
  4. there is a synchronization problem when the object is 'activated'.
(*Honestly, this(4) is the hardest part to understand.
It's hard for me to figure out if it's only a problem when it's activated, or if it's other things like transforms after it's activated.)
*ex) transform, objectpool, teleport to