1.0-beta.1
Compatibility
Changes
๐ MoonBorne 1.0-Beta.1
This update marks a major transition for the mod. BloodMoon Enhanced is now MoonBorne, with a new identity, a completely redesigned configuration system, and a significant internal refactor.
๐ New Identity โ MoonBorne
BloodMoon Enhanced has officially been renamed to MoonBorne.
This is more than a simple name change. The mod is moving toward its own identity and expanding beyond the original BloodMoon concept.
- New Mod ID: moonborne
- New project name: MoonBorne
- Updated assets and translations
- Updated creative tab
- Updated item and entity identifiers
- Updated key mappings and localization
- Updated internal packages and references
โ ๏ธ Important: Due to the Mod ID and registry changes, items obtained from previous versions may no longer exist after updating. If you have items from BloodMoon Enhanced in your world, they may be lost when upgrading to MoonBorne.
โ๏ธ Completely New Configuration System
The old Forge ModConfig system and .toml configuration have been completely removed.
MoonBorne now uses its own configuration system based on JSON.
Previous configuration:
config/bloodmoon-enhanced-common.toml
New configuration:
config/moonborne/moonborne.json
This change required a large internal refactor of how configuration is loaded, stored, modified, and applied at runtime.
๐ฅ๏ธ In-Game Configuration UI
You no longer need to manually edit configuration files.
Press F8 by default to open the MoonBorne configuration menu.
The new configuration UI allows you to configure the features that were previously available through the TOML file, including:
- General settings
- Moon intervals
- Moon types
- Moon probabilities
- Horde settings
- Mob templates
- Mob effects
- Player effects
- Horde drops
- Mob Kill Actions
- Difficulty modifiers
- And more
The configuration interface will continue to expand as MoonBorne receives new features.
๐ง Major Internal Refactor
The new configuration system required substantial changes throughout the mod.
- Removed the old Forge ModConfig implementation
- Removed TOML-based configuration
- Added JSON-based configuration
- Added configuration state classes
- Added configuration serialization/deserialization
- Added runtime configuration reloading
- Added a new configuration management system
- Added multiple configuration screens and editors
- Reworked how configuration changes propagate through the mod
- Improved separation between configuration state and runtime state
This refactor also provides a much better foundation for future MoonBorne features.
๐ Bug Fixes
A number of bugs discovered during development of the previous version have also been fixed.
- Fixed several configuration-related issues
- Fixed incorrect configuration values being applied at runtime
- Fixed various GUI and navigation issues
- Fixed several mob and horde-related issues
- Fixed miscellaneous gameplay and stability bugs
- Improved configuration handling and validation
๐ง Beta
MoonBorne is still in Beta.
The new configuration system is now the foundation for future development, and more content, mechanics, abilities, and configuration options are planned.
Welcome to MoonBorne. ๐
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:EBRtMmX4:qtexuMFc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EBRtMmX4:qtexuMFc"
}

