Proposed Message Standardisation

[xoft]

The prefixes WILL be configurably optional. And updating will be needed from time to time anyway.

[NiLSPACE]

They will be configureably in the function or in a config file?

[tigerw]

In a configuration file, of course.

For the plugin side of things, I'll just add extra SendMessage/BroadcastChat functions, not going to change the existing ones. Then, I'll submit PRs to WorldEdit to change everything to use appropriate functions.

I think it would be the easiest without exploding all plugins to bits or doing manual bindings.

Exploding all plugins to bits. heh

heh

[NiLSPACE]

But is there a way to send a message to a player without any prefixes even if it is set in the config? Because as an example if you would use /help you would get a screen like:
[INFO] Page 1 out of 15.
[INFO] '-' means no prefix, '~' means a value is required.
[INFO] //copy - Stuff here
[INFO] //cut - Other stuff here
[INFO] //drain - Some more stuff
[INFO] //ex - Guess what comes here.
[INFO] //ext - Even more stuff.

I mean, say for yourself. That looks horrible.

[bearbin]

Looks fine to me. Anyway, Player:SendMessage would still work, right?

[NiLSPACE]

Why not like this:

void SendMessage(const AString & a_Message, int a_PrefixType = ptNone);

So for default it wouldn't have any prefix at all.

[tonibm19]

That wouldn't break plugins, right?

[tigerw]

Mah gawsh peeps.

SendMessage sends a raw message to players, and server does not format it. Nothing is changed for this.
For SendMessageXXX, server performs formatting. These are the new functions.

That shouldn't break anything

[NiLSPACE]

Thanks I was getting worried because xoft said "SendMessage() might be marked as obsolete and might be removed later on."

[tigerw]

Oh. Xoft, is what I said what you intended to do? It seems to make our plugin writers happy?