Inspect the wish at the earliest useful point
The published beach report found the active Visit Elegushi Beach wish completed on arrival, before any beach activity. The character gained three stars in that checked window.
That result does not make every beach visit a reward route. Read your own active wish and use the arrival check before deciding whether another purchase is needed.
Create a two-stage outing
Separate the visit check from optional exploration. Participants can agree to finish the first stage before discussing swimming, food or other scene entrances.
A menu quote is a comparison input
The tested Cab cost 650 each way, or 1,300 for the visit. Other modes were listed but not used in that outing, so their labels cannot establish the fastest or safest complete route.
| Evidence | What it supports |
|---|---|
| Two completed Cab trips | A recorded 1,300 total in that outing |
| Other mode labels | Options to inspect in the current menu |
| Visible beach activities | Places to investigate, not verified prices or effects |
Review the result before extending the plan
If the wish has already completed, another paid activity answers a new question. Name that question and record its starting state rather than treating it as part of the visit trigger.
The field report observed daytime access once. It did not map the venue’s full opening schedule, and scene descriptions alone cannot supply that schedule.
What if the result differs?
Confirm that the same wish was active and that the journey actually ended. A destination selected in a transport dialog is not evidence of arrival.
A one-point need change during a later save comparison does not identify a cause. Keep it separate from the earlier arrival and wish readings.
Sources & dates
Check what each source records. A menu label and a completed playtest are different kinds of evidence.
- dated public guideElegushi Beach arrival field report 7 Oct 2026