
Movement help for night routes and stealing pressure.
Pet roles, abilities, verification state, and asset slots for official game images.

Movement help for night routes and stealing pressure.

Useful garden protection role in early defense setups.

Growth-focused pet for basic farming progression.
Support role tracked while GAG2 pet data settles.
Pets matter because they can change farming, movement, defense, stealing pressure, or support decisions. A useful pets page should not only list names. It should explain what role each pet appears to serve, how confident that role is, and whether the information is confirmed or still community reported.
Each card shows a pet image, name, rarity, role, ability note, and source status. The first tracked pets are Bunny, Bee, Deer, and Frog. Bunny is treated as a stealing or movement-related role, Bee as defense, Deer as growth, and Frog as support while the data settles. These labels help players scan the list, but they are not final tier rankings.
The images are local identification assets. They help players recognize the pet quickly and compare it with the game object they remember. Because the assets are temporary P2 Fandom-sourced images, the page keeps the fan-made boundary visible and does not use them as official branding.
A role tells the player what problem the pet may help solve. A rank says one pet is better than another. This MVP does not publish a hard pet tier list because the abilities, values, and balance context still need stronger verification. That is intentional. A weak role note with a clear status is safer than a confident tier list built on unstable information.
Growth pets belong with farming and calculator decisions. Defense pets belong with night stealing and AFK risk. Stealing pets belong with route pressure and public server behavior. Support pets may affect several systems at once, so they need clearer ability notes before they can be recommended.
A confirmed pet entry should eventually include source notes, ability text, trigger conditions, cooldowns or limits if relevant, and a last verified date. If a pet has a role but no confirmed mechanics, the page should say community reported or needs verification. That keeps users from treating speculation as a recommendation.
The pet page should also connect to other tools. If a pet affects growth, it should link naturally to calculator or crop planning. If it affects defense, it should link to the defense guide. If it affects stealing pressure, it should include server-risk context. That is how the wiki layer becomes useful instead of just decorative.
A pet tier list should not be published just because pet names are popular. It needs enough mechanics to explain why one pet is better for a specific job. A growth pet may be strong for farming but weak for public server defense. A defense pet may be valuable for AFK safety but less useful when a player is actively managing the garden.
This page is therefore better as a role database first. Once each pet has verified ability details, the site can add scenario rankings such as best early growth pet, best defense pet, or best support pet. Those rankings would be stronger because they answer a concrete player task instead of pretending one universal pet order fits every situation.
Not yet. The page tracks roles and early ability notes, not a final best-pet ranking. A tier list should wait for stronger data.
Frog was not part of the first approved asset batch. It stays as a placeholder rather than using an untracked or mismatched image.
Choose based on the problem you are solving: growth, defense, stealing pressure, or support. Then check whether that role is confirmed.
Yes, but only after each pet has enough unique information. Otherwise separate pages would become thin programmatic entries.