Playgames field tools · version / date / reset
Daily Red versions: what each source actually says.
The tool uses dated visible statements, not a private game API. Source checks below were completed during the14October07:08 audit; implementing this page does not refresh their evidence date.
- amoi current entry
The current author entry states a reset at 00:00 UTC, a first recorded battle for the Hall of Fame and unlimited unranked rematches. It asks for a user-owned FireRed USA1.0 or1.1 ROM; this helper neither accepts nor supplies it. The current entry differs from the archived local-date code. Its live team and deployed date-to-team mapping have not been independently verified.
- daily-red.com browser edition
The visible page describes a browser-local midnight reset, one daily recorded run and practice in a Pokémon Showdown Gen3 simulation. This is a different browser implementation from the amoi FireRed entry. Matching dates do not establish identical teams.
- dailyredgame.org browser edition
This browser edition states a local-midnight reset, one scored attempt, turn saves and practice after the result. These are its own page claims. Its published browser-edition rules are not proof of the original FireRed version or identical daily teams.
- dailyredpokemon.com browser edition
This browser edition describes a local-midnight reset, one recorded attempt, practice and continuation of an unfinished run. It describes a custom Gen3 simulation. A different simulation and species pool can produce a different team on the same calendar date. Backend/gameplay behavior is untested here.
- Archived amoi daily.js — local-date code
The archived file uses local calendar methods for the date/next midnight. It is evidence of that archived revision, not evidence that the current webpage’s stated UTC rule uses the same deployed generator. We do not calculate a live team from it.
- Player discussion — same challenge number, different teams
Players describe different browser-edition teams and ask about battle rules. This establishes a concrete help request, not audited scores, compatibility, market size or a paid conversion.
- Existing support guide and version comparison
A support comparison already exists. This helper adds a usable explicit website/timezone/calendar label; ordinary version comparisons and battle tips are not claimed as a new market gap.
Current entry and archived code are separate evidence
The public current entry says UTC, while an archived source file uses local dates. The deployed app script could not be read through normal navigation in the audit. No game or ROM was loaded. The helper therefore follows the current entry’s stated reset basis but leaves its actual date-to-team mapping unknown.
A boundary is not a live-team verification
IANA timezone mathematics can calculate the next calendar midnight, including DST boundaries. It cannot verify that a website’s backend changes its challenge exactly then. This page deliberately has no current-team lookup, original-game seed output, damage calculator or guaranteed-win strategy.