v2.0.0
(under construction)
v1.2.0
Changes
-
Complete overhaul of pack generation and management.
-
Plugin always generates fully-assembled resource pack.
-
Resources from the vanilla resource pack can be referenced automatically.
-
Language files are now bundled internally with the plugin and not copied to data folder.
Additions
-
Resource pack generation can now be configured to target certain client versions via
resource-pack.support
. -
Resource pack description can now be configured via
resource-pack.description
using MiniMessage markup. -
Resources from other packs can be imported using
resource-pack.resources
. -
MythicHUD can now be used to manage packs generated by other plugins using the
resource-pack.merge
configuration option. -
Resource pack generation will generate a
.zip
archive ifresource-pack.destination
ends in.zip
. -
Users can now configure z-offset of layers and asset layers.
-
Users can hide vanilla HUD elements using
elements
.
Removals
- Custom fonts are no longer manually configured via separate configuration. Instead, define them in a resource pack and import.
v1.0.0
Additions
-
Support for server versions 1.20.6 through 1.21.1. Paper removed a necessary snapshot version of Adventure, so it is not possible to target 1.20.5 with paperclip-userdev.
-
Support for client versions 1.20.5 through 1.21.1. A new
mythichud-modern
overlay is added to provide the updated shader for those versions. -
Proper API publishing. Documentation for API consumers is coming for a later release, but it is possible to do so now if you are so inclined to figure it out.
-
Automatic migration from HappyHUD. As long as the plugin data folder exists, MythicHUD will attempt to migrate the installation and guide users to ensure functionality.
-
Development builds! Users can now keep track of project activity from our Discord server. Downloadable builds will be added soon.
Removals
-
Support for Spigot and Bukkit servers. Support will be added back in a later release. Currently, the plugin will function in minimal state.
-
Dependency on ProtocolLib. While useful in some contexts, ProtocolLib is has undesirable implications for performance and maintainability.
Changes
-
Significant internal refactoring and optimization
-
Fully asynchronous, native implementation of packet injection. By dropping ProtocolLib, we now use a fully custom packet handling implementation, allowing for markedly better performance.