PacketBlocks

## PacketBlocks 1.2.7 ### Added: bisected block support Packet blocks now render both halves of two-block-tall blocks such as doors, tall flowers, tall grass and rose bushes. Previously only the bottom half would appear. - Create a packet block or group with the bottom half and the top half is added automatically. - Works with single packet blocks and packet block groups. - Removing the bottom half also removes the top half, and both halves are restored for the viewer. - Chunk loads, block updates and ray tracing all handle the top half too. - Stairs and trapdoors are unaffected. You no longer need to place the two halves yourself. If you already do, your code keeps working. ### Fixed - `PacketBlockUtil.getBlockData` and `getBlockType` now return the player's own data for a single packet block, where they used to return the shared data. If you pass a player, you now get that player's data.

- Added Folia support - Bumped version to `1.2.6`

- Bumped required PacketEvents version to `2.13.0` - Removed requirement to disable fly in server.properties - Added `Block-Flight-Kick` config option to block *all* player flight kicks

## 🩹 PacketBlocks - v1.2.4 Hotfix ### 🐛 Fix - Fixed an issue where `PacketBlockGroup` blocks outside a chunk could wrap and render on the wrong side. ### 🔧 Details - Blocks are now validated against the target chunk before being written. - Prevents cross-chunk wraparound and visual inconsistencies. Safe to update. No API changes.

## 📦 PacketBlocks — v1.2.3 Group Updates ### 📌 What’s New This release enhances the **PacketBlocks** API by adding support for adding and removing blocks from existing `PacketBlockGroup` instances. These new methods make it significantly easier to modify block groups after creation. ### ✅ Highlights - **Added** methods in `PacketBlockManager` to: - Add multiple blocks to a group (`addBlocksToGroup(...)`) - Add single blocks to a group (`addBlockToGroup(...)`) - Remove multiple blocks from a group (`removeBlocksFromGroup(...)`) - Remove single blocks from a group (`removeBlockFromGroup(...)`) ### 🧠 Why This Matters Previously, block groups were static after creation. With this update, developers can dynamically modify groups at runtime!

## 🔧 Hotfix - 1.2.2 **Summary** - Ensures `updateConsumer` is invoked when a viewer is added and updated - Fixes cases where viewers were not receiving updates after being registered **Impact** - Viewer state is now correctly synchronized on add **Notes** - No breaking changes

# PacketBlocks v1.2.1 — Hotfix Release ## 🛠 Fixed An oversight in the previous version caused any updates to the data in a PacketBlock or PacketBlock group to not properly reflect in updates sent to players. --- This is a **hotfix release**, intended for all users of v1.2.0 to ensure block updates work as expected.

# 📦 PacketBlocks — 1.2.0 Release Notes This release introduces **grouped packet blocks**, along with a substantial internal refactor to improve extensibility, clarity, and long-term maintainability. --- ## 🚀 New Features ### ✅ Packet Block Groups PacketBlocks now supports **grouped blocks**, allowing multiple packet blocks to behave as a single logical unit. With **PacketBlockGroup**, you can: - Treat multiple blocks as one entity - Share metadata and state across a block cluster - Handle interactions (break, place, update) at the group level - Resolve BlockData dynamically per group This enables more advanced structures such as multi-block machines, large custom blocks, or linked visual elements. > Group logic is implemented in > `net.bitbylogic.packetblocks.group.PacketBlockGroup` --- ## 🔄 Group-Aware Packet Handling Packet adapters have been updated to detect and respect block groups automatically: - `BlockBreakAdapter` - `BlockPlaceAdapter` - `BlockUpdateAdapter` - `ChunkLoadAdapter` Each adapter now: - Detects whether a block belongs to a group - Resolves group-specific BlockData - Applies packet overrides consistently across the entire group This ensures correct rendering and interaction behavior on the client. --- ## 🧩 Event Improvements Existing events now support **group context**, including: - `PacketBlockStartBreakEvent` - `PacketBlockBreakEvent` - `PacketBlockInteractEvent` Event consumers can now determine whether an interaction applies to: - A single block - A block group

## 🚀 PacketBlocks v1.1.1 — Block Position Keying Fix & Stability Improvements ### ⚙️ Internal Changes - Migrated block indexing to WorldPosition rather than Location - PacketBlock's may now have a set of BoundingBoxes rather than a single one. ### Performance Improvements This update should drastically improve lookup times and raytracing performance using the PacketBlockUtil#rayTrace method.

## 🚀 PacketBlocks v1.1.0 - Improved Bounding Boxes & Ray Tracing ### ✨ Changes - Reworked bounding boxes to be identified by block state, allowing accurate shape retrieval for all block variants - Overhauled packet block ray tracing to more accurately detect blocks - Improved reliability when interacting with non-full and complex block shapes