5.0.0+26.1
Compatibility
Required content
Changes
I did a whole bunch of stuff for this version to fix broken features and generally optimize the mod. IF YOU HAVE ANY ISSUES PLEASE DM ME ON DISCORD @aroiu
-
Added support for importing legacy Python-style exotic databases from .txt, .json, and .py files.
-
Added automatic normalization of imported armor IDs, colors, piece types, set names, owner UUIDs, and timestamps.
-
Improved UUID-based database merging to prevent duplicate items.
-
Reworked /exo db update to significantly reduce memory usage and crash risk.
-
Added safer atomic database writes to protect files from corruption during interrupted updates.
-
Added handling for malformed database records without aborting the entire update.
-
Improved performance for database searches, exports, counts, and Seymour queries using in-memory snapshots.
-
Moved CSV and XLSX exports off the client thread to prevent game freezes.
-
Optimized /exo seymour pieces to retain only the best requested matches.
-
Added separate workers for database maintenance and read-only background operations.
-
Improved inventory highlight performance with per-tick item evaluation caching.
-
Improved tracer performance by caching auto-trace and exotic targets.
-
Reduced tracer debug-log spam with rate limiting.
-
Improved /exo scan island detection for custom armor stands, item frames, glowing item frames, and item-display entities.
-
Added fallback equipment and displayed-item extraction for Hypixel custom display entities.
-
Added detailed island-scanning diagnostics, including entity discovery, extraction methods, item data, and rejection reasons.
-
Changed the island scan summary to report the number of items checked.
-
Removed the /exo scan near command and its help entries.
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:DjlYVzoU:UDP3iJ0A"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DjlYVzoU:UDP3iJ0A"
}


