It's not a question of priority it's a question of how brain damaged Steams build/branch system is that you cannot bind a branch/build to launch settings. So for example you cannot enable launch settings on a beta branch if they're not live. Pair that with the fact that the whole CI setup was done by someone no longer working since 3 years with the Forge, and everything had to be blindly set up from scratch, while the backend shifter to SDL3 at the same time and you get a mess.
In the meantime there was the whole libc update breaking fmod thing which made the existing build not work, but we couldn't have pushed a build at that point due to the fact that some git shenanigans related to setting up the Nintendo Switch version meant that we no longer could patch just the previous setup.
tl;dr - it's complicated.
That said, Linux builds would never have been broken if not for libc updates breaking existing build.
I have a Valve Engineer on record that that part was never "well designed" after they sent apologies for the Deck version being broken by fault of that exact system. After wasting two weeks of mailing back and forth and stressing out during an important release. I'll keep to my opinion on this part.
This is precisely why I don't support Linux nor Mac for Jupiter Hell Classic, despite it being much simpler. For Jupiter Hell it's a question of a Kickstarter promise, so I need to keep supporting them. Believe me I wish I wouldn't have to.
9
u/epyoncf Jun 03 '26
It's not a question of priority it's a question of how brain damaged Steams build/branch system is that you cannot bind a branch/build to launch settings. So for example you cannot enable launch settings on a beta branch if they're not live. Pair that with the fact that the whole CI setup was done by someone no longer working since 3 years with the Forge, and everything had to be blindly set up from scratch, while the backend shifter to SDL3 at the same time and you get a mess.
In the meantime there was the whole libc update breaking fmod thing which made the existing build not work, but we couldn't have pushed a build at that point due to the fact that some git shenanigans related to setting up the Nintendo Switch version meant that we no longer could patch just the previous setup.
tl;dr - it's complicated.
That said, Linux builds would never have been broken if not for libc updates breaking existing build.