In the end I think I’ll try to make builds for all OSes and have testers for each platform, and estimate the viability of the builds from the amount of bugs they give me back.
Don’t forget to consider the possibility that getting more bug reports from Linux users doesn’t necessarily mean the Linux version is more buggy, but instead that Linux users may be better at finding bugs or more willing to report them.
Closed-source games should be packaged including their dependencies (e.g. like an AppImage or whatever) rather than relying on OS-provided shared libraries.
Sigh… this is exactly the sort of developer decision people were worried about when Proton first came out, and why some Linux users were opposed to it. Obviously in retrospect the benefits of Proton have been worth it, but those folks wouldn’t be wrong to say “I told you so.”
My take on it is that if you’re not developing Xbox-first (which would imply being forced into DirectX etc.) you should pick libraries that give you cross-platform compatibility “for free” (I know it’s not that simple, but you know what I mean) to begin with. It has to be part of the plan from the beginning (and integrated into your build/test pipeline, etc.); writing the whole game for Windows first and then trying to add Linux support after the fact is a fool’s errand.
Worst case scenario, you could hook your LEDs to an Arduino running WLED instead of to the motherboard headers directly, then run something like Home Assistant, xLights, or Vixen to automate them or choreograph them to music. 🤪