fix: exploration timer exceeds the area's stated duration #53

New Issue

2026-03-18T11:03:01-07:00

hikari commented

2026-03-18 11:03:01 -07:00

Description

Exploration areas display a stated duration (e.g. 1 hour) but the actual countdown timer is longer than advertised (e.g. 1h15m). This is likely caused by the timer starting from when the server receives the request rather than when the client initiates it, or by clock drift between client and server.

Steps to Reproduce

Start an exploration in an area with a known duration
Observe the countdown timer
Note that the timer exceeds the stated duration

Expected Behaviour

The countdown timer should match the area's advertised duration.

Reported By

Community member kindally

✨ This issue was created with help from Hikari~ 🌸

## Description Exploration areas display a stated duration (e.g. 1 hour) but the actual countdown timer is longer than advertised (e.g. 1h15m). This is likely caused by the timer starting from when the *server* receives the request rather than when the client initiates it, or by clock drift between client and server. ## Steps to Reproduce 1. Start an exploration in an area with a known duration 2. Observe the countdown timer 3. Note that the timer exceeds the stated duration ## Expected Behaviour The countdown timer should match the area's advertised duration. ## Reported By Community member `kindally` ✨ This issue was created with help from Hikari~ 🌸

hikari referenced this issue from a commit

2026-03-18 16:46:56 -07:00

fix: use server-computed endsAt for exploration timer to prevent clock drift

hikari referenced a pull request that will close this issue

2026-03-18 16:47:03 -07:00

fix: use server-computed endsAt for exploration timer to prevent clock drift #68

naomi closed this issue

2026-03-18 17:09:48 -07:00

naomi referenced this issue from a commit

2026-03-18 17:09:49 -07:00

fix: use server-computed endsAt for exploration timer to prevent clock drift (#68)

Sign in to join this conversation.