Messages overhaul + message styling API#5
Open
AlignedCookie88 wants to merge 5 commits intoBlazeMCworld:mainfrom
Open
Messages overhaul + message styling API#5AlignedCookie88 wants to merge 5 commits intoBlazeMCworld:mainfrom
AlignedCookie88 wants to merge 5 commits intoBlazeMCworld:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The messages now look like:

The API can be used as so:
It currently uses the Adventure API and MiniMessage but I am ok with changing this to use the vanilla Text API if required.
The current message types consist of:
INFO- Used for messages conveying information that do not fit into other categories.SUCCESS- Used to notify the user of a successful action.ERROR- Used to notify the user of an error.FOLLOWUP- Used to provide additional context to previous messages.NOTIFY- Used to notify the user of an action that may require their intervention.These are static final fields on the Messages class.
The
ERRORandNOTIFYtypes play sound effects when sent to a player, i'm not too sure of the best way to show this in the PR.