ChunkCache question

[sphinxc0re]

I did

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

[NiLSPACE]

Hmm. It might be a problem in the server code.

@xoft the C++ code for adjusting the coordinates uses >=. Shouldn't that be >?

[sphinxc0re]

I thought so, too. It's good though, that this little bug is now present

[NiLSPACE]

Hang on There is a possibility that I'm wrong.

[xoft]

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.

[sphinxc0re]

I have another problem now. How do I work around the chunk thing? Also why does my algorithm generate these gaps?

[NiLSPACE]

It might create those gaps because it's on the edge of a chunk?

[sphinxc0re]

How can I fix this?

[sphinxc0re]

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?

[xoft]

Report an issue on Github for it so that it doesn't get forgotten.