AFK farming: test a connected session before leaving it

Test what continues without your input

Start with a short connected session and observe what happens without touching the controls. The documented loop supports training, clone egg runs and pet income, but it does not establish an offline-earnings formula or guarantee that every hatch and replacement continues unattended.^↗

AFK is often used loosely to describe both standing still in a server and leaving the experience entirely. Those are different states. Write down which one you tested. A video showing a player training while a clone runs is not evidence that cash continues to accrue after disconnection.

Prepare a run you can evaluate

1. Choose a target that has already returned an egg in your current setup.
2. Check the active training state and note speed, pets and current cash.
3. Inspect the portal, active clones and visible counters.
4. Observe a short interval without purchases or reward claims.
5. On return, check cash, speed, delivered eggs and any ready-hatch prompt separately.

Count unfinished work as unfinished. Eggs delivered during an interval may still need a timer or interaction before adding a pet. A rising wallet can come from pets already earning, even if the egg pipeline stops. Measure both outputs before deciding the whole system is running by itself.

Estimate only from an observed window

For example, an illustrative wallet moves from 20,000 to 26,000 over three minutes without spending or rewards. That interval averages 2,000 per minute. Projecting another 30 minutes at the same rate gives 60,000 additional cash only if the same conditions persist. A boost ending or connection dropping breaks that assumption.

Check a temporary timer before leaving. A boosted first minute should not be multiplied across the entire evening. If your purpose is funding a purchase, use a conservative ordinary rate after expiry, then check the actual wallet when you return.

Claims about infinite clones can hide several different meanings: repeated replacements, a growing active capacity or an exploit. The reviewed menu distinguishes clone count from summoning speed. Repeated summoning is not evidence of unlimited simultaneous clones, and this guide does not supply macros, exploit scripts or ways to bypass a platform idle limit.

If you choose to test reconnect behavior, keep it separate from the connected interval. Record the last balance, elapsed absence and returned balance, plus any explicit offline-reward notice. Without that notice or a controlled comparison, leave the reason for any change unresolved rather than publishing a passive-income formula.

Inspect the controls that can limit the loop

Keep a useful record

Use the short worksheet for this decision. Fill only the fields you can read or measure; leave an uncertain result marked unknown. A second observation is useful only when you can compare the same setup. Keep the date with your readings so a later balance change does not silently turn an old result into a current rule.

Audit a connected idle interval with a cash ledger

Added 20 October 2026. The procedure below is our editorial planning method; any numerical example is hypothetical.

Also note whether you stayed connected, the contributing pets, the target, egg queue and any boost expiry. Stop the interval at a disconnect. This method estimates a connected session; it does not establish offline rewards or recommend bypassing idle controls.