Scope and independence
OSMCoach is an independent fan resource for Online Soccer Manager, a game developed by Gamebasics. It is not affiliated with or endorsed by Gamebasics and does not claim private match-engine access, insider coefficients or guaranteed tactics.
The editorial aim is practical: state the best current starting decision, show the context that can change it and keep evidence limitations visible.
Evidence levels
Confirmed mechanic
An official OSM or Gamebasics source documents the mechanic or option. This does not automatically validate a complete tactic.
Supported guidance
The recommendation is coherent with the formation and has repeat practical or community support, while the private engine formula remains unknown.
Experimental or provisional
The reasoning is plausible but comparable observations are limited. It is published as a testable hypothesis, not a conclusion.
Unknown or theory-based
Available evidence is insufficient. OSMCoach may explain the tactical theory but does not present the claim as reliable engine behaviour.
Confidence describes the support behind a starting point. It never predicts or guarantees the outcome of one match.
How tactical advice is produced
- Define one decision: opponent formation, relative strength, venue, squad constraint or match objective.
- Check whether formation, game plan, line instructions, marking, offside and slider ranges form one coherent system.
- Compare official documentation where it exists, then identifiable community observations and transparent tactical reasoning.
- Reject contradictory combinations and avoid upgrading anecdotal screenshots into universal rules.
- Publish a recommendation, evidence level, confidence level, risks and conditions that should change the plan.
Exact slider values are reference points inside a range. They are not presented as discovered engine breakpoints.
Community testing and match evidence
The current match-note form validates a versioned record and stores it only in the visitor’s browser. No centralized submission endpoint is enabled, no account details are requested and no community win rate is displayed.
A future opt-in evidence system must validate records server-side, control duplicates and spam, preserve tactic versions, document exclusions and wait for a meaningful comparable sample before publishing any aggregate. Observational match records would still not prove causality.
Review dates and freshness
A deployment alone does not change a page’s review date. dateModified and the visible updated date change only when recommendations, evidence, page structure or other meaningful editorial content changes.
Time-sensitive club objectives, player targets, prices and game behaviour should be verified in the current OSM database. Static freshness labels are not used as a substitute for real review.
Corrections and conflicting evidence
A disagreement is not resolved by selecting the most confident claim. OSMCoach checks whether the sources describe the same season, formation, strength tier and game context. If conflict remains, the lower defensible evidence label is retained and the uncertainty is stated.
Corrections can be submitted through the public project contact described on the About page. Useful reports identify the URL, disputed statement, source or match context and the proposed correction.
Source priority
Sources are prioritized in this order: official OSM and Gamebasics material; statements from identifiable OSM staff or moderators; reproducible OSMCoach observations; repeated community evidence; and finally formation logic or an explicitly labelled hypothesis.
See the source audit, evidence and confidence guide and engine rules and myths review.
Known unknowns
OSMCoach does not know the private match-engine formula, universal formation multipliers, exact slider response curves or guaranteed transfer-sale probabilities. It cannot infer causality from one result or separate tactics from squad quality and variance without comparable evidence.