Pet auto feeding
How hunger thresholds, fruit selection and confirmation protect feeding behavior.
Enable Auto Feed deliberately#
Open Pets and enable Auto Feed. The worker considers active pets with known hunger and feeds the hungriest eligible pet. It starts below the configured threshold and continues toward the stop threshold.
| Setting | Default | Meaning |
|---|---|---|
| Start feeding below (%) | 25 | Begin a feeding cycle when hunger falls below this percentage. |
| Stop feeding at (%) | 80 | End the cycle once hunger reaches the target. |
| Max fruit value | 0 | 0 means no price cap. A positive cap limits eligible fruit value. |
| Auto Feed | Off | No feeding until enabled. |
How a fruit is selected#
The worker compares usable inventory fruit and mature fruit on your own plot, selecting the cheapest eligible candidate. Favorites and locked/waxed plot fruit are protected. Claimed, queued or invalidly priced candidates are excluded.
Own-plot fruit is collected directly through the existing collection path. The character does not teleport to the fruit. The collected item is equipped and then offered to the pet.
Confirmed feeds and failures#
A confirmed feed requires server acceptance, consumption of the inventory item and an observed hunger increase. Replication delay can leave an accepted feed uncounted; the counter does not invent confirmation. Pending responses prevent a second concurrent feed, and failures pause retries for that pet.
The worker shares the existing automation lock. Disabling the feature or stopping the client invalidates pending continuations. An already sent server request cannot be recalled.
Verification scope#
The public source reports controlled desktop feeding cycles and local mock checks. That historical evidence is separate from this documentation build. If hunger or inventory data is missing in your runtime, stop feeding and inspect the status rather than assuming success.