Product community
Championship SoccerRead public discussions or exchange ideas with approved users and the product team.
Official guide: reporting bugs and suggestions
Started by adrastea GmbH & Co. KG on 22 août 2026, 20:55
Showing 1–1 of 1 posts
Please use the Championship Soccer tracker for bugs and concrete suggestions so they remain searchable and can be followed through to a decision. Sign-in may be requested:
https://www.playtesting.de/en/issues/new?game=championship-soccer
Before submitting
• Update to the newest x64 build unless the report is specifically about an older release.
• Check whether the issue already exists.
• If practical, check whether it also occurs with the original football world. Mod-specific problems are still useful when the package and version are named.
• Keep one distinct problem or suggestion per report.
Include
• the complete build number and whether it is the original x86 or current x64 branch;
• Windows version, device and graphics adapter;
• keyboard, mouse or gamepad and the selected control layout;
• career or match mode and the custom football world or datapack, if any;
• exact steps that reproduce the issue;
• expected and actual behaviour;
• a save, replay, screenshot, generated replay video or diagnostic file when available.
For an idea, describe the concrete situation, who benefits and what outcome you want. Do not post passwords, activation codes, private personal data or exploitable security details in a public discussion. Use the product page’s reporting route for sensitive matters.
If a browser or antivirus warning appears, do not simply bypass it. Name the exact warning and compare the complete SHA-256 value with the official download entry.
https://www.playtesting.de/en/issues/new?game=championship-soccer
Before submitting
• Update to the newest x64 build unless the report is specifically about an older release.
• Check whether the issue already exists.
• If practical, check whether it also occurs with the original football world. Mod-specific problems are still useful when the package and version are named.
• Keep one distinct problem or suggestion per report.
Include
• the complete build number and whether it is the original x86 or current x64 branch;
• Windows version, device and graphics adapter;
• keyboard, mouse or gamepad and the selected control layout;
• career or match mode and the custom football world or datapack, if any;
• exact steps that reproduce the issue;
• expected and actual behaviour;
• a save, replay, screenshot, generated replay video or diagnostic file when available.
For an idea, describe the concrete situation, who benefits and what outcome you want. Do not post passwords, activation codes, private personal data or exploitable security details in a public discussion. Use the product page’s reporting route for sensitive matters.
If a browser or antivirus warning appears, do not simply bypass it. Name the exact warning and compare the complete SHA-256 value with the official download entry.