-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled error everytime i open the game #170
Comments
It seems that the DiscordRPC's Scheme Creator is running the command with the home directory as the working directory, and writing to |
I guess we could create a separate desktop file just for Discord rich presence or maybe add the required MIME type to the main one (but that may not work when osu! is already open and |
I don't think it is possible for an AppImage alone to register MIME and URL scheme without directly modifying user directories. The user will have to install some kind of AppImage desktop integration program to make it possible. If that's the case, I think it should be mentioned somewhere in the game or the installation documentation. This thing make me wonder if AppImage is even a good format for this game. It's fine for portable, run-then-forget applications. But I don't think it's suitable for things that have desktop integrations like MIME and URL scheme (and automatic updates). |
We are not maintaining fifty builds for fifty distros with whatever the distro maintainers decide to apply on top of the base game and then attempting to track whether all of them are playing fair with respect to game integrity. No other platform/OS plays these games. In that light "portable" is the only viable choice for linux. It's appimage or nothing. |
I'm not saying we should package the game for every distros. That is why Flatpak is created to solve that. I said that to make Flatpak to be considered as the main way to distribute on Linux. |
With this new update, every time i open the game i get the following error:
1713010783.runtime.log
The text was updated successfully, but these errors were encountered: