[Ecentrix] Progressive Core

[!(https://cdn.jsdelivr.net/npm/@intergrav/devins-badges@3/assets/cozy/available/curseforge_vector.svg)](https://www.curseforge.com/minecraft/mc-mods/ecentrix-progressive-core) [!(https://cdn.jsdelivr.net/npm/@intergrav/devins-badges@3/assets/cozy/available/modrinth_vector.svg)](https://modrinth.com/mod/ecentrix-progressive-core) [!(https://cdn.jsdelivr.net/npm/@intergrav/devins-badges@3/assets/cozy/requires/fabric-api_vector.svg)](https://modrinth.com/mod/fabric-api)

### 📖 About

Progressive Core is the shared foundation for all mods within the Progressive Mods ecosystem.

It centralizes common systems, utilities, and internal frameworks, allowing each individual mod to remain lightweight, focused, and easy to maintain. By moving shared logic into a dedicated core module, updates are streamlined and cross-mod compatibility is significantly improved.

Progressive Core does not add gameplay content on its own. Its sole purpose is to provide a stable and consistent backend that ensures all Progressive mods work together reliably and efficiently.

### 🔌 Included APIs & Systems

Progressive Core includes several internal APIs that Progressive mods build on:

Core API entry point (`EcentrixAPI`) A single access point for registering mods, shared features, and retrieving core services.

Mod & Feature registry (`ModRegistry`) A central registry where each Progressive mod can register itself and optionally publish cross-mod features via `ResourceLocation` IDs. This enables clean optional integrations (e.g., “if Storage is present, enable X”) without hard dependencies.

Network utilities (`NetworkManager`) Shared helpers to create consistent packet IDs (either in the core namespace or per-mod namespace), so feature mods don’t have to reinvent naming conventions and collision-avoidance.

Multi-loader platform abstraction (`Services` + `IPlatformHelper`) A service-loaded platform helper that allows common code to query the modloader/platform (Fabric/NeoForge), check whether other mods are loaded, and detect dev vs production environments.

Client model loading helpers (client API) `EcentrixClientAPI`, `ModelLoaderRegistry`, and `CustomModelResolver` provide a small framework for registering namespace-based model resolvers. Progressive mods can plug in custom model resolution without duplicating boilerplate across loaders.

Shared GUI screens for containers/backpacks (client API) `GenericContainerScreen` and `GenericBackpackScreen` provide reusable container UI logic (auto-sizing by rows, shared textures), so feature mods can keep their client code minimal and consistent.

### ⚙️ Features

Centralized shared codebase for all Progressive Mods Guarantees consistent behavior across Progressive Backpacks, Storage, and Furnaces Reduces redundancy and keeps feature mods lightweight Simplifies maintenance and long-term updates Optimized for performance and stability Internal-use only — not intended as a general-purpose modding library

### 🛠️ Installation

✅ Required on both client and server

Fabric: requires Fabric API NeoForge: no additional dependencies (besides NeoForge itself) * Automatically used by all supported Progressive Mods

### ⭐ Related Mods

[!(https://cdn.modrinth.com/data/cached_images/9d2f0fad0010fdee255cea8aec543abf383200c6.png)](https://modrinth.com/mod/ecentrix-progressive-storage)

[!(https://cdn.modrinth.com/data/cached_images/31b96b0e93a7da4bcb69c4faee59c88710c1dcfe.png)](https://modrinth.com/mod/ecentrix-progressive-furnaces)

[!(https://cdn.modrinth.com/data/cached_images/2461e4988583375ba440cd4d5a88aa9c94f58f15.png)](https://modrinth.com/mod/ecentrix-progressive-backpacks)