Summery

When writing configuration for the plugin you may run into a small issue. Let's say that you want to use the message keyword to send a message to a player, but you want to add proper punctuation because you’re not a monkey. Because of that, you find yourself adding commas to the message text, but there is an issue, the interpreter tells you that you provided invalid arguments. This is because when a comma is placed in a keyword’s arguments, the interpreter thinks it means you want to add a new argument, but in this case, you just want to add a normal comma. This is where the new escape character comes in. By placing a backslash (\) before the comma you are telling the interpreter that you want the comma to act as a normal character and to “escape” all of its special functionality. If you wrote the keyword:

- ‘message(?player, Hello, my name is Bob.)’

It would throw an error, but if you wrote it like this:

- ‘message(?player, Hello\, my name is Bob.)’

It would work perfectly fine and when the message is parsed the backslash is removed so the final message sent to the player would be:

Hello, my name is Bob.

Features

• Added the escape character to all keywords for commas
• Added to the randomability keyword for semicolons