Sources, methodology and corrections
The aim is to make a draft decision understandable and repeatable. A useful result needs its starting assumptions as well as its final player list.
What the simulator represents
The draft room combines a selected player pool, a starting selection order, pick ownership, draft-point values and rule settings. Selecting a player or completing a trade changes that scenario. It does not change an official draft order, record a real transaction or reveal a club's intentions.
Different draft classes and custom rules can produce different behaviour. When comparing two results, record the class, ladder assumptions, ownership, enabled rules and any trades made before the first selection. The app's current setup is the place to inspect its working data; it is not a substitute for an official AFL register.
Rules and calculations
The AFL's 2026 player-movement announcement and its practical bidding explainer provide the official context linked by these guides. Public examples use the simulator's current points table and explicitly stated assumptions. The app's displayed match plan is the result to inspect when live pick numbers, rounding or settings change.
A points total explains part of a draft decision. It does not measure a player's complete value, guarantee a trade is permitted, or account for every contract, list or club strategy constraint. Custom scenarios can deliberately depart from the real competition's settings.
Player information and comparisons
Player profiles can contain measurements, reported testing, draft ranges and descriptive scouting opinions. Treat those categories separately. A range is an assessment; a comparison is a stylistic description. Neither is an official prediction. If a measurement or a reported result is uncertain, rely on the supporting source and any qualification displayed in the profile.
These guides do not claim new interviews, exclusive scouting access, or private club information. The examples use hypothetical clubs or clearly labelled interface test scenarios. They are educational exercises, not reported events.
How this guide section was prepared
The initial guides were prepared with AI assistance from the simulator's implementation, existing in-app instructions and the official sources linked on each relevant page. They explain workflows and assumptions; they are not a claim that Adam personally observed or reported the examples. Dates indicate when a page was published or substantively changed, not a promise that every underlying player record changed on that date.
Automated news is separate
The news wire collects feed metadata and generates short summaries with links to the source publisher. It is automated and is not individually reviewed before every update. Its page carries no Google ad code. Attribution lets readers check the original story; it does not turn a summary into independently verified reporting.
Corrections and questions
Email sotaramyt@gmail.com with the page or app class, the item that appears wrong, the expected result, and a supporting source if available. For an app issue, include the pick, club, settings and steps required to reproduce it. Please do not include passwords or sensitive personal information.
A correction can concern the wording of a guide, an outdated player detail, a source attribution or the simulator's behaviour. A difference between a custom scenario and official settings should first be checked against the scenario's rule configuration.