Tags
Creators
Details
All versions
0.2.0
Beta
MKT Essentials 0.2.05 months ago 27
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
v0.2.0 — Ground Item System Fixes
Bug Fixes
Critical
- Fixed a bug where setting despawn-time: 0 also disabled item stacking and holograms — each feature now operates independently
- Fixed a race condition with Minecraft's native item despawn timer — when mod despawn is enabled, the vanilla timer is now suppressed (lifespan = MAX_VALUE); previously items with a despawn time above 5 minutes were removed by Minecraft before the configured time
- Fixed orphaned holograms persisting across server restarts — holograms in unloaded chunks were never cleaned up and duplicated on every restart; added an EntityJoinLevelEvent interceptor that blocks stale holograms from loading regardless of when the chunk loads
Performance
- Fixed O(n²) complexity in the lightweight hologram position update (every 5 ticks) — instead of scanning all level entities for each hologram, the manager now holds direct ItemEntity references, reducing complexity to O(n)
Holograms
- Holograms are now invulnerable (setInvulnerable) and have no hitbox (setMarker via reflection) — previously players could accidentally destroy them
- Fixed a 0.5-block position snap one second after hologram creation — the Y offset was inconsistent between the creation method and update methods; unified via a HOLOGRAM_Y_OFFSET constant
- Holograms no longer display a countdown timer when despawn-time: 0 (disabled)
Stacking
- Fixed missing partial stack merging — previously items would not merge at all when the combined count exceeded the stack size limit (e.g. 60 + 20 arrows had no effect); stacking now works incrementally (60 + 20 → full stack of 64 + remainder of 16)
Sweep
- Fixed the sweep warning being broadcast immediately when sweep-warning was greater than or equal to sweep-interval
New Features
- Added items.max-stack-size option in settings.yml — allows ground items to merge beyond the vanilla limit of 64 (e.g. max-stack-size: 200); items picked up by players are automatically split into normal inventory slots
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:dzLZCn7R:yqQehlYE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dzLZCn7R:yqQehlYE"
}

