![[AN]Adaptive Nemesis](https://cdn.modrinth.com/data/anacxDIl/f63c99aa9be78e31253e68c2c8368f95ea97d58e.gif)
[AN]Adaptive Nemesis
The dynamic difficulty balancing module specifically designed for integration packs aims to address the issue of difficulty imbalance in current mainstream integration packs, where the early game is too easy and the late game is too challenging.
Tags
Creators
Details
1.0.10
Compatibility
Changes
⚔️ Adaptive Nemesis v1.0.10 ⚔️
Tired of squinting at tiny input boxes? So were we.
Now you can edit those long lists in comfort.
📋 What's New
| Type | Change | Details |
|---|---|---|
| ✨ Added | Long Text Edit Screen | A dedicated modal for editing lengthy config fields |
| 🔧 Reworked | Config UI | Replaced cramped input boxes with preview buttons + popup editing |
| 📦 Bumped | Mod Version | 1.0.9 → 1.0.10 |
| 🧹 Cleaned | Temp Files | Removed the temporary refactor review report |
🎯 Why This Matters
Ever tried editing a massive entity blacklist or a long list of Boss exclusions in a tiny 320px-wide box? Painful.
Now those fields show a preview button (first 16 chars) that opens a full-screen modal with:
- 🖊️ A wide, adaptive text box (up to 640px)
- 🔢 Live character count badge
- ✨ Smooth fade-in animation
- 🟠 Clean, dark-themed UI matching the main config screen
🔄 Affected Config Fields
| Config Field | What It Does |
|---|---|
| Boss Damage Cap Exclusions | List of bosses immune to the damage cap system |
| Entity Blacklist | Entities excluded from adaptive scaling |
| Debug Log File Path | Custom path for debug output |
⚠️ Heads Up
No breaking changes. Your existing config files will work exactly as before.
The only difference is how you edit them — and it's a lot nicer now.
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:anacxDIl:r3GMewJY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:anacxDIl:r3GMewJY"
}
