The current checks and strategies for handling the different sync modes at least partially rely on the assumption that FrooxEngine spits out connector changes immediately. If this turns out to not be the case, some of the existing logic can be simplified for efficiency and brevity.
With my unified approach to handling timeouts in #31, it doesn't really matter anymore what this underlying behavior is; the performance gains from optimizing for it specifically would be small in theory.
The current checks and strategies for handling the different sync modes at least partially rely on the assumption that FrooxEngine spits out connector changes immediately. If this turns out to not be the case, some of the existing logic can be simplified for efficiency and brevity.