1.0.0
Compatibility
Changes
KozaCore
KozaCore is a client-side visual and utility mod for Minecraft 1.21, built on the Fabric loader. It focuses on enhancing the user experience with a sleek purple interface, highly customizable HUD elements, and a variety of quality-of-life modules. 🛠 Features 🎨 Visuals & UI
Purple ClickGUI: A stylish, intuitive interface to manage all your modules.
Custom Main Menu: A redesigned home screen for a fresh look.
Drag HUD: Freely move your HUD elements anywhere on the screen.
Fullbright: Enhances visibility in dark environments.
Time Changer: Adjust the world time locally to your preference.
Swing Animation: Customizable sword/tool swing animations.
📊 Information HUD
Armor HUD: Tracks the durability of your equipped armor.
Potion HUD: Displays active potion effects and their duration.
Keystrokes: Shows your key presses (WASD, CPS) on screen.
FPS / Ping / Direction: Keep track of your performance and orientation.
⚙️ Utilities & Performance
Keybind Manager: Easily bind modules to any key via commands.
Auto Reconnect: Automatically attempts to rejoin a server after a disconnect.
FPS Boost & NoRender: Improves performance by disabling unnecessary particles and rendering overhead.
Zoom: Built-in cinematic zoom for better visibility at a distance.
NameProtection: Hide your real nickname or set a custom one locally.
⌨️ Commands
Set custom nickname: /kozacore name <nick>
Bind module to key: /kozacore bind <module> <key>
Example: /kozacore bind Zoom C
Clear bind: /kozacore bind <module> none
📋 Requirements & Installation
Version: Minecraft 1.21
Loader: Fabric Loader
Required API: Fabric API
Java: 21
Note: KozaCore is a client-side mod. While many features are visual or quality-of-life improvements, always check individual server rules before using utility modules.
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:MyqwPYod:3aPPIfXZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MyqwPYod:3aPPIfXZ"
}

