From fcb5bdf04241082d08b1ecc083745d6d97af61a9 Mon Sep 17 00:00:00 2001 From: mat Date: Mon, 5 Sep 2022 11:44:48 -0500 Subject: use az-registry in az-protocol --- azalea-protocol/src/packets/game/clientbound_block_update_packet.rs | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'azalea-protocol/src/packets/game/clientbound_block_update_packet.rs') diff --git a/azalea-protocol/src/packets/game/clientbound_block_update_packet.rs b/azalea-protocol/src/packets/game/clientbound_block_update_packet.rs index 44629c82..3034accc 100644 --- a/azalea-protocol/src/packets/game/clientbound_block_update_packet.rs +++ b/azalea-protocol/src/packets/game/clientbound_block_update_packet.rs @@ -1,3 +1,4 @@ +use azalea_block::BlockState; use azalea_buf::McBuf; use azalea_core::BlockPos; use azalea_protocol_macros::ClientboundGamePacket; @@ -5,8 +6,5 @@ use azalea_protocol_macros::ClientboundGamePacket; #[derive(Clone, Debug, McBuf, ClientboundGamePacket)] pub struct ClientboundBlockUpdatePacket { pub pos: BlockPos, - // TODO: in vanilla this is a BlockState, but here we just have it as a number. - // perhaps we could make a crate that only handles block states? right now blockstates are handled in azalea-block - #[var] - pub block_state: u32, + pub block_state: BlockState, } -- cgit v1.2.3