This is part of a larger ongoing issue where the way the game disallows players from placing blocks inside of themselves is by immediately deleting the block. This no longer works with the new terrain system, and it will be replaced by simply preventing the block from being placed.

it asks for clang

This seems to be caused by the code that darkens the bottoms of block textures. When it is removed, their undersides look normal (too bright of course, but normal).

However this only happens on stone and water. Another thing of note is that the "streaking" noise no longer applies on the bottoms of these blocks as it should.

When hovering over a block, only the half of the white indicator outline that is to the right of the mouse shows up.

Player coordinates are offset by 64. I believe this behavior was present in the original java version, to offset the broken rendering in negatives so that it did not appear in the world. The broken rendering can be mitigated by increasing this offset.

However, the player struct currently stores this these offset values. It should not do this, instead the values should be offset when rendering is taking place.

The player struct should store the real values because more things need the real values than the offset ones.

Significant lack of trees in most chunks. I feel like this has to do with the way it checks whether or not to generate structures based on the heightmap.

Anything past -64 on any axis becomes distorted. Issue is independent of whether gameLoop uses doubles or floats. May have something to do with modulo.

This does not pose a problem yet unless the code is edited to loop the world, but it will affect the game once infinite terrain is added.

Occasionally when creating a world the player spawns in stone, and the player position seems to reset after restarting the program and reopening the world. Needs further investigation.

Perlin noise function generates jittery and exaggerated terrain in negative coordinate chunks on the x and z axis.

When colliding with a block, the player stops moving entirely. The player is also able to stick to walls instead of falling down.

When pausing while holding down movement controls, the player continues to move.

At some point it would be a good idea to have all raycasting functionality run in a compute shader. Creating this issue to remind myself.