+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Development (https://forum.cuberite.org/forum-13.html)
+--- Thread: ChunkCache question (/thread-1624.html)
RE: ChunkCache question - sphinxc0re - 10-18-2014
I did
(10-18-2014, 07:45 PM)SphinxC0re Wrote:Code:[11:59:49] Saved obfuscated chunk 36#-144 to drive!
[11:59:49] ReadBlockArea: MaxRelX more than chunk width, adjusting to chunk width
[11:59:49] ReadBlockArea: MaxRelZ more than chunk width, adjusting to chunk width
RE: ChunkCache question - NiLSPACE - 10-18-2014
Hmm. It might be a problem in the server code.
@xoft the C++ code for adjusting the coordinates uses >=. Shouldn't that be >?
RE: ChunkCache question - sphinxc0re - 10-18-2014
I thought so, too.
It's good though, that this little bug is now present
RE: ChunkCache question - NiLSPACE - 10-18-2014
Hang on
There is a possibility that I'm wrong.
RE: ChunkCache question - xoft - 10-18-2014
I think the code's right, the coords range from 0 to 15, which is 16 blocks total.
EDIT: wait, you might be right, because the coords are first adjusted for inclusion by adding 1 to them.
RE: ChunkCache question - sphinxc0re - 10-18-2014
I have another problem now. How do I work around the chunk thing? Also why does my algorithm generate these gaps?
RE: ChunkCache question - NiLSPACE - 10-18-2014
It might create those gaps because it's on the edge of a chunk?
RE: ChunkCache question - sphinxc0re - 10-18-2014
How can I fix this?
RE: ChunkCache question - sphinxc0re - 10-20-2014
(10-18-2014, 10:50 PM)xoft Wrote: I think the code's right, the coords range from 0 to 15, which is 16 blocks total.
EDIT: wait, you might be right, because the coords are first adjusted for inclusion by adding 1 to them.
Will this be fixed soon?
RE: ChunkCache question - xoft - 10-20-2014
Report an issue on Github for it so that it doesn't get forgotten.