After installing BetterSay, I can no longer use \n to make a new line or use 2 x spaces or more.
Not respecting newline and double spaces
That isn't handled or restricted at all in any way with this plugin. The message you enter is what is sent to Rust directly and handled Rust.
So why can I make new lines in say with \n when vanilla, and with this plugin the \n is displayed in chat and no new line is made ?
When I use the ServerChat plugin I can use \n to make new line ?
or at least when using say through a plugin that is the difference.
Most likely because of the method used for chat sending.
To clarify, when I use GUIShop to sell VIP and make GUIShop do a command that uses say, the \n makes a new line and I can use lots of spaces to tweak how the say is diplayed in chat.
As soon as I install BetterSay, all that doesn't work anymore, the \n is just displayed in chat and multiple spaces are converted to a single space.
That may be the case as this plugin overrides the default say command, but it isn't what is preventing that from working as it just passes what you give it to other methods that do handle the text.
Dammit Wulf... stop speaking russian.... I do not understand it xD
Anyway, I understand that it depends on the method used to display the say in chat.
I'm just gonna have to stick with ServerChat then.
Server Chat uses an entirely different method, and doesn't override the "say" command from Rust. It basically just intercepts an existing message and reformats it.
Better Chat overrides the "say" command in Rust, grabs the string of text from Rust, and sends it using the same method that Server Chat does.
So the only real varying factor there is what it is getting the text from (Rust) and how it formats it; so the issue is going to be either the formatter or what Rust provided to the plugin.
Better Chat overrides the "say" command in Rust, grabs the string of text from Rust, and sends it using the same method that Server Chat does.
So the only real varying factor there is what it is getting the text from (Rust) and how it formats it; so the issue is going to be either the formatter or what Rust provided to the plugin.
So I'm guessing it's when BetterChat grabs the text string that the \n and multiple spaces formatting gets lost.
Anyway, thanks for the explanation, it made sense. :o)
It's possible that arg.Args from Rust is where it gets lost, else the universal formatter in Oxide; would need to be tested.