In the announcement, on the same date, why do we still need to check the time zone? Because a date only tells you “which day,” not necessarily the “exact cutoff moment.” UTC and Beijing Time differ by 8 hours; if you read it wrong, your operation window may start earlier or later.
For example, suppose the announcement says the cutoff is “23:59 on September 30 (UTC).” Converted to Beijing Time, that becomes 07:59 on October 1. If you treat it as Beijing Time “23:59 on September 30,” then you would actually stop 8 hours early. This example is just for teaching purposes and does not correspond to the current event. If the announcement already specifies the time zone, the platform countdown will also display using that same time zone, and any ambiguity is then considered resolved.
When you see the announcement, copy the date, the exact time, and the time zone, then compare them item by item with the cutoff notice on the event page. If it only says “September 30” and doesn’t specify the time zone, first assume that the cutoff time is not yet determined.
For example, suppose the announcement says the cutoff is “23:59 on September 30 (UTC).” Converted to Beijing Time, that becomes 07:59 on October 1. If you treat it as Beijing Time “23:59 on September 30,” then you would actually stop 8 hours early. This example is just for teaching purposes and does not correspond to the current event. If the announcement already specifies the time zone, the platform countdown will also display using that same time zone, and any ambiguity is then considered resolved.
When you see the announcement, copy the date, the exact time, and the time zone, then compare them item by item with the cutoff notice on the event page. If it only says “September 30” and doesn’t specify the time zone, first assume that the cutoff time is not yet determined.