Tags
Creators
Details
1.2.0
Compatibility
Required content
Changes
Memory Leak Detector
Added a new memory monitoring system that watches Minecraft over time and looks for signs of memory leaks. This is not Hypixel-only, you can use this for everything.
It can:
- Detect steadily increasing memory usage
- Notice old worlds/players that stay in memory after leaving
- Detect background tasks that keep accumulating
- Identify mods that may be related to the issue and show a confidence level
- Automatically clean up temporary NSM-owned data when it is no longer needed
- Generate detailed reports that can be attached to bug reports
If NSM suspects a memory problem, it can automatically send a warning in chat with what it found and what you can do next.
Suggested actions may include updating the suspected mod, creating a report before restarting, restarting Minecraft if memory gets too high, or reporting the issue to the mod developer.
Commands are available to check the current status, diagnose problems, clean temporary NSM data, create a report, and reset monitoring.
The detector is designed to avoid blaming mods when there is not enough evidence.
Bug Fixes & Improvements
Dungeon Secrets
- Fixed locked chest spam being counted as a secret
- Bat secrets now only count when the bat actually dies
- Fixed teammate item pickups being counted as your secret
- Fixed essence secrets occasionally counting twice
Room Stacking
- Fixed alert threshold handling
- Fixed
Ignore BloodandIgnore Fairysettings not being respected - Fixed sounds still playing when disabled
Lag Monitor
- Fixed saved settings not loading correctly
- Improved ping tracking
- Fixed incorrect network packets being used for latency checks
- Improved dungeon start/end detection
Minion Fixes
- Disabled minion features now properly stop processing
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:sEm3cR3W:cRE0Dbd2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sEm3cR3W:cRE0Dbd2"
}![Nico's Super Mods [NSM]](https://cdn.modrinth.com/data/sEm3cR3W/2c2fe185354af32e885271cb9aa2b8986d882a5b_96.webp)

