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

Bot getting kicked for outdated client? #443

Closed
safazi opened this issue Jul 31, 2016 · 5 comments
Closed

Bot getting kicked for outdated client? #443

safazi opened this issue Jul 31, 2016 · 5 comments

Comments

@safazi
Copy link
Contributor

safazi commented Jul 31, 2016

My bot is getting kicked from my 1.10.2 server

Here's my error.

I got kicked for {"text":"Outdated client! Please use 1.10.2"}

Is minecraft-protocol outdated? Is there some way I can manually change the version sent to the server?

@roblabla
Copy link
Member

You can try to specify the version in the constructor :

var mc = require('minecraft-protocol');
mc.createClient({
  version: '1.10',
  // ... Other options
});

Though I think it's supposed to find the version automatically.

On Jul 31, 2016 8:05 AM, "safazi" notifications@github.com wrote:

My bot is getting kicked. from my 1.10.2 server

Here's my error.

I got kicked for {"text":"Outdated client! Please use 1.10.2"}

Is minecraft-protocol outdated? Is there some way I can manually change
the version sent to the server?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#443, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABBRBtEyfx1H6tH8pXlIJeOVptYCQjM_ks5qbDsVgaJpZM4JY96i
.

@rom1504
Copy link
Member

rom1504 commented Jul 31, 2016

Version:false for auto detection.
But that's for node-minecraft-protocol
Mineflayer doesn't quite support anything but 1.8 yet.
Feel free to contribute in supporting 1.10 though !

On Sun, Jul 31, 2016, 09:34 Robin Lambertz notifications@github.com wrote:

You can try to specify the version in the constructor :

var mc = require('minecraft-protocol');
mc.createClient({
version: '1.10',
// ... Other options
});

Though I think it's supposed to find the version automatically.

On Jul 31, 2016 8:05 AM, "safazi" notifications@github.com wrote:

My bot is getting kicked. from my 1.10.2 server

Here's my error.

I got kicked for {"text":"Outdated client! Please use 1.10.2"}

Is minecraft-protocol outdated? Is there some way I can manually change
the version sent to the server?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#443, or mute the
thread
<
https://github.com/notifications/unsubscribe-auth/ABBRBtEyfx1H6tH8pXlIJeOVptYCQjM_ks5qbDsVgaJpZM4JY96i

.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#443 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACPN_nS1Ymi6E41FlJ-x8NOvIWCSqw1iks5qbE_9gaJpZM4JY96i
.

@growlf
Copy link

growlf commented Sep 10, 2016

Hi Rom1504! What areas need help to get MF to 1.10? Is there a list we can poke at and see what can be done? Or is it a chaos cloud that we cant really attack in small slices? I see that MCP is already supporting 1.10, so I suspect you have a clear idea what needs doing already.

@lachlandcp
Copy link

@growlf The biggest stepping stone is to get the chunk parser updated to support 1.9+ (#417)

@rom1504 rom1504 mentioned this issue Sep 12, 2016
@rom1504
Copy link
Member

rom1504 commented Sep 12, 2016

closed in favor of #449

@rom1504 rom1504 closed this as completed Sep 12, 2016
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

5 participants