seth

imo #1728 is enough for situations like this although it is sorta comparable to (q)fapi, we aren't dealing with a fork here that's known to have wide compatibility. sinytra still...

this issue seems to be resolved now, but if services outages are that common i can see the problem here. remember [pacstall](https://prismlauncher.org/download/linux/#installing-with-pacstall) is also another option though - but as...

> Just a personal idea, but I don't think it'd be a bad idea to still publish .deb files as part of releases. If you're doing it as part of...

msixbundle is done! https://github.com/PrismLauncher/PrismLauncher/actions/runs/5233072078

with the appinstaller (mostly) completed the package *should* be able to auto update now using the same msixbundle created previously. `prismUpdate.AppInstaller` should be the file distributed to users, as it...

> (totally not because I use ltsc 2019 on some PCs) i might be wrong, but i'm pretty sure mainline support for ltsc 2019 this year no? i think it...

> TIL we're in 2029 (https://learn.microsoft.com/en-us/lifecycle/products/windows-10-enterprise-ltsc-2019) hey i did say mainline ...but man, off by a year :waaa:

i've found that using the `packagedClassicApp` runtime behavior still allows prism to work, and thankfully that allows us to use the older (but not deprecated) `EntryPoint` specification over `uap10:RuntimeBehavior`. this...

> this is bundling the filelink exe too? frankly I don't understand how its' controlling what get packages at all, I only see one reference to the main exe, no...

the minimum supported version of windows for this is now windows 10 1809/ltsc 2019. vc++2022 has also been added as a dependency, and should be installed along with the package...