Mebahel's API

# Mebahel's API Shared systems and utilities used by Mebahel mods. Mebahel's API is a Fabric library that provides common systems used across several Mebahel projects. It contains reusable code for structure processing, custom containers, multiplayer loot handling, entity movement, and other features that would otherwise need to be implemented separately in each mod. The mod is primarily a technical dependency and does not add standalone gameplay content by itself. *** ## Dependencies ### Forge / NeoForge * (https://www.curseforge.com/minecraft/mc-mods/sinytra-connector) * (https://www.curseforge.com/minecraft/mc-mods/forgified-fabric-api) * (https://www.curseforge.com/minecraft/mc-mods/geckolib) ### Fabric * (https://www.curseforge.com/minecraft/mc-mods/fabric-api) * (https://www.curseforge.com/minecraft/mc-mods/geckolib) *** ## For Players and Modpack Users Mebahel's API is installed as a dependency for mods that use its shared systems. In most cases, players do not interact with it directly. Depending on the mod using the API, it can provide features such as dry structure generation, animated custom chests, personal loot, synchronized container behavior, and improved movement for custom entities. ### Structure Water Removal Structures can use the API to remove water and waterlogged states after generation. This is useful for dungeons, ruins, and other structures that may intersect oceans, rivers, caves, or aquifers. ### Custom Chests Mods using the chest framework can provide custom containers with features such as: * Animated opening and closing * Custom sounds and screens * Server-authoritative inventory handling * Multiplayer-safe synchronization * Optional personal loot for each player When personal loot is enabled, each player receives their own generated inventory from the configured loot table instead of sharing the same chest contents. ### Entity Movement Custom entities can use shared movement utilities for combat positioning, including strafing, retreating when a target is too close, target-facing rotation, jump assistance, and anti-stuck handling. ### Installation Install Mebahel's API when another mod lists it as a required dependency. It must be present in the appropriate environment for the mod that depends on it. Removing the API while dependent mods are installed can prevent them from loading or functioning correctly. *** ## For Mod Developers Mebahel's API provides reusable foundations for systems shared between Fabric mods. The goal is to keep common behavior in one library instead of maintaining separate implementations in every project. The main systems currently exposed by the API include: * Structure water removal * Animated custom chest foundations * Personal and shared chest inventories * Screen and screen handler support for custom containers * Entity movement and combat positioning utilities *** ## Developer Installation Add the API repository and dependency to your Fabric project. ### Maven Repository ```gradle repositories { maven { name = "GitLab-Mebahel" url = uri("https://gitlab.com/api/v4/projects/77311613/packages/maven") } } ``` ### Dependency ```gradle dependencies { modImplementation "net.mebahelsapi:mebahels-api:<version>" } ``` ### fabric.mod.json ```json { "depends": { "mebahels-api": "*" } } ``` *** ## Structure Water Removal Processor The water removal processor is intended for structures that should remain dry after generation. It can: * Remove waterlogged states from generated blocks * Clear water inside the processed structure area * Work with template-based structure generation * Perform cleanup after placement without requiring custom logic in every structure ### Usage Add the processor to the relevant structure processor configuration: ```json "processors": "mebahelsapi:water_removal_processor" ``` The cleanup is handled automatically after structure placement and runs on the server side. *** ## Custom Chest Framework The chest framework provides a base implementation for custom containers that need animation, synchronization, custom sounds, or multiplayer-specific inventory behavior. It includes support for: * GeckoLib open, close, and spawn animations * Custom opening and closing sounds * Custom screens and screen handlers * Server-authoritative container logic * Multiplayer synchronization * Personal loot generated separately for each player * Standard shared inventories when personal loot is not used ### Personal Loot When a loot table is configured, the chest can generate a separate inventory for each player. Loot is generated once for that player and stored independently from the inventories seen by other players. This is useful for dungeon rewards, boss chests, or multiplayer structures where every player should be able to claim their own loot. ### Shared Inventory When no person