Use a controlled sample
Choose a fixed duration, avoid changing upgrades mid-run, and note any event or server condition. The goal is a personal rate, not a universal promise.
Define the stop condition before repeating.
How to Plan Appeal Farming
Run a one-minute sample in your current server, record Appeal gained and actions completed, then enter those values in the planner. Retest after any hammer or update change.
+1 Mog Evolution Appeal farm: run a one-minute observation and record the displayed rate
Keep Appeal per action and actions per minute separate, then use those values in the planner.
Choose the target
Separate farming lanes by outcome
A farm needs a measurement and a stop rule.
Separate gain from pace
Appeal per action and actions per minute are different inputs. Either can change, so record both instead of relying on total gain alone.
Define the stop condition before repeating.
Retest decisions
After a hammer or other visible change, repeat the same sample. Compare net Appeal per minute and keep the result dated.
Define the stop condition before repeating.
Repeatable loop
Run the session in order
- 1
1. Record the start
Write down current Appeal and the exact server/session context.
- 2
2. Count one minute
Perform the same Appeal action for sixty seconds and count completed actions.
- 3
3. Record the result
Subtract starting Appeal from ending Appeal, then keep gain, action count, and time as separate values.
- 4
4. Plan the next goal
Use the Appeal planner for remaining actions and estimated time; recalculate after a change.
Stop rules
Leave a bad farming loop
Copying +1 or +999 from art
Promotional overlays do not prove live per-action rates.
Mixing upgrades mid-sample
A changed hammer invalidates a before-and-after comparison.
Assuming an event bonus
An event name and time do not establish a bonus, command, or reward.
Appeal Planner
Estimate actions and time.
Session Estimator
Compare two measured rates.
Appeal Wiki
Review the confirmed relationship.