So client.index is available now but it's still inconsistent with the other uses for syncer.
For example, when triggering a network event for an element's syncer you use the client object itself in the args (meaning you still have to use a loop to get which client's index matches element.syncer), but when setting it's syncer you have to use the client's index instead.
For example, when triggering a network event for an element's syncer you use the client object itself in the args (meaning you still have to use a loop to get which client's index matches element.syncer), but when setting it's syncer you have to use the client's index instead.