Modern Emerald clock: real time, fake time and event checks

Read which clock mode this run uses

The README points to the Pokémon Center PC’s CHALLENGES entry for reviewing enabled and disabled run options. Record the actual clock choice alongside the game build before comparing a timed event.

Use the documented time controls deliberately

The creator’s version-specific FAQ says that from 3.0, clock changes must use R+B+Left at the title screen. The README also lists R on the clock. These descriptions differ; for a 3.0+ adjustment, follow the FAQ’s title-screen route and your matching build instructions.

The FAQ describes date resets as a cause of stalled time events. Record the date and time, keep the working save and use the FAQ’s title-screen route for a matching 3.0+ build. Afterwards, inspect the event as well as the clock display.

Record the original displayed time before making a change. Adjust only when that serves the task, then inspect the new display. If the input does not register, check that the expected GBA buttons reach the game before treating the event as broken.

The settings guide owns broader run-option permanence and exceptions. The documentation’s clock rate is not a measured statement about sleep, suspend, fast-forward or every emulator’s RTC implementation.

Make one recorded clock comparison

1. Keep the build, runtime and RTC mode fixed.
2. Record the displayed time and the specific event you are checking.
3. Choose either normal observation or one deliberate documented adjustment; do not alternate both without notes.
4. Inspect the displayed time again, then inspect the event separately.
5. Write down which result changed: the clock, event availability, both or neither.

If you compare another emulator, preserve the original setup and progress so both runs start from the same situation.

A correct clock does not unlock every event

Before another clock change, establish the target’s encounter or access rule. Modern Emerald’s selected encounter tables and campaign phase are separate from time. For a species, use the location and encounter-mode guide.

For berries, trades and daily rewards, use the event’s own refresh instructions. The fake-clock ratio describes clock speed, while each event can have additional conditions.

Example: time changes but the target is still absent

Keep the recorded time, check the selected table and progression condition, then choose the next action from that result. Repeatedly changing time before identifying the encounter rule would leave the same question unresolved.

Read the game’s day, night and morning windows

The maker feature list describes daytime as 06:00–20:00 and night as 20:00–06:00. For two new evolutions, it names a narrower morning window of 06:00–09:00. A morning requirement is therefore more specific than a general daytime requirement.

Example: the game shows 14:00 and a reference asks for morning. The display fits daytime but does not fit the narrower named period. Resolve that distinction before trying another item, replacing the Pokémon or changing runtime settings. For an evolution, also look up the species’ full method in the maker documentation.

Near a boundary, record the exact display and the action attempted. Use the clock’s exact display alongside the matching event instructions. If the action fails at a boundary, record when you tried it and whether a menu was open; lighting alone gives less detail.

Maker day/night and clock FAQ reference, checked 8 Oct 2026. The documented windows and the fake-clock ratio answer different questions: one defines a named period, the other describes the selected clock’s pace.

Record the task as well as the time you changed

Before adjusting the clock, finish this sentence: “I want this action to become available, and the reference says it needs this period.” If you cannot name the action or its requirement, changing time would leave the actual question unresolved.

1. Write the exact target: evolution, encounter or named event.
2. Read its own method and non-time requirements.
3. Record build, clock mode and displayed time.
4. Use the documented control only if the target calls for a different period.
5. Inspect the time, then perform the required action deliberately.
6. Record whether the action became available, not only whether the clock moved.

Example: after a time adjustment, the display enters the requested period but the evolution still does not occur. That narrows the remaining task to the species’ complete method or the action that triggers it. It does not show that time adjustment failed. Do not consume unrelated items or repeatedly change emulator settings before identifying that missing condition.

Use the evolution-versus-recruit decision for an existing teammate. For a search, use the encounter input check. These handoffs preserve the specific task instead of treating every missing result as an RTC problem.

Sources and next steps

Creator documentation, checked 8 Oct 2026. The README covers clock modes; the linked FAQ covers the 3.0+ adjustment route and time windows. Both source checks remain dated 8 Oct 2026. Examples and comparison steps are editorial guidance, not an independent RTC test.

game profile · GBA emulator, controls and saves