
? 简介
Progressive Core 是 Progressive Mods 生态系统中所有模组共享的基础核心。
它集中管理了通用的系统、工具类以及内部框架,使得各个独立模组能够保持轻量、专注且易于维护。通过将共享逻辑移至专用的核心模块,不仅简化了更新流程,还显著提升了跨模组的兼容性。
Progressive Core 本身不添加任何游戏玩法内容。
它的唯一目的是提供一个稳定且一致的后端支持,确保所有 Progressive 模组能够可靠且高效地协同工作。
? 包含的 API 与系统
Progressive Core 内置了多个内部 API,供 Progressive 模组在此基础上进行开发:
-
核心 API 入口点 (EcentrixAPI)
一个统一的访问点,用于注册模组、共享功能以及获取核心服务。
-
模组与功能注册表 (ModRegistry)
一个中央注册表,每个 Progressive 模组可在此注册自身,并通过 ResourceLocation ID 选择性地发布跨模组功能。这实现了简洁的可选集成(例如:“如果存在 Storage 模组,则启用 X”),而无需硬依赖。
-
网络工具类 (NetworkManager)
共享辅助程序,用于创建一致的数据包 ID(可在核心命名空间内或按模组命名空间划分),从而避免功能模组重复设计命名规范和处理冲突问题。
-
多加载器平台抽象层 (Services + IPlatformHelper)
一种基于服务加载的平台辅助工具,允许通用代码查询模组加载器/平台(Fabric/NeoForge)、检查其他模组是否已加载,并区分开发环境与生产环境。
-
客户端模型加载辅助工具(客户端 API)
EcentrixClientAPI、ModelLoaderRegistry 和 CustomModelResolver 提供了一个小型框架,用于注册基于命名空间的模型解析器。Progressive 模组可以接入自定义模型解析逻辑,而无需在不同加载器之间重复编写样板代码。
-
容器/背包的共享 GUI 界面(客户端 API)
GenericContainerScreen 和 GenericBackpackScreen 提供了可复用的容器 UI 逻辑(按行数自动调整大小、共享纹理),使功能模组能够保持其客户端代码的最小化和一致性。
⚙️ 特性
- 为所有 Progressive Mods 提供集中化的共享代码库
- 确保 Progressive Backpacks、Storage 和 Furnaces 之间的行为一致
- 减少冗余代码,保持功能模组轻量
- 简化维护工作与长期更新
- 针对性能和稳定性进行了优化
- 仅供内部使用 —— 并非旨在作为通用模组开发库
?️ 安装
✅ 客户端和服务端均需安装
- Fabric: 需要 Fabric API
- NeoForge: 无额外依赖(除 NeoForge 本身外)
- 所有受支持的 Progressive Mods 将自动使用本核心
⭐ 相关模组




? 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



评论 0
登录后参与评分
还没有评论,来抢沙发吧