Tags
Creators
Details
1.4.0
Compatibility
Changes
Added
-
Introduced the new Entity Restoration System (BETA).
StellarProtect can now fully restore entities with all their original data and attributes, preserving unique behaviors and relationships.
This includes:- Villagers → Restored with their level, profession, experience, and custom trades.
- Pets → Dogs, cats, parrots, and other tamed creatures now retain their name, owner, and state.
- Hostile & passive mobs → Restored with their equipment, attributes, and AI data.
This system has been completely rewritten from scratch to achieve a far more accurate and faithful restoration of entity states.
As it’s still in BETA, feedback and bug reports are highly appreciated on the official Discord server. -
Added the new
#entitieshashtag
Allows selectively including or excluding entities from rollback operations, giving more precise control between block and entity recovery.
Improvements
- Enhanced block data string handling to prevent collisions between complex NBT structures (e.g., custom heads, banners, decorated pots, etc.).
- Optimized mixed rollback performance, improving stability and processing time when restoring both blocks and entities together.
Fixed
- Fixed a long-standing issue with container item logging (including chests, shulkers, furnaces, hoppers, droppers, barrels, and more).
The internal pool counters were not properly resetting after multiple operations, which could result in inconsistent or duplicated logs. - Adjusted block data handling to minimize conflicts during fast or concurrent restorations.
Entity Restoration (BETA) — Click to preview

Join the community
- Discord: Join here
- Support on Patreon: Become a patron
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:l3Dexbwu:PW3E7ZrJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l3Dexbwu:PW3E7ZrJ"
}

