You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,7 @@ As mentioned above, MCP implements compatibility layers for Simple Chat-Processo
35
35
I want to emphasise here that I am only implementing API compatibility, not feature pairity! In addition you can switch the transport method from using SayText2 packets to TextMsg packets (system/plugin messages).
36
36
Simple Chat-Processor also had the quirk that the Post call was only called if the message was changed. I have an optional fix for that in place, that you can enable in the config as well.
37
37
The compatibility options for `Custom-ChatColors` and `HexTags` will try to read the clients chat colors back into MCP for other plugins to access.
38
+
In case you still encounter weird issues with external plugins that reliably format chat messages manually or through a compatibility layer, you can turn on the `External Formatting` option and check if things improve.
38
39
39
40
By Default MCP will also perform input sanitation that brings chat messages back in-line with vanilla behaviour. Native colors are not actually allowed by games by default, neither are empty messages.
40
41
The `Trim All Whitespaces` option will catch unicode spaces as well, to properly block messages without content.
@@ -53,6 +54,7 @@ The config can be found at `addons/sourcemod/config/metachatprocessor.cfg`:
53
54
"Custom-ChatColors" "1"
54
55
"HexTags" "1"
55
56
"Fix Post Calls" "0"
57
+
"External Formatting" "0"
56
58
}
57
59
// Transport defines the message channel/type. You should probably keep it at SayText.
0 commit comments