Chat-Processor fails to load if compatibility for it is enabled

[kmak7]

SourceMod: 1.12.0.7146 MetaChatProcessor: 24w24a Chat-Processor: 2.2.3

Setting "Drixevel" "1" in Compatibility causes chat-processor to error:

L 10/18/2024 - 14:05:28: [SM] Exception reported: Failed to create native "ChatProcessor_GetFlagFormatString", name is probably already in use L 10/18/2024 - 14:05:28: [SM] Blaming: chat-processor.smx L 10/18/2024 - 14:05:28: [SM] Call stack trace: L 10/18/2024 - 14:05:28: [SM] [0] CreateNative L 10/18/2024 - 14:05:28: [SM] [1] Line 78, chat-processor.sp::AskPluginLoad2 L 10/18/2024 - 14:05:28: [SM] Failed to load plugin "chat-processor.smx": unexpected error 23 in AskPluginLoad callback.

Disabling compatibility makes chat-processor load again and work together with mcp but doubles messages in chat

[DosMike]

did you remove dirxevel's chat processor before loading meta chat processor?

[kmak7]

No because I thought you're supposed to have them both if you want to run hextags as its required by it but I see it don't work that way and hextags still load if with only mcp as processor. Removed other chat processors and only left mcp.

In config file I now have these set to 1 "Drixevel" "1" "HexTags" "1"

However hextags don't seem to get parsed properly when using mcp and prints to chat something like this: {teamcolor}heavy{default} : {aliceblue}dasdsa

[DosMike]

The compat settings are for replacement layers, because multiple chat processors can not really run at the same time. It duplicates messages as you have seen. If you want to use HexTags, I recommend to remove Drixevel's chat processor and enable Drixevel compat, keep the HexTags plugin (e.g. setting the MCP config value to 0). With that, MCP should mimic Drixevel's chat processor to a degree that allows HexTags to do it's thing. (Just fyi, enabling the HexTags would be for cases where you'd not want to use HexTags features, but at the same time use a different plugin that uses HexTags functionality)

If you still have issues with that set up, please report back, and have a nice weekend :)

[kmak7]

I misunderstood how this works. Very impressive. I now set it up like this:

Chat processors: Only mcp as processor Hextags: hextags are loaded (version: 2.12)

Compatibility settings in mcp: "SCP Redux" "0" "Drixevel" "1" "Cider" "0" "Custom-ChatColors" "0" "HexTags" "0" "Fix Post Calls" "0" "External Formatting" "0" // I tried enabling this but didn't help

Result in chat with this setup:

[DosMike]

Can you show me the whole config? I haven't used HexTags in a while, so I'd like to test it (That would be MCP and HexTags config then)

[kmak7]

mcp config: https://pastebin.com/jRWV7Nfs hextags config: https://pastebin.com/Mt4R4LxH

Only reason im using hextags instead of mcp tags is because of feature where you can use multiple colors with "ChatTag" you can see some examples in hextags config