Links
Tags
Creators
Details
Licensed Apache-2.0
Published 5 months ago
Updated 12 hours ago
All versions
1.1.3-new
Release
Blocky Outline 1.1.3-new12 hours ago 160
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
What's new in Blocky Outline v1.1.3-new:
Bug Fixes
- Fixed Menu (M) Crash across 1.21.x & 26.x: Resolved all menu crashes on both legacy Minecraft 1.21 (1.21.0 – 1.21.4) and modern versions (1.21.11+ / 26.x) via the dynamic Dual-Runtime Bridge.
- Fixed Render Event Registration: Resolved
IllegalAccessExceptionwhen registeringBEFORE_BLOCK_OUTLINEwith Fabric API. - Fixed Minecraft Version Detection for 26.1.x – 26.3: Added proper version range declarations in
fabric.mod.json, enabling seamless loading across all Fabric 1.21.x and 26.x releases. - Fixed Incorrect Menu Version Tag: Corrected the version indicator displayed in the menu header from
v1.1.7tov1.1.3-new. - Fixed Menu Layout Overflow: Fixed elements and cards overlapping the footer on smaller window resolutions or higher GUI Scales (Scale 3, 4, Auto).
- Fixed Frame Micro-Stutters (Zero-GC): Completely eliminated per-frame heap allocations during outline/fill rendering and crosshair tracking.
Changes & Improvements
- Added
/reportCommand: Run/reportor/blockyoutline reportin chat to quickly open the official GitHub Issues page in your browser. - Added "Report Bug" Button in Menu [M]: Added a quick teal button next to the Done button in the settings footer for instant feedback submission.
- Render Fast-Path: Standard cube blocks (>95% of world blocks) are now drawn directly via a fast-path, skipping complex shape slice evaluations.
- Optimized Reflection with
MethodHandle: Boosted per-frame matrix, camera, and offset queries by 20–50x with zero boxing overhead. - Resting CPU Optimization: Halts spring and physics calculations when the crosshair rests steadily on a target block.
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:T13rrCSg:IAZ8fm9E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:T13rrCSg:IAZ8fm9E"
}

