All versions
3.4.0-beta
Beta
Lode Entities 3.4.0-betayesterday 12
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.4–1.21.11
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Velocity
Changes
- Added player-looking NPCs:
base: playerspawns a mannequin (Minecraft 1.21.9+) - Added
skin:forbase: playermobs: a player name, a uuid, or a 64x64 png beside the mob's file (baked into the resource pack, no upload needed) - Player-looking NPCs hide the grey "NPC" label, so only their display name shows
- NPC movement is back as fields on
type: npcmobs:follow,behaviour(wandering,chaser,playerlike),radiusandpositioning - Added
behaviour: guard: stands on its spot, hunts inside itsradius, then walks back and faces the way it was placed - Added
chase:to set what a chaser or guard goes after, by entity type or mob id (players by default) - A chaser or guard with
damage:now hits what it catches - Moving NPCs walk with Minecraft's own pathfinding, so player-looking NPCs can move too
- Follow, behaviour, radius and positioning can be set from the
/le guieditor - Converting an old
NPCs/folder now carries follow, behaviour, radius, positioning and the player look over instead of dropping them look: trueNPCs now turn their head up to 50° before the body follows, like a player- Fixed
look: trueNPCs keeping the head pitch they spawned with - Fixed
look: trueNPCs turning their head all the way round without the body following - Fixed player skins showing as the default skin on offline-mode servers (test servers, Velocity backends)
- Fixed the plugin failing to enable on Minecraft 26.3
- Fixed armor on player-skin models failing to load on Minecraft 26.3
- Config:
npc.behaviour-intervalis back inconfig.yml(default2) - API:
MobDefinitiongainedskin,follow,behaviour,radius,positioningandchase
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:VSNXrXJh:XakykWTP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VSNXrXJh:XakykWTP"
}

