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

Lich error code 0 #42

Open
halprind opened this issue Feb 14, 2018 · 3 comments
Open

Lich error code 0 #42

halprind opened this issue Feb 14, 2018 · 3 comments

Comments

@halprind
Copy link

--- Open "ruby /Users/*******/Dropbox/lich/lich.rbw --dragonrealms --frostbite -g dr.simutronics.net:11024"

--- Lich process exited with code 0

Connecting ...

  • Unable to connect to server. Please check your internet connection and try again later. [3:39 pm]

Thoughts on what this could mean?

@matoom
Copy link
Owner

matoom commented Feb 15, 2018

In the context of this message code 0 means that the program (lich) exited without any errors. That means it did not explicitly crash but doesn't mean there were no errors in the program that caused it to exit prematurely. In short the exit code here doesn't help much.

ruby /Users/*******/Dropbox/lich/lich.rbw --dragonrealms --frostbite -g dr.simutronics.net:11024

This was the exact command that was executed in your terminal to run Lich. In my experience Lich doesn't seem to flush the pipes before it gets stuck in the connect loop. There could have been errors printed in the console but not displayed in Frostbite.

One thing you could do is to run the same exact command in your terminal and see what happens.

Another thing to note is that the "--frostbite" argument is only present in the rcuhljr fork of Lich, other versions probably won't run.

https://github.com/rcuhljr/dr-lich

@Dartellum
Copy link

This condition also occurs when trying to connect to the game after it crashes. The way I have found to resolve it is to close Frostbite completely, make sure it is not hung as a process, and launch again. This usually resolves it.

@matoom
Copy link
Owner

matoom commented Sep 29, 2018

Yep, it's likely the background process that runs lich will still be open after a client crash.

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