Ruby and Sapphire clock, Shoal Cave tides and Berry glitch
Distinguish the working cartridge clock, tide windows, depleted battery and original calendar glitch.
Original Pokémon Ruby Version and Pokémon Sapphire Version for Game Boy Advance. Version-specific encounters and story roles are labelled. Emerald and the Nintendo 3DS remakes have separate rules and progression.
Shoal Cave uses two clock windows
Low tide runs from 03:00–08:59 and 15:00–20:59. High tide runs from 09:00–14:59 and 21:00–02:59. Low tide exposes the ice-room route and Shoal Salt; high tide supplies Shoal Shells. Return across the two layouts if you want the four of each material needed for a Shell Bell.
Check the effect, not only the message
A depleted internal battery stops real-time events such as Berry growth and daily changes while ordinary saved progression can continue. An emulator or re-release may handle the clock differently from an original cartridge. Verify that its time is advancing before planning a tide or Berry route. The bedroom clock sets the in-game offset at the beginning of the adventure.
The historical Berry glitch is different
Original Ruby/Sapphire also have a calendar bug that can stop timed events after a particular period of clock operation. Official patches were supplied through compatible Generation III software and historical distribution tools. A working battery and a corrected calendar are separate requirements; replacing a battery alone does not automatically describe every stopped-event case.
Keep an ordinary play plan
If timed events are frozen, the eight-badge adventure and League can still be pursued. Choose catches and supplies that do not depend on a changing daily event while investigating the clock. Record which tide layout is visible and whether newly planted Berries advance rather than changing the clock repeatedly without checking the result.
Use the Ruby or Sapphire version listed in the record. These guides cover the original Game Boy Advance games.