What should I record when I keep changing an FPL decision?

Xiao K · FFTQL developer ·

Save each important version's time, triggering evidence and reason, then check whether the revisions responded to genuine new information.

FFTQL news in English

Review the chain of changes

Place the key versions in order and link their triggers. Identify changes supported by a new fact and those prompted by rereading the same opinion. This can reveal whether your process needs better evidence checks, clearer objectives or a defined point for reassessment.

Create a practical trigger for next time. For example, revisit the plan when a specific unresolved fact is confirmed, rather than reopening every alternative whenever the feed repeats the story.

Practical checks

  1. Retain the important versions and source triggers.
  2. Review whether each revision addressed a material information change.

Context and sources

These are my suggested record-keeping methods. FFTQL can help you find reports and public Draft results. Use original articles and the official game to verify events, operations and settled scores before drawing conclusions.

Sources and useful pages