Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Created 4 years ago
Updated last week
All versions
1.26.10.1
Release
Let Me Despawn 1.26.10.1last week 258
Compatibility
Minecraft: Java Edition
26.4-snapshot-4
26.3
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
Changed
- Settings now use Dungeon Config (bundled with Almanac). They are stored in
config/letmedespawn/letmedespawn.json5and can be edited in game, with searchable mob and item pickers. The previousconfig/letmedespawn.jsonis imported automatically. /letmedespawn addandaddPersistenceEnablernow reject unknown ids instead of saving them, and suggest every entity type rather than monsters only.- Endermen carrying a block now drop it when they despawn instead of losing it.
- Removed MobStacker-specific name handling: a mob with any custom name is treated as named.
- Requires Almanac 1.26.10.2 or newer.
Fixed
- Picking up an item no longer clears persistence a mob already had. Structure mobs such as mansion illagers and ocean ruin drowned, name-tagged mobs, and mobs made persistent by commands or other mods now stay persistent.
- Equipment from a dispenser now follows the despawn rules. Previously the dispenser made the mob persistent after LetMeDespawn had run.
- Monsters are removed on Peaceful difficulty again, even while holding a persistence enabler item.
- Mobs from spawners with custom spawn data and from configured trial spawners are now recognised, and the spawner origin is saved with the mob, so the spawner rules survive chunk reloads and server restarts.
- Despawn hooks no longer use
@Redirect, which conflicted with other mods hooking the same calls.
Performance
- Mob and item lookups compare registry ids directly instead of building strings, and the equipment slot list is no longer reallocated on every despawn check.
- Removed an unused mixin and a duplicate persistence calculation on every item pickup.
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:vE2FN5qn:1oLhVad0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vE2FN5qn:1oLhVad0"
}

