Have a demo so users can tell how well supported their platform is.
Be clear about the target platform (E.G. Tested on Debian 10.8 + NonFree, Ubuntu 2020.04 etc; also include the minimum supported OpenGL / Vulcan / whatever version etc.)
Document the product execution lifecycle, and how to manually skip steps. (E.G. steam calls X to start the launcher, the launcher calls Y to start the game. These are the arguments each take to modify behavior.)
Have developer level debug checks in the logs. Print to standard error where you're trying to open a log file ("Opening log file: %s\n"), have an example of what a healthy log file should look like. If a native command is missing say so, and if there's a test-platform link to the package page for that platform, as well as the source website. (Eventually historical gamers might need to visit Archive.org to grab the last published version.) Have debug levels to increase verbosity (even if it's just "production" vs "collect crash report") validate every assumption and requirement in the crash report log level. You shouldn't need to ask the user for any additional information other than the log file, because it should all be right there in the log file.
Have a demo so users can tell how well supported their platform is.
Be clear about the target platform (E.G. Tested on Debian 10.8 + NonFree, Ubuntu 2020.04 etc; also include the minimum supported OpenGL / Vulcan / whatever version etc.)
Document the product execution lifecycle, and how to manually skip steps. (E.G. steam calls X to start the launcher, the launcher calls Y to start the game. These are the arguments each take to modify behavior.)
Have developer level debug checks in the logs. Print to standard error where you're trying to open a log file ("Opening log file: %s\n"), have an example of what a healthy log file should look like. If a native command is missing say so, and if there's a test-platform link to the package page for that platform, as well as the source website. (Eventually historical gamers might need to visit Archive.org to grab the last published version.) Have debug levels to increase verbosity (even if it's just "production" vs "collect crash report") validate every assumption and requirement in the crash report log level. You shouldn't need to ask the user for any additional information other than the log file, because it should all be right there in the log file.