PhotonEngine DateTime serialization shows unexpected offset behavior for non-UTC locales

When exchanging timestamp values between PhotonEngine clients configured in different regional time zones, it is unclear whether the serialized payload preserves the original UTC offset or undergoes an implicit local-time conversion. The goal is to determine if PhotonEngine’s built-in serialization automatically converts UTC DateTime values to the receiving client’s locale, or whether it passes the original value through unchanged.

Documentation indicates that date conversion relies on configured locale settings and underlying data source integration, but it does not specify whether this transformation happens during serialization, deserialization, or only at the presentation layer. This ambiguity complicates the design of time-sensitive multiplayer state that must remain consistent across regions.

Assuming a recent PhotonEngine version using standard timestamp or DateTime data types, what is the expected serialization behavior for a value explicitly created with a non-UTC time zone offset? Does the serialization layer normalize the value to UTC, apply the client’s local offset, or retain the original offset on the wire? How can the actual serialized representation be confirmed for a specific client locale?