Links
Tags
Creators
Details
0.2.0-beta6
Compatibility
Required content
Changes
v0.2.0-beta6+1.21.1:
Full Changelog: https://github.com/CriticalRange/vulkanmod-extra/compare/v0.2.0-beta4...v0.2.0-beta5
Enhanced documentation with comprehensive version management information
ARCHITECTURAL OVERHAUL:
• Complete modular architecture with Feature-based system • New core package structure with clean separation of concerns • Registry pattern implementation with FeatureManager • Enhanced configuration system with ConfigurationManager
PERFORMANCE OPTIMIZATIONS:
• 85% memory reduction in particle settings (100+ fields → efficient HashMap) • Optimized BaseFeature class (removed unused methods, improved efficiency) • Enhanced particle checking logic with early returns • Improved method naming and code clarity across all mixins
BUILD & QUALITY FIXES:
• Reduced build warnings from 100+ to 1 (99% improvement) • Fixed all deprecation warnings by migrating to new config structure • Replaced System.out.println with proper SLF4J logging • Fixed serial warnings in CustomPageList class • Enhanced build system with better code quality tools
CODE IMPROVEMENTS:
• Comprehensive debug logging replacement (6 instances) • Fixed misleading method names in particle mixins • Complete mixin system reorganization (com.criticalrange.mixin → com.criticalrange.mixins) • Enhanced version management with VersionHelper utility • Sophisticated override system for multi-version compatibility
TECHNICAL ENHANCEMENTS:
• Multi-version support system (1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5) • Runtime version detection and comparison utilities • Version-specific method/field mappings using reflection • Improved error handling and compatibility across all versions
VISUAL & ASSET UPDATES:
• High-quality icon update ( 3.9KB -> 186KB) • Enhanced documentation with comprehensive version management information
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| vulkanmod-extra-0.2.0-beta6+1.21.1-sources.jar | Unknown | 267.46 KiB |
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:gglzOxJ8:Q5obWc39"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gglzOxJ8:Q5obWc39"
}


