Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated last week
All versions
0.1.9
Release
Sorted 0.1.9 (neoforge)last week 23
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
Fixed
- Auto-scan and nearby Quick Stack no longer flash the chest GUI on Minecraft 26.2+. The headless opens the scanner makes were meant to be invisible; on 26.2 the screen showed anyway, each container took a two-second timeout instead of a tick, and nothing was cached — so the same chests were scanned again and again. Minecraft moved where a container screen is opened in 26.2; the mod now suppresses it in the new place. 26.1 was never affected, and the one jar still covers the whole 26.x line.
- A container's name in the cache can now be cleared. Renaming a chest updated its cached name, but taking the name off again did not — the old label stuck around indefinitely. All versions.
Added
- Player heads render with their own face in glance labels, container search results and the shulker lid preview, instead of the default Steve head. Custom heads are drawn from the skin the head itself carries, so they look right without a lookup. All versions.
Changed
- The container cache is upgraded in place instead of being thrown away. Storing head skins needed a new cache field; rather than wiping the file and making you re-scan everything, the existing cache is migrated and keeps its containers, names and sort modes. Heads cached before this update draw the default face until their container is next scanned, which happens on its own as entries go stale.
Optional dependencies
Any compatible version
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:vtsGVHan:Lpm1U20t"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtsGVHan:Lpm1U20t"
}

