Links
Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated last month
All versions
2.2.5+1.21.11
Release
WikiRenderer 2.2.5 for Minecraft 1.21.118 months ago 81
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Unavailable version
Changes
- Added entity batch rendering support:
- Use
/wikirender group entity namespace <namespace>to render all entities in a namespace - Use
/wikirender group entity namespace <namespace> nbt <nbt>to render all those same entities but with NBT applied to each of them - Use
/wikirender group entity namespace <namespace> nbt_filter <filter> <nbt>to render those same entities with NBT applied, but only if they pass a certain filter - Similarly to above, you can use
/wikirender group entity tag <#namespace:tag>to render entities in a tag, with the same NBT options. - There are three NBT filters to choose from:
require_all_valid: Allows an entity to render if all the provided NBT tags are validrequire_one_valid: Allows an entity to render if at least one of the provided NBT tags is validrequire_none_valid: Allows an entity to render if none of the provided NBT tags are valid- More specifically, a "valid" tag is a tag that is saved with the entity when it tries to save its NBT. Some tags are exported for all entities, regardless of if they change how they render (i.e.
Equipmentfor all living entities), whereas others only get saved for specific types (i.e.Pumpkinfor snow golems)
- Use
- Added support for cropping and rescaling images in batch renders
- Added better error handling for failed exports
- Improved how entities are automatically scaled in exports, now they take up half the screen (on the longer axis) by default
- Changed "atlas" to "itematlas" in the command syntax for atlas renders
- Changed "group" to "group item" in the command syntax for item-based batch renders (as "group entity" was added)
- Fixed a memory leak caused by rescaled images not having previous rescale passes cleared from memory
- Fixed a memory leak caused by cropped images not having the uncropped images cleared from memory
- Fixed a memory leak caused by failed exports not having image data cleared from memory (can happen from trying to scale something up that is too small initially)
- Fixed rendered players (and potentially other mobs) sometimes having an extra line appearing on top of them above the hat layer (was dependent on the position/scale/rotation)
- Fixed entities, tile entities, and particles not rendering through transparent blocks
- Fixed dropped player heads not showing texture data
- Fixed cropped animated entities sometimes having inconsistent file sizes, if the animation could change the height (for vertical rescaling) or width (for horizontal rescaling) between rescale passes
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:7x65n82E:NM06S2Z0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7x65n82E:NM06S2Z0"
}

