All versions
1.4.4
Release
MITE Underworld 1.4.453 minutes ago 2
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
R1.4.4
- This update is compatible with save files from version 1.4.3 and later.
- Optimized the detection and conversion logic for vanilla workbenches and certain disabled blocks. A flag is now added to previously scanned chunks to prevent redundant re-scanning, thereby improving performance.
- Optimized the AI pathfinding logic for monsters tracking the player. This addresses the issue of large numbers of monsters clustering in a single location at night; instead of all rushing the player simultaneously, monsters are now deployed in waves. A new wave is triggered only after the current group has been defeated by the player. The deployment counts are as follows: 4 monsters per wave on the Overworld surface, 8 monsters per wave in the deep layers of the Overworld, and 8 monsters per wave in other dimensions.
- Updated background images.
- Optimized the rendering of water color during a "Blood Moon."
- Increased the monster spawn limit for the Underground dimension from 35 to 40.
- Recommendations: For single-player games, allocate at least 4–6 GB of RAM. For LAN multiplayer, the host should allocate at least 8 GB. For multiplayer sessions, using a dedicated server is recommended.
R1.4.4
- 此更新后,兼容1.4.3及其以后版本的存档;
- 优化原版工作台与一些禁用方块的检测与转换逻辑,对已经扫描过的区块,添加一个标记,使得后续不再重复多次扫描,加快运行速度;
- 优化怪物追踪玩家的AI寻路逻辑;解决夜晚大量怪物集中在一个地方的问题,现在怪物不再一起冲向玩家,而是由系统分批调配,当当前批次的怪物被目标玩家击杀后,系统才再次尝试调配附近的怪物追击目标玩家;在主世界地表,每次调配4个怪物;在主世界的深层,每次调配8个怪物;其它维度,每次调配8个怪物;
- 调整背景图片;
- 优化血月期间水体颜色的渲染;
- 地下世界维度的怪物刷新上限由35个改为40个;
- 建议:单人游戏至少需要分配4-6G内存,多人局域网游戏,主机建议至少8G以上;多人游戏建议使用服务端;
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:vRtxSy7y:vDNwSLza"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vRtxSy7y:vDNwSLza"
}

