Tags
Creators
Details
1.0.6
Compatibility
Changes
Pra'Hyu Suite 1.0.6 for Minecraft 26.1 to 26.3
Minecraft 26.3 support, a new No Nether Fog module, and macros that finally work on mouse buttons.
This release ships three separate files. Pick the one matching your game version.
| File | Minecraft |
|---|---|
prahyu-suite-26.1.2-1.0.6.jar |
26.1, 26.1.1, 26.1.2 |
prahyu-suite-26.2-1.0.6.jar |
26.2 |
prahyu-suite-26.3-1.0.6.jar |
26.3 |
Requires Fabric Loader 0.14.0 or newer, Fabric API, and Java 25.
Added
No Nether Fog
- New module: No Nether Fog. Clears the thick fog of the Nether so you can see across the dimension. The fog is pushed past your render distance, so the far edge of the world still fades out smoothly and chunks do not pop in.
- Only the Nether's own fog is touched. Fog from lava, water, powder snow, Blindness and Darkness still works as usual, even in the Nether.
- Off by default. Turn it on from the config screen, or bind a hotkey to toggle it in game.
- Available on 26.1, 26.2 and 26.3, and translated in all 26 languages.
Minecraft 26.3
- Minecraft 26.3 support. 26.3 replaces the library that handled keyboard and mouse input, which changed every key and mouse button code. All input handling in the suite now goes through a per-version layer, so hotkeys, macros, KeyMap, Favorite Slots and the text fields of the config screen behave the same on every version.
- Your existing configs carry over as they are. Keys are saved by name, and those names did not change.
- Body Layers works on 26.3. The 26.3 builds of the TRansition and TRender libraries it depends on are now bundled with the mod.
Fixed
Macros
- Macros could not be bound to a mouse button. The key capture in the macro editor only listened to the keyboard. Right click, middle click and the side buttons (4 and 5) can now be assigned. Left click still cancels the capture.
- Macros already bound to a mouse button never fired. The mod only checked the keyboard to see if the key was held, so a mouse-bound macro never triggered. Mouse buttons are now checked too.
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:v6WHBH0Y:3nN5LMmI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v6WHBH0Y:3nN5LMmI"
}

