In newer versions it just displays the EvergreenHUD icon everywhere instead of what the mod actually is, this make it impossible to find a mod by just looking at the icon.
A better solution would be to give every HUD element it's own icon, which would be more work though
CPS hud currently detects input from raw mouse input, instead of what keybind each button it set to. One reason is an issue because if you change the keybind for attack/use, when pressing the key it is set to, the cps counter does not go up. Another reason this is an issue is when you are in a gui, and press left/right click, the cps counter goes up.
i have a ton of shell scripts on my system and one of them can monitor the current spotify track, it would be really nice if this mod could monitor some file in .minecraft in a local and secure way and output it as custom text
>Configure project :1.8.9-forge
:could not find forge mod in modRuntimeOnly but forcing:DevAuth-forge-legacy-1.1.2.jar (me.djtheredstoner:DevAuth-forge-legacy:1.1.2)
:could not find forge mod in modRuntimeOnly but forcing:DevAuth-common-1.1.2.jar (me.djtheredstoner:DevAuth-common:1.1.2)
:could not find forge mod in modRuntimeOnly but forcing: toml-3.6.5.jar (com.electronwill.night-config:toml:3.6.5)
:could not find forge mod in modRuntimeOnly but forcing: core-3.6.5.jar (com.electronwill.night-config:core:3.6.5)
>Configure project :1.12.2-forge
ArchitecturyLoom:0.10.0.5:could not find forge mod in modRuntimeOnly but forcing:DevAuth-forge-legacy-1.1.2.jar (me.djtheredstoner:DevAuth-forge-legacy:1.1.2)
:could not find forge mod in modRuntimeOnly but forcing:DevAuth-common-1.1.2.jar (me.djtheredstoner:DevAuth-common:1.1.2)
:could not find forge mod in modRuntimeOnly but forcing: toml-3.6.5.jar (com.electronwill.night-config:toml:3.6.5)
:could not find forge mod in modRuntimeOnly but forcing: core-3.6.5.jar (com.electronwill.night-config:core:3.6.5)
>Task:1.8.9-forge:compileDummyJava
ERRORStatusLoggerUnable to locate a logging implementation, using SimpleLogger>Task:1.12.2-forge:compileKotlin FAILED
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\BedwarsResource.kt: (20, 42):Unresolved reference:S01PacketJoinGame
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\BedwarsResource.kt: (149, 30):Unresolved reference:S01PacketJoinGame
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\BedwarsResource.kt: (171, 44):Cannot access 'stackSize': it isprivatein'ItemStack'
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\BedwarsResource.kt: (176, 73):Cannot access 'stackSize': it isprivatein'ItemStack'
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\Inventory.kt: (16, 45):Unresolved reference:RenderItem
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\Inventory.kt: (19, 42):Unresolved reference:S01PacketJoinGame
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\Inventory.kt: (206, 30):Unresolved reference:S01PacketJoinGame
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\TPS.kt: (11, 42):Unresolved reference:S03PacketTimeUpdate
e:C:\Users\*****\Desktop\EvergreenHUD-oneconfig\versions\1.12.2-forge\build\sources\kotlin\cc\polyfrost\evergreenhud\hud\TPS.kt: (35, 34):Unresolved reference:S03PacketTimeUpdateFAILURE:Build failed with an exception.
*What went wrong:Execution failed for task ':1.12.2-forge:compileKotlin'.
>A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction>Compilation error. See log for more details
*Try:>Run with --stacktrace option to get the stack trace.
>Run with --info or--debug option to get more log output.
>Run with --scan to get full insights.
*Get more help at https://help.gradle.orgDeprecatedGradle features were used inthis build, making it incompatible with Gradle8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.4/userguide/command_line_interface.html#sec:command_line_warningsBUILDFAILEDin 39s
20 actionable tasks:5 executed, 15 up-to-date