Links
Tags
Creators
Details
Licensed Apache-2.0
Published 2 months ago
Updated last week
All versions
0.1.17
Beta
totem-vanilla-tweaks 0.1.172 months ago 5
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Any compatible version
Changes
TotemVanillaTweaks 0.1.17 Beta
Observer View — protocol-native rewrite
- Replaced the old framebuffer/PNG relay with protocol-native observation.
- Observer world rendering now uses Minecraft's native spectator camera and normal chunk/entity synchronization.
- Added locally reconstructed Target HUD state including health, food, saturation, experience and selected hotbar slot.
- Removed production
FrameChunk,FrameRelay,CaptureControl, screenshot transport and dynamic frame textures. - Incompatible Observer clients are rejected instead of falling back to image transport.
Semantic screen capabilities
- Observer gameplay/session protocol is now v4 with semantic screen protocol v2.
- Added negotiated per-screen-family capability masks.
- Added
container_slotssemantic reconstruction for supported container screens. - Added dedicated
furnacesemantic reconstruction for furnace, smoker and blast-furnace style screens, including slots, cook progress, fuel progress and lit state. - Unsupported or unnegotiated screens use a local metadata-only placeholder; Target pixels are never transmitted.
Validation and runtime fixes
- Added/expanded Server GameTests, Client GameTests, production-runtime tests and a real Dedicated Server + Target Client + Observer Client three-JVM E2E.
- CI now enforces a framebuffer-free production source invariant.
- Fixed client/server side separation for concrete-powder hardening discovered by Observer E2E coverage.
- Keeps the Minecraft 26.2 production namespace/remap fix introduced in 0.1.16.
Minecraft 26.2 · Fabric · Java 25 · requires Fabric API and TotemCore >=0.7.0 <0.8.0.
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:mEcpkZT2:1pF4b3hX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mEcpkZT2:1pF4b3hX"
}

