The implementation in #159 omits property paths in packets, with the assumption that property config is predetermined, and constant.

While in many cases this might hold true, it's possible to update property configurations during gameplay, even while some updates are in-flight. This would mean that by the time the packet arrives, it is based on a different version of the property config.

To fix this, updates get a tag denoting the version of the property config. Older versions are simply discarded.

Currently there's no plans for a more robust mechanism, as this is not a very common use case, and runtime property config changes won't be supported in v2.