TEKKIT II Unofficial

BuildCraft Community Edition
- Restored the original BuildCraft 8 Quarry fluid behavior. Water and other low-viscosity fluids remain passable, while lava, heavy oil, and other high-viscosity fluids now act as barriers and prevent the Quarry from mining blocks underneath them
- The Quarry now periodically checks already excavated areas and can detect new blocks placed inside the quarry after the drill has already passed through that area
- Fixed an issue where a fluid container rejected by a machine could continue its normal use action and place fluid directly into or through the machine block, potentially destroying the machine
- Fixed fluid-container handling in Survival when the item's capability replaces its container during a fluid transfer
- Fixed Quarry stalls caused by stale frame-breaking tasks when the target block disappeared, was broken by a player, another Quarry, or another world update
- Fixed cases where the Quarry could permanently lose a block-breaking task and stop displaying the corresponding red laser
- The Quarry can now correctly clear frame obstacles that cannot be harvested with its default tool instead of retrying the same block indefinitely
- Fixed the Quarry drill head and upper drill section disappearing when processing fluids or other blocks with empty geometry
- Improved cleanup of stale denied Quarry positions so outdated entries no longer block further operation after the world state changes
- Improved item pipe hand-off reliability. Items travelling through connected pipes now retry temporary hand-off failures instead of being dropped into the world, preventing cargo loss in otherwise valid pipe networks, especially at high speeds such as Golden Item Pipes
- Reworked fluid-container handling to consistently use the container's own fluid handler and resulting container state. BuildCraft fuel buckets, vanilla and modded buckets, and fragile fluid containers now behave consistently across direct machine interaction and GUI transfers
- Fixed Combustion Engine fluid-container interactions. BuildCraft fuel buckets and fragile fuel containers are now consumed correctly in Survival, empty buckets are returned properly, and direct interaction no longer leaves the original filled container behind
- Fixed Combustion Engine GUI fluid transfers, including cases where inserting BuildCraft fuel could delete the bucket instead of returning an empty one
- Fixed Combustion Engine shift-click handling using raw player-inventory indices instead of menu-slot indices, which could move or replace the wrong item
- Improved fluid transaction safety. Player inventory and GUI state are now committed before fluid sounds are played, preventing cosmetic sound failures from causing duplicated, deleted, or desynchronized fluid containers
- Fluid sounds are now non-fatal. Missing or broken third-party fluid sound providers fall back to vanilla bucket sounds instead of aborting an already completed fluid transfer
- Fixed Quarry fluid detection so standalone fluids are correctly distinguished from waterlogged blocks. Water and other low-viscosity standalone fluids remain traversable, high-viscosity fluids remain barriers, and waterlogged solid blocks are still mined as normal blocks
- Fixed Quarry chunk-loading initialization so chunk loading only starts once both the frame and mining areas are fully initialized, avoiding invalid half-configured Quarry states
- Fixed packet ID allocation for the Electronic Library, Distiller, and BC8 Distiller by exposing their correct child packet allocators, preventing payload IDs from being validated against the wrong allocator
- Fixed the Facade Swap recipe on Minecraft 1.19.2 being exposed as a generic recipe instead of a crafting recipe, restoring correct recipe classification and compatibility with crafting-related systems
- Fixed a crash when placing a Redstone Engine next to a Wooden Item Pipe in singleplayer
- Fixed MJ/FE energy metadata checks incorrectly executing server-only capability logic on the client
- Hardened related Wooden/Obsidian Pipe energy queries against similar client-side crashes