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

I got Bravo working in OSX, but unable to connect to the server. #448

Open
ghost opened this issue Feb 22, 2014 · 1 comment
Open

I got Bravo working in OSX, but unable to connect to the server. #448

ghost opened this issue Feb 22, 2014 · 1 comment

Comments

@ghost
Copy link

ghost commented Feb 22, 2014

So, I got Bravo to work on OSX super-easily.

  1. Download everything from github
  2. cd to the installation folder (which was bravo-master on my desktop, from a zip file)
  3. Run "sudo python setup.py install"
  4. Run "twistd -n bravo"
    And then it created a world and all that jazz. However, when I try to connect to the server, it says "logging in" and then I get a connection timeout.
    What the console says when I try to connect with localhost:

2014-02-22 12:09:53-0800 [bravo.beta.factory.BravoFactory] Starting connection for IPv4Address(TCP, '127.0.0.1', 52230)
2014-02-22 12:09:53-0800 [bravo.beta.factory.BravoFactory] Registered entity <bravo.beta.protocol.BravoProtocol object at 0x1994b10>
2014-02-22 12:09:53-0800 [bravo.beta.factory.BravoFactory] Registering client hooks...
2014-02-22 12:09:53-0800 [bravo.beta.factory.BravoFactory] Registering policies...
2014-02-22 12:09:53-0800 [bravo.beta.factory.BravoFactory] Registered client plugin hooks!
2014-02-22 12:10:23-0800 [-] Error: 'Connection timed out'

However, I can go to the web app just fine (I connected to it with localhost:8080).

Why does this happen?

@edunham
Copy link
Member

edunham commented Mar 12, 2014

This happens because you're probably using the latest Minecraft client, and Bravo most recently worked somwehere around 1.4 (from the changelog at bravo 2.0: "The 1.4.x protocol is now supported, without server-side encryption.")

In the Minecraft launcher, go to "edit profile" in the lower left, then in the "use version" dropdown pick 1.4.2. I make no promises as to whether this will fix anything, but it might help.

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

1 participant