Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 2 weeks ago
All versions
1.3.1
Release
NPC Studio 1.3.1last month 168
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
NPC Studio 1.3.1 - Changelog
NPCs riding boats
- NPCs riding boats now sit using the boat's real passenger seating positions.
- Two NPCs sharing a boat now use proper side-by-side seat offsets.
- Mounted NPCs no longer get culled (vanish) when viewed at steep camera angles.
Custom models
- Added support for Blockbench Java modded-entity models, which now import and render upright.
- Modded-entity models are now mirrored correctly when converted.
- Fixed upside-down textures on modded-entity model faces.
- Custom items built from modded-entity models now use the same upright base transform.
- Paper-thin (zero-thickness) custom model shapes are now nudged so they still render instead of disappearing.
Structure and schematic import
- Added importing of legacy MCEdit/WorldEdit .schematic files as NPC structures.
- Legacy schematics saved uncompressed can now be imported.
- Old numeric block IDs and data values are converted to modern block states on import.
- Chest, sign, and other block entity contents are now preserved when importing schematics.
- Added support for importing the newer Sponge V3 schematic layout.
Rendering and visual fixes
- Enchanted armor that also has a trim now shows its glint shimmer correctly.
- Trimmed armor glint now renders properly on frozen-block NPCs as well.
- Animated-texture blocks now get proper per-face side shading so their sides are lit like normal blocks.
- Restored normal batched NPC rendering by removing a leftover debug path.
Presets
- Preset thumbnails now render for single-NPC presets, which previously showed a blank preview.
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:DYtNBtIy:JmuuIyqQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DYtNBtIy:JmuuIyqQ"
}

