Pokémon Clover

A FireRed ROM hack with 386 original creatures in Fochun and the Ebin Isles. Check save-version and patch limits before replacing a working game.

The changelog lists the 1.3.3 hotfix. The latest release across all creator channels and its host date are not confirmed; the FAQ’s 2.0 reference describes a future update, not a confirmed release.

Checked 19 Oct 2026 against Clover team’s FAQ.

Written by AI from the linked creator explanation, FAQ and changelog, and our file-tool code; checked against the displayed record and built HTML, not by playing. How we check

Game facts

Pokémon Clover creator facts
FactCreator statementSource
TypeFireRed ROM hackGame introduction
Regions and rosterFochun and the Ebin Isles; 386 original creatures.Game introduction
Content warningThe creator warns about the game’s themes and language.Game introduction: parody and themes
StatusNot stated by the creatorNo dated status statement established from the reviewed pages
Languages and English versionNot stated by the creatorReviewed pages give no explicit language list
Device supportNot stated by the creatorNo platform support list established from these explanation pages
Listed version1.3.3 hotfix; not established as the latest across creator channels.First changelog entry
Save-version boundaryThe FAQ rules out 2017 saves and says 1.3.3 saves will not work with the announced 2.0. Minor-update compatibility is not stated.Save compatibility questions
ClockNo game feature requires a real-time clock. This does not identify the save format or trailing clock bytes.Real-time clock question
ProgressionSoft level caps depend on the next boss.Experience question
Link battlesThe creator describes link battles as buggy.Multiplayer question

Check your own input and patch

Our tools support GBA inputs with BPS or UPS patches. Clover’s patch format and exact base checksum have not been established here. Do not use this profile as a base-match certificate.

  1. Open the ROM checker. Select your own GBA input and BPS or UPS patch in the ROM checker. Compare the source and target requirements stored in that patch; a FireRed header alone does not prove the base is right.
  2. Open the ROM patcher. Only continue with a supported patch after the input checks agree. The patcher stops on a mismatch or an already patched input, then checks the complete output before offering a separate file.

A no-RTC requirement does not justify stripping bytes from a save. Do not rename a patch to change its format or ignore a checksum failure.

Before replacing a working game

Keep the working game and an untouched in-game save separately. The FAQ’s version exclusions are not permission to move a save between other versions. Our save comparison shows byte differences, not whether Clover will accept the save.

Compare two local save copies to inspect their sizes and changed byte ranges. This does not convert or repair them.

Read the creator’s save and clock guidance for the stated version boundaries. We have not tested Clover’s patching, saves, battles or device behavior.