Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated last month
All versions
1.13.0
Release
Create: Redstone Link Tablet 1.13.0last month 1,041
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
1.13.0 — 2026-08-17
Added
- Hover tooltips on every button and glyph across all program screens — the wordless ones (chain-link, padlock, solo, eyedropper, emote toggle) finally say what they are. Paint's tool tips also name their keyboard shortcuts (B/F/L/R/I), which were previously undiscoverable. Client-only, pairs with 1.12.x.
- Dropped tablets keep transmitting: a tablet lying on the ground (or sitting in an item frame) now broadcasts its toggled-ON signals from where it is — throw a scene tablet into the machine room and the scene keeps running. The Frequency Monitor names these members ("Dropped tablet (player)" / "Framed tablet"), completing the who-is-transmitting story. This changes the old "phantom copy" diagnosis: dropping a spare tablet used to silence it — now the Monitor just names it as a dropped member instead, so the fix for a phantom-pinned receiver is to pick the copy up or destroy it, not drop it. Edge case: a deliberate player toss (Q-drop or inventory drag-out) now registers instantly via an add-only fast path, closing the blink at the exact moment of a throw; because the handoff still runs on a periodic sweep for every other case, edge-sensitive contraptions may still see a brief blip at pickup, or on death drops, dispensers, and other non-toss spawns.
Changed
- Network protocol version unchanged (still 24) — 1.13.0 pairs with 1.12.x on both sides (tooltips are client-only, dropped-tablet transmission is server-side only).
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:hovmfNG2:SAEddoLD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hovmfNG2:SAEddoLD"
}

