prismarine-world
prismarine-world copied to clipboard
PrismarineJS
What should happen for y>256 or y<0
Maybe return air for getters but return an error for setters ?
Maybe this should happen in prismarine-chunk and we just shouldn't do modulus 256 there https://github.com/PrismarineJS/prismarine-world/blob/master/src/world.js#L11
That's not possible with Minecraft protocol AFAIK, the chunk packet only support up to 16 sections.
hum, i know with the java server and client, i was able to make 512 build limits
@rom1504 vanilla server has an option to make a higher build limit. 256 is just the default IIRC.
Hmm really ? I don't understand how would http://wiki.vg/Protocol#Chunk_Data work then, it takes the bitmap as an unsigned short, so 2 byte, 16bits, 16 sections (=256 max) Would they change the datatype used for the bitmap automatically ?
Need to experiment about that with the vanilla server + nmp proxy to see what happens
(edit: this issue is related to https://github.com/mhsjlw/flying-squid/issues/119#issuecomment-159319424 )
"always sends it or never sends it" send what ? the bitmap ? it's not optional
Maybe the solution they use is setting "Ground-Up Continuous" to false. ("This is true if the packet represents all sections in this vertical column, where the Primary Bit Mask specifies exactly which sections are included, and which are air")
The content. Not the bitmap. Bitmap defines whether the content is sent or not, so my guess is, if bitmap is too small, the content that couldn't fit in bitmap is either always sent, or never sent. We'd need ot check.
15:42 <+Thinkofname> you can't go bigger than 256 15:48 < rom1504> so server property max-build-height does nothing ? 15:50 < Fenhl> it does nothing when you set it above 256, yes
Not sure who to believe, I guess it needs testing
Uh-oh, looks like 256 isn't enough now .. and the height is hard written, maybe try to get it from bot.game.height, and same for bot.game.minY
