CoolCatLib

v8.2.0 Release | Nov 10, 2026

✨ New Features

• More common events (api.event.v2.common), fired the same on every loader:
  • EntityEvents.SPAWN: a new mob is about to be added to the world (spawned naturally or with a new chunk, by a spawner, a spawn egg, a command, breeding, a conversion), with why it was made when the game says; interrupt to keep it out, with its passengers. EntityEvents.MOUNT: an entity is about to ride another (interrupt to keep it off), or got off one.
  • PlayerEvents.OPEN_MENU: a player is about to open a menu: a block's, an entity's, an item's, or one another mod opens with extra data; interrupt to keep it closed.
  • RecipeEvents.MATCH: a recipe matched where the game looks one up (furnaces, campfires, smithing tables, stonecutters, crafting grids, other mods' machines), with the block entity or the player asking; interrupt to pass it over for the next one that matches.
  • PlayerEvents.ADVANCEMENT_EARNED (a player completed an advancement), CommandEvents.EXECUTE (a command is about to run; interrupt to stop it) and LivingEvents.EFFECT_APPLICABLE (an effect is about to be given; interrupt to keep it off).
  • BlockEvents.DROPS: a broken block is about to drop its items and experience; change the list and the amount.
  • PlayerEvents.BREAK_SPEED and HARVEST_CHECK: how fast a player breaks a block, and whether their tool is right for it (without it, it drops nothing), on both sides.
  • MerchantEvents.OFFERS: the trades a player is shown, as their own list; take trades out to hide them (they can't make them either).
  • EnchantEvents.TABLE_OPTIONS (the enchantments an enchanting table's offer gives) and ANVIL_RESULT (what an anvil makes; interrupt with another stack or none).
  • LootEvents.MODIFY: any loot table's loot as it's rolled (chests, block drops, mobs, fishing), with the table's id; change the list.
  • LivingEvents.DAMAGE (before armor; interrupt and no damage is taken) and DEATH (interrupt to keep the entity alive), as on 26.1.2.
• Blocks that look like other blocks to some players (api.block.BlockViews): BlockViews.register(id, view) adds a BlockView, which groups players by a key (players with the same key see the same, and a null key leaves everything as it is for them) and says what a block looks like to them. What the server sends them (chunks, block changes, block entities' data) has that block in its place, so their client never knows the real one, while the server keeps it for everything else. BlockViews.refresh(player) sends them their chunks again when what they should see changes.
• BlockEntityRendererRegistry (api.client.registry): registers block entity renderers, the same on every loader, as on 26.x.
• BlockRenderLayers (api.client.registry): register(block, RenderType.translucent()) (or cutout(), cutoutMipped()) draws a block's model in that layer, for textures with clear or partly see-through pixels, the same on every loader.