Skip to content
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

"It seems that Minecraft has crashed Minecraft has exited with a non-zero error code." #288

Closed
M1L46R05 opened this issue Apr 25, 2020 · 3 comments

Comments

@M1L46R05
Copy link

M1L46R05 commented Apr 25, 2020

Unknown argument: -s
Process exited with unexpected exit code: 1

http://prnt.sc/s5kv3c

@M1L46R05 M1L46R05 changed the title "It seems that Minecraft has crashed" "It seems that Minecraft has crashed Minecraft has exited with a non-zero error code." Apr 25, 2020
@ChristopherHX
Copy link
Member

You downloaded the wrong appimage

Do not use ng.appimage with the description

THIS IS A TEST RELEASE OF THE NG BRANCH CURRENTLY NO SUPPORT FOR THIS APPIMAGE

in the description

@ScaryPit92
Copy link

ScaryPit92 commented Apr 25, 2020

calm down bro
okay , so how we can play minecraft bedrock edition without this appimage ? @ChristopherHX

@ChristopherHX
Copy link
Member

Never mind, this is now fixed in ng.
Pixelscale was ignored in my fork (kept this cli switch) and removed in ng (without my knowledge).
The mcpelauncher-ui-qt@ng got updated to fix this issue. (The -s switch will not be back anytime soon)

My stable AppImage can be found here https://github.com/ChristopherHX/linux-packaging-scripts/releases/tag/appimage

Sorry I have confused a lot of peoply by providing the stable, behind the experimental appimage.
I know everyone may linked to this download page, saw the first and thought this launcher is still a Test Release and no stable would exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants