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

java.lang.IllegalArgumentException: Unknown meta type #2294

Closed
Yorkforce opened this issue Nov 19, 2017 · 6 comments
Closed

java.lang.IllegalArgumentException: Unknown meta type #2294

Yorkforce opened this issue Nov 19, 2017 · 6 comments

Comments

@Yorkforce
Copy link

We just started having this occur on one of our modpack servers, it's a brand new world and only seems to occur in a certain area of the world. (eg: we were moving from default world spawn to 0,0 coordinates.

Were at a complete loss tbh
Error from bungeecord log:
https://pastebin.com/JcnpHdUk

@md-5
Copy link
Member

md-5 commented Nov 19, 2017

http://wiki.vg/Entity_metadata

There is no metadata with type 14 in vanilla.
Without knowing what the mod is and what data it is adding there is nothing we can do.
Even if we did, really the mod should be using plugin messages to handle custom data rather than changing the vanilla protocol.

@md-5 md-5 closed this as completed Nov 19, 2017
@Yorkforce
Copy link
Author

Yorkforce commented Nov 19, 2017

The actual forge log is this:

[04:27:02] [Netty Epoll Server IO 2/DEBUG] [FML]: Muted NetworkDispatcher exception
io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer
at io.netty.channel.unix.FileDescriptor.readAddress(..)(Unknown Source) ~[FileDescriptor.class:?]

We also got a Unknown meta type 16 error too.

Do you know if this is a mob? Were just trying to narrow it down to find out which mod is causing the problem.
Or could be caused by ViaVersion? (I'm unsure if you're referring to mc version protocol or a protocol in general)

@md-5
Copy link
Member

md-5 commented Nov 19, 2017

No, you need to find the issue - we can only investigate issues that occur with vanilla, craftbukkit, or spigot

@MrCrayfish
Copy link

I know that this was closed a while ago but I recently ran into the issue. The problem lies with adding custom DataSerializers for Entities. I now have reverted to using plain primitives instead of a custom serializer. I disagree though that we are changing Vanilla's protocol because these are my own custom entities with values that I need synced to the client.

@md-5
Copy link
Member

md-5 commented Apr 27, 2018

disagree though that we are changing Vanilla's protocol

custom DataSerializers

How is that NOT changing the protocol?

@MrCrayfish
Copy link

Okay, I take that back :/

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