The event archive answers provenance: where did an old crop, egg, pet, gear item, or mutation come from? It does not promise that the source has returned. Grow a Garden updates frequently combine temporary activities with new entities, so inventory and trade listings can outlive the event that introduced them.
Each archive entry should include event name, year, source type, documented content families, start/end evidence when available, and current obtainability status.
Documented 2026 activity examples
Current community event indexes list Garden Games in January 2026, Feed a Pet in January, Buttercup Quest in January, Alien Invasion in February, Community Garden in March, Easter in April, Bizzy Bee in May, and a 4th of July activity in July. These dates and names are Community corroborated historical markers, not complete patch notes.
Later summer and lunar/harvest discussions continue the pattern of rotating crops, pets, eggs, gear, mutations, points, and shops. Exact reward lists require the specific archived event page or update note.
Record provenance
For an old item, trace the original event and acquisition method. Distinguish reward track, merchant, quest, pack, craft, weather, admin grant, and trade. Note whether the source was free, currency-based, premium, or chance-based only when the archived evidence supports it.
Do not use current trade availability as proof of current acquisition. A player can trade an owned historical pet after its egg closes.
Current status labels
Use historical when the original window ended, returning only after a current source confirms a return, current when live now, owned-only when items remain but no source is verified, and unknown when evidence is insufficient.
Avoid “unobtainable forever.” A future rerun can change status. “No current source verified on August 7, 2026” is more accurate.
Verify rewards
Match the exact entity name and variant. Event pets can have similar names or mutated appearances; crops can share families; gear can be reskinned. Record the inventory card rather than relying on a thumbnail.
For a returning event, recheck the live reward pool. A reused event name does not guarantee every old reward returned.
Build an entity history card
When an unfamiliar pet, crop, egg, or gear item appears in a trade, create a compact history card before assigning scarcity. Record the exact inventory name, mutation or variant, first documented event, original source, whether the item itself can be traded, and the newest verified route. Link the dated event entry that supports the origin. If only a screenshot or unsourced value list names the item, mark provenance unresolved.
This process prevents two opposite mistakes: calling an ordinary returning reward permanently unobtainable, or treating an old player-owned specimen as evidence that the event source is open. The current inventory card establishes identity; the archive establishes history; the live game establishes present availability.
Archive use cases
Collectors can identify provenance. Traders can distinguish current supply from historical scarcity. Guide writers can prevent old recipes and timers from entering current pages. Returning players can understand why a pet exists without wasting time at the wrong shop.
Link from an archived entity to the current system page only when the mechanic still applies. Historical facts should not control the current-event guide.
Event archive FAQ
Is this a complete event list?
No. It is a currently documented archive foundation. Community logs are useful but may omit short admin events or phases.
Can I still get an Easter or Bizzy Bee reward?
Only a live return, current trade eligibility, or another verified source can answer for the exact item. The old event page proves origin only.
Are archived prices and recipes still valid?
Treat them as historical. Recheck any current station, shop, or rerun.
Why keep old events?
They explain entity provenance, update history, and availability without polluting current guides with stale claims.