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

Malmo's internal Minecraft client/server message system can't send more than 64k per message #52

Closed
DaveyBiggers opened this issue Jun 6, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@DaveyBiggers
Copy link
Member

MalmoMessage.toBytes() uses ByteBufOutputStream.writeUTF() to encode message data.
From the docs:

First, the total number of bytes needed to represent all the characters of s is calculated. If this number is larger than 65535, then a UTFDataFormatException is thrown.

Alas, the limit of 65535 can easily be surpassed by requesting a large grid observation (21x21x21 will do it, depending on the blocktypes of the terrain). The effect in this case is that the observations never reach the agent.

@DaveyBiggers DaveyBiggers added the P2 label Jun 6, 2016
@DaveyBiggers DaveyBiggers self-assigned this Jun 6, 2016
@katja-hofmann katja-hofmann modified the milestone: Alpaca Jun 7, 2016
DaveyBiggers added a commit that referenced this issue Jun 8, 2016
Added ability to write strings > than 64k in message data (issue #52)
@DaveyBiggers
Copy link
Member Author

Fixed in 8c0c47f
We now use four bytes to represent the length of the string, rather than two.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants