-
-
Notifications
You must be signed in to change notification settings - Fork 886
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
Comments
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:
|
Version:false for auto detection. On Sun, Jul 31, 2016, 09:34 Robin Lambertz notifications@github.com wrote:
|
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. |
closed in favor of #449 |
My bot is getting kicked from my 1.10.2 server
Here's my error.
Is minecraft-protocol outdated? Is there some way I can manually change the version sent to the server?
The text was updated successfully, but these errors were encountered: