Parsing Messages

The most important file of RoseChat's API is the RoseChatAPI class, which can be found here.
This class contains many functions which you may find useful.

The most convenient way of parsing a message is to use the RoseChatAPI#parse() function. This function will take a given string and parse it using RoseChat's message wrapper and message tokenizer system. This will allow colors (including hex, rainbow and gradient), emojis, tags, and everything else included in RoseChat, to be parsed.

There are a few variations of this function:

This method simply parses the message.

BaseComponent[] parse(RosePlayer sender, RosePlayer viewer, String message)

This method allows you to use placeholders in the message.

BaseComponent[] parse(RosePlayer sender, RosePlayer viewer, String message, StringPlaceholders placeholders)

This method allows using a MessageLocation to check for permissions.

BaseComponent[] parse(RosePlayer sender, RosePlayerviewer, String message, MessageLocation location)

RosePlayer

The RosePlayer object is used by RoseChat to give more information to a Player object. When you need to use a RoseSender, you can just create a new RosePlayer(). This object has a few different constructors, but passing a Player object through is the most common.

This is an example of how to use these together, for parsing a message when the player joins.

@EventHandler
public void onPlayerJoin(PlayerJoinEvent event) {
    RoseChatAPI rosechat = RoseChatAPI.getInstance();
    Player player = event.getPlayer();
    RoseSender roseSender = new RoseSender(player);

    BaseComponent[] message = rosechat.parse(roseSender, roseSender, "<r:0.5>Hi %player_name% &r:rosewood:");
    Bukkit.spigot().broadcast(message);
}

When parsing a single message, this may be preferred. However, to allow multiple messages to be sent at the same time to multiple players, these should be sent asynchronously.
The RoseChatChannel class displays how.

The parse method creates a single RoseMessage object, intended to be viewed the same by any player.
Creating a new RoseMessage object for each player allows each player to receive a message unique to them.

Rose Messages

The preferred way to send a message to multiple players is by creating a new RoseMessage().
This class is useful as, by default, parsed messages do not filter things like URLs and spam.

An example of this is used in the RoseChatChannel class:

        // Create the rules for this message.
        MessageRules rules = new MessageRules().applyAllFilters().applySenderChatColor();

        // Parses the first message synchronously
        // Allows for creating a token storage.
        RoseMessage roseMessage = new RoseMessage(sender, this, message);
        roseMessage.applyRules(rules);

        // Check if the message is allowed to be sent.
        if (roseMessage.isBlocked()) {
            if (roseMessage.getFilterType() != null)
                roseMessage.getFilterType().sendWarning(sender);
            return;
        }

        BaseComponent[] parsedConsoleMessage = roseMessage.parse(new RosePlayer(Bukkit.getConsoleSender()), this.getFormat());

        // Send the parsed message to the console
        Bukkit.getConsoleSender().spigot().sendMessage(parsedConsoleMessage);

This creates a new MessageRules object, which defines the rules of the message, and if a message should be filtered based on the permissions of the sender. It also applies the sender's chat colour.
A RoseMessage object is then created, passing in the sender, channel, and message. Then the rules are applied. At this stage, the message is changed to be filtered.

Before a message is parsed, checking if isBlocked() may be useful to see if the filter system caught anything that should not be sent. The function getFilterType() can provide you with the reason why the message was filtered.

After this, the message is parsed with a viewer and format. This is first parsed for the console, so that the console receives the message, but also so that the tokens are generated and cached, allowing for further optimization.
RoseChat will, essentially, cache part of the message so it does not needed to be parsed every time for every player, only when the content should change, such as a per-player placeholder.
A format is not needed, and null can be passed.

There are several parse functions in the RoseMessage class.
The first simply parses the message as it should be seen in-game.

BaseComponent[] parse(RosePlayer viewer, String format)

The second treats the message as if it was sent from Discord, converting Discord formatting to Minecraft. A discord id can be passed to allow messages to be deleted in Discord.

BaseComponent[] parseMessageFromDiscord(RosePlayer viewer, String format, String discordId)

The third treats the message as if it was sent to Discord, converting Minecraft formatting to Discord.

BaseComponent[] parseMessageToDiscord(RosePlayer viewer, String format)

The fourth treats the message as if it was going to be sent to a Bungee server.

BaseComponent[] parseBungeeMessage(RosePlayer viewer, String format)

The final method allows a MessageParser to be specified, and a discord id too, if needed..

BaseComponent[] parse(MessageParser parser, RosePlayer viewer, String format, String discordId) {

Now that the message is parsed, functions such as getTaggedPlayers() become available to use.

Message Parsers

A message parser is a way of deciding what to do with a message when it is parsed.
Typically, this consists of combining multiple tokenizers to create a final message.
An example of a MessageParser can be seen here.
This MessageParser, like others, splits a format and tokenizes the prefix, message, and suffix, then combines them to deliver the final message.
A MessageParser is simply called when the message is parsed, so anything can be done to the message.