flewkey/cuberite-2a
1
0
Fork 0
Code Releases Activity

Updated comments for slabs

Browse Source
This commit is contained in:
Tiger Wang 2013-12-06 19:22:25 +00:00
parent ee4d57a076
commit 57b8b38511
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/ClientHandle.cpp
View File

@ -685,12 +685,10 @@ void cClientHandle::HandleBlockDigStarted(int a_BlockX, int a_BlockY, int a_Bloc
int pX = a_BlockX; int pX = a_BlockX;
int pY = a_BlockY; int pY = a_BlockY;
int pZ = a_BlockZ; int pZ = a_BlockZ;
AddFaceDirection(pX, pY, pZ, a_BlockFace);
AddFaceDirection(pX, pY, pZ, a_BlockFace); // Get the block in front of the clicked coordinates (m_bInverse defaulted to false)
Handler = cBlockHandler::GetBlockHandler(World->GetBlock(pX, pY, pZ)); Handler = cBlockHandler::GetBlockHandler(World->GetBlock(pX, pY, pZ));
// 2013_01_05 _X: This looks weird
// Why do we ask the block "behind" the one being clicked if it is clicked through? Shouldn't we ask the primary block instead?
if (Handler->IsClickedThrough()) if (Handler->IsClickedThrough())
{ {
Handler->OnDigging(World, m_Player, pX, pY, pZ); Handler->OnDigging(World, m_Player, pX, pY, pZ);
@ -886,7 +884,10 @@ void cClientHandle::HandlePlaceBlock(int a_BlockX, int a_BlockY, int a_BlockZ, c
) )
) )
{ {
// Coordinates at CLICKED block, don't move them anywhere // Coordinates at clicked block, which was an eligible slab, and either top or bottom faces were clicked
// If clicked top face and slab occupies the top voxel, we want a slab to be placed above it (therefore increment Y)
// Else if clicked bottom face and slab occupies the bottom voxel, decrement Y for the same reason
// Don't touch coordinates if anything else because a dblslab opportunity is present
if((ClickedBlockMeta & 0x08) && (a_BlockFace == BLOCK_FACE_TOP)) if((ClickedBlockMeta & 0x08) && (a_BlockFace == BLOCK_FACE_TOP))
{ {
++a_BlockY; ++a_BlockY;