MatterAMXX: Chat relay between many services [Includes API]
 

https://i.imgur.com/IDxyLUk.png
[ALL] MatterAMXX
Author: Gabe Iggy
Version: 1.5
Powered by Matterbridge, MatterAMXX is a plugin for AMXX that allows simple bridging between your game servers, Mattermost, IRC, XMPP, Gitter, Slack, Discord, Telegram, and more.

https://i.imgur.com/rQdVuIx.png

Description

Using Matterbridge API, this plugin allows you to bridge your game server with a Matterbridge installation, relaying messages from/to a growing number of protocols.

You can also bridge multiple servers together so the players can chat between each one.


Protocols natively supported in Matterbridge

• Mattermost
• IRC
• XMPP
• Gitter
• Slack
• Discord
• Telegram
• Rocket.chat
• Matrix
• Steam (Bugged for now)
• Twitch
• Ssh-chat
• WhatsApp
• Zulip
• Keybase

Tested Protocols

• Discord
• Matrix
• Telegram

Dependencies

This plugin requires the following to work:

• GoldSrc Rest In Pawn (gRIP)
• A working Matterbridge installation

Supported Games

This plugin is supposed to be mod agnostic. All official games should work out of the box

• Half-Life
• Counter-Strike
• Condition Zero
• Opposing Force
• Ricochet
• Day of Defeat
• Team Fortress Classic
• Deathmatch Classic

Kill feed feature will also work in mods where a proper hamdata.ini table is provided

• The Specialists
• Sven Co-op

Tested Games

• Half-Life
• Ricochet
• Sven Co-op
• The Specialists

Installation Instructions

• Do not download the .amxx file from here. As the webcompiler lacks the includes needed to generate the plugin correctly.
• Download all requirements, plus the .sma file.
• Place include files in the /scripting/includes directory.
• Compile the plugin and install the newly generated .amxx file. (Remember to install the latest version of GRIP in your server)
• Copy the matteramxx.txt and matteramxx_old.txt files to the /data/lang directory in your AMXX installation.

Setting up MatterAMXX

This quickstart guide assumes you already have a working Matterbridge installation.

Open your matterbridge.toml file and add the following lines:

Where "myserver" is goes the name of the relay, you can put anything.

Find your gateway where you want to relay the messages.
Where cstrike is goes the gateway name. By default is the mod's gamedir (cstrike for Counter-Strike, valve for Half-Life, etc) but you can change it using cvars, you can add more gateway.inout entries depending on how many protocols do you want to relay messages.


Avatar Spoofing

It's possible to set up avatars for each user on protocols that support it. Unfortunately, due to limitations of AMXX and the GRIP module, user info from the Steam API can't be retrieved because it gets truncated.

However, you can host this simple PHP script to query for avatars to be used in this plugin, you just need a Steam API Key that you can obtain from the Steam Web API website.



This will also cache each avatar and they will be deleted after a while.

Remember to create the /avatars folder! The script won't do it for you.


API

The API allows other plugins to use MatterAMXX features. Just include the matteramxx.inc file in your plugin and it should work immediately.



Remember that the plugin requires the latest version of MatterAMXX to be running in the server.

Click here to check out the MatterAMXX subplugins.


Click here to check out servers using this plugin.

Console Variables

• amx_matter_enable
  • Enables the plugin.
  • Default: 1
• amx_matter_bridge_protocol
  • Protocol of where the bridge is located.
  • Default: "http"
• amx_matter_bridge_host
  • Host of where the bridge is located.
  • Default: "localhost"
• amx_matter_bridge_port
  • Port of where the bridge is located.
  • Default: "1337"
• amx_matter_system_avatar
  • URL pointing to a picture that will be used as avatar image in system messages. (In protocols that support it)
  • Default: [empty string]
• amx_matter_autogenerate_avatar
  • URL pointing to a picture that will be used as avatar image in unauthenticated player messages. (In protocols that support it)
  • This will mostly affect LAN servers, ID_PENDING cases, cases where Steam might be down and other specific cases.
  • This is generated on the user's nickname, so you must provide a link to Gravatar, Identicons, etc.
  • Default: [empty string]
• amx_matter_player_avatar
  • URL pointing to a picture that will be used as avatar image in player messages. (In protocols that support it)
  • Note that this is dynamic based on the user's Steam ID64, if it can't be retrieved the message won't have any avatar.
  • Upload the PHP file I provided to your file server and use it in this cvar like "http://localhost/avatars/get_avatar.php?steamid=%s".
  • See "Avatar Spoofing" for more information.
  • Default: [empty string]
• amx_matter_bridge_gateway
  • Gateway name to connect.
  • Default: [varies, depends on the game]
• amx_matter_bridge_token
  • String token to authenticate, it's recommended that you set it up, but it will accept any connection by default.
  • Default: [empty string]
• amx_matter_bridge_incoming
  • Enables incoming messages (protocols to server).
  • Default: 1
• amx_matter_bridge_incoming_ignore_prefix
  • Messaging matching this in the beggining of the message will be ignored by the plugin.
  • It supports regex.
  • Plugins using the API can still catch these messages.
  • Default: "!"
• amx_matter_bridge_incoming_dont_colorize
  • By default it will colorize any message with a simple format (green username) but if set to 1 it will not colorize anything, leaving the admin to handle any colorization in the matterbridge.toml file.
  • It will only affect Counter-Strike.
  • Default: 0
• amx_matter_incoming_update_time
  • Specifies how many seconds it has to wait before querying new incoming messages.
  • Performance wise is tricky, lower values mean the messages will be queried instantly, while higher values will wait and bring all messages at once, both cases may cause overhead. Experiment and see what's ideal for your server.
  • No effect if amx_matter_bridge_incoming is 0.
  • Default: 3.0
• amx_matter_bridge_outgoing
  • Enables outgoing messages (server to protocols).
  • Default: 1
• amx_matter_bridge_outgoing_display_map
  • Display the current map at the start of every session.
  • Default: 1
• amx_matter_bridge_outgoing_strip_colors
  • Strip color codes from player names.
  • It will only affect Half-Life and Adrenaline Gamer.
    • No effect in other games.
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default: 1
• amx_matter_bridge_outgoing_system_username
  • Name of the "user" when relying system messages.
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default: [your server name]
• amx_matter_bridge_outgoing_chat_mode
  • Select which chat messages you want to send.
    • 1 = All chat
    • 2 = Team chat
  • You must sum the values you want to send. For example, if you want to send everything the value must be 3.
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default: 3
• amx_matter_bridge_outgoing_chat_zwsp_at
  • This controls if the plugin should add a ZWSP character after the at symbol (@) to prevent unintentional or malicious pinging.
  • No effect if amx_matter_bridge_outgoing_chat is 0.
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default: 1
• amx_matter_bridge_outgoing_chat_no_repeat
  • Implement basic anti-spam filter. Useful for preventing taunt binds from sending multiple times.
  • No effect if amx_matter_bridge_outgoing_chat is 0.
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default: 1
• amx_matter_bridge_outgoing_kills
  • Transmit kill feed.
  • It's recommended that you to turn it off on heavy activity servers (Like CSDM/Half-Life servers with tons of players)
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default 1
• amx_matter_bridge_outgoing_join
  • Transmit when people join the server.
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default: 1
• amx_matter_bridge_outgoing_join_delay
  • Specify how many seconds the server has to wait before sending Join messages..
  • No effect if amx_matter_bridge_outgoing_join is 0.
  • Default: 30.0
• amx_matter_bridge_outgoing_quit
  • Transmit when people leave the server.
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default: 1
• amx_matter_bridge_outgoing_quit_ignore_interm ission
  • Specify if the server shouldn't send quit messages if the server reached the intermission state.
  • No effect if amx_matter_bridge_outgoing_quit is 0.
  • Default: 0
• amx_matter_bridge_outgoing_joinquit_count
  • Display playercount on each Join/Quit message.
  • No effect if both amx_matter_bridge_outgoing_quit and amx_matter_bridge_outgoing_join are 0.
  • Default: 1
• amx_matter_bridge_retry_delay
  • In seconds, how long the server has wait before retrying a connection when it was interrupted.
  • No effect if amx_matter_bridge_outgoing is 0.
  • Default: 3.0

Change Log

• 1.5
  Main Changes
  • Deprecated the usage of amx_matter_bridge_url, users are encouraged to use the new cvars amx_matter_bridge_protocol, amx_matter_bridge_host and amx_matter_bridge_port.
  • The plugin will no longer try to query the incoming protocol, it will now respect the format specified on the matterbridge.toml file.
  • Introduced system messages, a message marked as "system message" won't be printed to other game servers.
  • User's SteamID is now included in the Matterbridge payload.
  • Added cvar amx_matter_bridge_incoming_dont_colorize. Only for Counter-Strike, by default it will colorize any message with a simple format (green username) but if set to 1 it will not colorize anything, leaving the admin to handle any colorization in the matterbridge.toml file.
  • Fixed a lot of errors related to Counter-Strike and rendering text with colors.
  • Removed amx_matter_bridge_outgoing_chat and amx_matter_bridge_outgoing_chat_team cvars, these will now be managed by a single cvar: amx_matter_bridge_outgoing_chat_mode. Add the sum of the desired behavior:
    
    • Send all chat = 1
    • Send team chat = 2
    If you want to send everything, you must put 3.
    
  • Added amx_matter_bridge_incoming_ignore_prefix. Useful to ignore bot commands.
  • Server messages now support multi language.
  • Quotes no longer get removed from players' messages.
  • Made Sven Co-op use the alternative language file, the game doesn't support rendering "%" in chat.
  Sub plugin changes
  
  
  • API
    
    • Added support for system messages.
    • matteramxx_print_message now includes the userid field.
    • Plugins now can specify an alternative Matterbridge gateway.
    • matteramxx_send_message is now a native.
  • CONSOLE
    
    • Console output won't be escaped if amx_matter_rcon_code_block is on.
    • Ignore commands coming from other game servers.
    • It will now use the user id instead of the name for admin checking.
    • Removed support for listip/listid commands, changed error message for a better explanation.
  • LAG CHECKER
    
    • Fix missing localization strings.
    • Fixed using wrong lag percent formula.
• 1.4
  • The matteramxx_print_message() forward now includes the user's avatar and protocol.
  • Fixed the Killed Hamsandwich hook in TFC that was not working as it should.
  • Added multilingual support.
    • Many thanks to the language contributors:
      • Romanian: tom .
      • Turkish: Snake.
      • Albanian: thEsp
      • Russian: Natsheh
  • The following console variables are now protected:
    • amx_matter_bridge_token
    • amx_matter_bridge_gateway
    • amx_matter_bridge_url
    • amx_matter_player_avatar
    • amx_matter_autogenerate_avatar
    • amx_matter_system_avatar
  • Added new console variable: amx_matter_bridge_outgoing_chat_zwsp_at
    • This controls if the plugin should add a ZWSP character after the at symbol (@) to prevent unintentional or malicious pinging.
  • Added new console variable: amx_matter_bridge_incoming_chat_protocol
    • This controls if the plugin should add the message protocol in incoming messages.
  • The plugin (and subplugins) now pause when disabled.
  • Code cleanup.
  • New subplugins released to showcase the power of the MatterAMXX Api:
    • MatterAMXX Lagchecker
      • This plugin will notify a configured user if the CPU/FPS increase/fall past/below a defined threshold.
      • This will be triggered if any user says "lag".
      • This will also output the current values to the users notifying them if the server is not lagging.
      • Requires Orpheu and Orpheu Signatures.
    • MatterAMXX RCON
      • This plugin will allow you to control the server's console from any messaging protocol, with full console output.
      • You can configure which users are allowed to send commands to the server console.
      • Requires Orpheu and Orpheu Signatures.
• 1.3.2
  • Extended buffers to allow more complex messages to be sent/received
  • Leave messages now work in 1.8.2
• 1.3.1
  • Tried to fix a case where multiple pending messages would cause them to not send due to AMXX limits. Further testing is required
  • Fixed a bug where it would always see any ID as a valid Steam ID
• 1.3
  • Added new console variable: amx_matter_incoming_update_time
    • Specify how many seconds the server has to wait before querying new messages
  • Decreased default value of amx_matter_bridge_outgoing_join_delay (from 30.0 to 15.0)
  • Fixed a bug where it would not display when a new map has started
  • Added new debug information (requires the plugin to be running on debug mode)
    • Currently it only supports outgoing messages
  • Added new console variable: amx_matter_autogenerate_avatar
    • Allows avatar support for unauthenticated users (LAN, Pending IDs and other uses I won't mention)
    • You need to supply an URL to generate an image from Text, where %s is a URL parsed nickname of the user
  • MatterAMXX will now display the external username in color (only if the game is a version Counter-Strike)
• 1.2.1
  • Fixed a bug where the attacker and victim were reversed in the non-HamSandwich version.
  • Fixed a bug where the leave message should show the player count before the player actually left.
• 1.2
  • Added new console variable: amx_matter_bridge_outgoing_join_delay
    • Specify how many seconds the server has to wait before sending Join messages
  • Added new console variable: amx_matter_bridge_outgoing_quit_ignore_interm ission
    • Specify if the server shouldn't send quit messages if the server reached the intermission state
  • Added new console variable: amx_matter_bridge_outgoing_display_map
    • Display the current map at the start of every session
  • Added new console variable: amx_matter_bridge_outgoing_joinquit_count
    • Display playercount on each Join/Quit message
  • Added API support!
    • The API allows other plugins to use MatterAMXX features
    • New stock: matteramxx_send_message
    • New forward: matteramxx_print_message
  • The plugin can now be set up to compile without the HamSandwich module.
  • Adjusted some code, using newer DEFINEs.
• 1.1
  • Join and Quit messages will only be sent after the user has actually joined the server (putinserver). This will prevent Join/Leave spam.
  • Added new console variable: amx_matter_system_avatar
    • Url pointing to a picture that will be used as avatar image in system messages. (In protocols that support it)
  • Added new console variable: amx_matter_player_avatar
    • Url pointing to a picture that will be used as avatar image in player messages. (In protocols that support it).
    • Note that this is dynamic based on the user's Steam ID64, if it can't be retrieved the message won't have any avatar.
  • Added new console variable: amx_matter_bridge_outgoing_strip_colors
    • Strip color codes from player names.
    • It will only affect Half-Life and Adrenaline Gamer.
  • Added new console variable: amx_matter_bridge_outgoing_chat_no_repeat
    • Implement basic anti-spam filter. Useful for preventing taunt binds from sending multiple times.
  • Minor code cleanup
• 1.0
  • Initial Release

Credits

• 42wim
  Main developer of Matterbridge.
• Michael Wieland
  His MatterBukkit plugin for Minecraft inspired me to create this.
• Th3-822
  Helped me finding some bugs.
• tom .
  Romanian translator.
• Snake.
  Turkish translator.
• thEsp
  Albanian translator.
• Natsheh
  Russian translator.
• MaNa
  Done a lot of testing on his CS1.6 server. The quick release of MatterAMXX 1.5 wouldn't be possible without him.

Re: MatterAMXX
 

So basically, I can register the whatsapp with the server and when someone join or leave the server, a message is sent to the group or person on whatsapp?

Re: MatterAMXX
 

You can relay messages between WhatsApp and the server, yes.

Re: MatterAMXX
 

Based on feedback a new version was released:

• 1.1
  • Join and Quit messages will only be sent after the user has actually joined the server (putinserver). This will prevent Join/Leave spam.
  • Added new console variable: amx_matter_system_avatar
    • Url poiting to a picture that will be used as avatar image in system messages. (In protocols that support it)
  • Added new console variable: amx_matter_player_avatar
    • Url poiting to a picture that will be used as avatar image in player messages. (In protocols that support it).
    • Note that this is dynamic based on the user's Steam ID64, if it can't be retrieved the message won't have any avatar.
  • Added new console variable: amx_matter_bridge_outgoing_strip_colors
    • Strip color codes from player names.
    • It will only affect Half-Life and Adrenaline Gamer.
  • Added new console variable: amx_matter_bridge_outgoing_chat_no_repeat
    • Implement basic anti-spam filter. Useful for preventing taunt binds from sending multiple times.
  • Minor code cleanup

It's now possible to set up avatars for each user on protocols that support it. Unfortunately, due to limitations of AMXX and the GRIP module, user info from the Steam API can't be retrieved because it gets truncated.

However, you can host this simple PHP script to query for avatars to be used in this plugin, you just need a Steam API Key that you can obtain from the Steam Web API website.

Visit https://pastebin.com/p9aBm1pS to get the script (Because CloudFlare is blocking the script from being posted here)

This will also cache each avatar and they will be deleted after a while.

Remember to create the /avatars folder! The script won't do it for you.

Re: MatterAMXX
 

Impressive especially for GoldSrc. Formally API like this I thought could only be done via Source. Thanks Iggy!

Re: MatterAMXX
 

amazing, will try this in whatsapp soon, thanks

Re: MatterAMXX
 

Thanks for the kind comments.

I have the following on the roadmap:

• Notify admins that a message failed to relay to Matterbridge.
• Display SteamID (Or IP, if you want) in the user message.
• A list of messages that will be ignored if typed in the server (Stuff like nextmap, timeleft, etc).

Re: MatterAMXX
 

how can i set up to send notifications about bans on whatsapp, when someone is banned or unbanned?
is it possible?

Re: MatterAMXX
 

It's definitively possible for other plugins to send messages to your protocols (For it, I have to implement a simple API in MatterAMXX).

However, you would still need to edit your plugins to do that.

Re: MatterAMXX
 

Looks like the plugin crashes on Ricochet due to it not having hamdata.ini entries, even if you disable the streaming of kill feed. (The plugin crashes upon detecting it has a Ham function, not when executing it)

Current roadmap:

• Implement API so other plugins can send messages via MatterAMXX Somewhat done. Need to know why I can't read the incoming message from the other plugin. Sending works fine.
• Implement simple compile defines to decide if you want to compile with HamSandwich support. (Search another way to detect death of players? Needs to be mod agnostic tho') Done (Using DeathMsg event)
• Add a list of words that would be ignored when typed in the chat (Stuff like "nextmap", "rtv", etc.)
• I would also like to add some checks to prevent Join messages on the first N seconds the map started, and Quit messages when we reached the intermission, to further prevent Join/Leave spam. Done
• Of course add a message when the map changed, should be very easy. Done as well

Re: MatterAMXX
 

Hello, a new version was released

• 1.2
  • Added new console variable: amx_matter_bridge_outgoing_join_delay
    • Specify how many seconds the server has to wait before sending Join messages.
  • Added new console variable: amx_matter_bridge_outgoing_quit_ignore_interm ission
    • Specify if the server shouldn't send quit messages if the server reached the intermission state
  • Added new console variable: amx_matter_bridge_outgoing_display_map
    • Display the current map at the start of every session
  • Added new console variable: amx_matter_bridge_outgoing_joinquit_count
    • Display playercount on each Join/Quit message
  • Added API support!
    • The API allows other plugins to use MatterAMXX features
    • New stock: matteramxx_send_message
    • New forward: matteramxx_print_message
  • The plugin can now be set up to compile without the HamSandwich module.
  • Adjusted some code, using newer DEFINEs.

Minor revision to 1.2

• 1.2.1
  • Fixed a bug where the attacker and victim were reversed in the non-HamSandwich version.
  • Fixed a bug where the leave message should show the player count before the player actually left.

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Hello, a new version was released

1.3

• Added new console variable: amx_matter_incoming_update_time
  • Specify how many seconds the server has to wait before querying new messages
• Decreased default value of amx_matter_bridge_outgoing_join_delay (from 30.0 to 15.0)
• Fixed a bug where it would not display when a new map has started
• Added new debug information (requires the plugin to be running on debug mode)
  • Currently it only supports outgoing messages
• Added new console variable: amx_matter_autogenerate_avatar
  • Allows avatar support for unauthenticated users (LAN, Pending IDs and other uses I won't mention)
  • You need to supply an URL to generate an image from Text, where %s is a URL parsed nickname of the user
• MatterAMXX will now display the external username in color (only if the game is a version of Counter-Strike)

Current TO-DOs:

• Display scoreboard at the end of each map
• Create ignore message list
• Call an admin in-game

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Hello, a minor revision to 1.3 was released

• 1.3.1
  • Tried to fix a case where multiple pending messages would cause them to not send due to AMXX limits. Further testing is required
  • Fixed a bug where it would always see any ID as a valid Steam ID

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Hello, a minor revision to 1.3 was released

• 1.3.2
  • Extended buffers to allow more complex messages to be sent/received
  • Leave messages now work in 1.8.2

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Hello, a new version of the plugin was released.

• 1.4
  • The matteramxx_print_message() forward now includes the user's avatar and protocol.
  • Fixed the Killed Hamsandwich hook in TFC that was not working as it should.
  • Added multilingual support.
    • Many thanks to the language contributors:
      • Romanian: tom .
      • Turkish: Snake.
      • Albanian: thEsp
      • Russian: Natsheh
  • The following console variables are now protected:
    • amx_matter_bridge_token
    • amx_matter_bridge_gateway
    • amx_matter_bridge_url
    • amx_matter_player_avatar
    • amx_matter_autogenerate_avatar
    • amx_matter_system_avatar
  • Added new console variable: amx_matter_bridge_outgoing_chat_zwsp_at
    • This controls if the plugin should add a ZWSP character after the at symbol (@) to prevent unintentional or malicious pinging.
  • Added new console variable: amx_matter_bridge_incoming_chat_protocol
    • This controls if the plugin should add the message protocol in incoming messages.
  • The plugin (and subplugins) now pause when disabled.
  • Code cleanup.
  • New subplugins released to showcase the power of the MatterAMXX Api:
    • MatterAMXX Lagchecker
      • This plugin will notify a configured user if the CPU/FPS increase/fall past/below a defined threshold.
      • This will be triggered if any user says "lag".
      • This will also output the current values to the users notifying them if the server is not lagging.
      • Requires Orpheu and Orpheu Signatures.
    • MatterAMXX RCON
      • This plugin will allow you to control the server's console from any messaging protocol, with full console output.
      • You can configure which users are allowed to send commands to the server console.
      • Requires Orpheu and Orpheu Signatures.

Re: MatterAMXX: Chat relay between many services [Includes API]
 

[ALL] MatterAMXX Plugins

The MatterAMXX API allow plugin creators to capture and send messages via MatterAMXX, you can see the plugin in action in the following plugins!

MatterAMXX Lag Checker
https://i.imgur.com/GX0Kwdu.png

This plugin will notify a configured user if the CPU/FPS increase/fall past/below a defined threshold. Triggered if someone says "lag" on the server.

If the user says "lag" and the server is not lagging he will be notified along with the FPS and CPU values.

Requirements:

• The latest version of MatterAMXX
• Orpheu
• OrpheuSignatures

Console Variables:

• amx_matter_lagchecker_enabled
  Enables the plugin.
  Default 1.
• amx_matter_lagchecker_ping_this_person
  Determines the person/s who should be pinged on alert.
  Should be a pingable string, for example "@username" for Telegram or "<@12345678910>" for Discord ID.
  Default [blank string].
• amx_matter_lagchecker_cpu_threshold
  If the CPU goes over this percentage, an alert should be sent.
  Default 75.
• amx_matter_lagchecker_fps_threshold
  If the FPS goes below this percentage (based on sys_ticrate), an alert should be sent..
  Default 25.

Changelog:

• 1.4
  • Initial Release

MatterAMXX RCON
https://i.imgur.com/3jSroQD.png
Control the server from anywhere.

This plugin will allow you to control the server's console from any messaging protocol, with full console output.

You can configure which users are allowed to send commands to the server console.

Requirements:

• The latest version of MatterAMXX
• Orpheu
• OrpheuSignatures

Configuration:

By default the plugin won't accept commands from any user, to do so you need to edit the matteramxx_rcon_accounts.ini file in your AMXX config folder.
The format is username§protocol. Both are required to disallow impersonation.

Console Variables:

• amx_matter_rcon_enable
  Enables the plugin.
  Default 1.
• amx_matter_rcon_dont_ignore_list
  Determines if the plugin should NOT ignore the master account list and accept commands from any user
  Dangerous! A badly configured bridge will allow to anyone to get access to the game console. Set it to 1 unless you really know what are you doing.
  Default 1.
• amx_matter_rcon_prefix
  The bot prefix to send commands to the console
  Default "!rcon "
• amx_matter_rcon_hide_cvars
  Determines if the plugin should redact protected cvars. (like rcon_password)
  Default 1.
• amx_matter_rcon_hide_ips
  Determines if the plugin should redact IPs.
  Default 1.
• amx_matter_rcon_code_block
  Determines if the plugin should send the output in a code block
  Note that not every protocol supports this feature
  Default 1.

Changelog:

• 1.4
  • Initial Release

Installation instructions

• Download all requirements, plus the .sma file.
• Place include files, in the /scripting/includes directory.
• Compile the plugin and install the newly generated .amxx files. (Remember to install the latest version of MatterAMXX in your server)

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Moving the conversation from another thread to help other people set up the plugin.

amx_matter_bridge_url is where you are hosting the matterbridge instance.

For example: "http://(ipofyourserver):27010/"

If you're hosting MatterBridge on the same machine as your gameservers you can use localhost ("http://localhost:27010/"). If not, you must use the external IP of the server that's hosting MatterBridge.

Change BindAddress to 0.0.0.0, it must be a local, this makes it so the API will be listening to the local IP.

You can use any port providing is it not being used.

For reference I will put my own configuration of one of my servers:
matterbridge.toml
cvars:

Re: MatterAMXX: Chat relay between many services [Includes API]
 

I tried out http://localhost:80, http://localhost:27010, http://localhost:27020, and my IP addresses as bridge, but I was receiving the error: "[MatterAMXX] Invalid message arrived, ignoring."

I set the token for both servers and gateway was set to cstrike. Maybe my bridge is the fault here, should it be an accessible link for the bridge or it's fine as long as it's accessing the bridge from the server?

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Can you connect to your bridges via a web browser?

If they're protected by a token you should get a "missing key in request header" message.

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Yeah, the matterbridge.toml and executable are accessable through the web, but the same error message pops up. I've changed the BindAddress to 0.0.0.0:27010 and 27020. My gateway name's cstrike, and my bridge is set to http://<IP excluding Port>/<Directory of MatterBridge>/ .

Re: MatterAMXX: Chat relay between many services [Includes API]
 

most people nowdays use rehlds, so we can`t use Orpheu, can you make one version for rehlds?

Re: MatterAMXX: Chat relay between many services [Includes API]
 

I added you to Steam but it seems our timezones do not match as I always find you offline.

I noticed your bridge is set to http://<IP excluding Port>/<Directory of MatterBridge>/, are you reffering to the cvar amx_matter_bridge_url? It must in be http://<IP including Port>. There's an example in the default value.

Hello, my main Setup uses ReHLDS and all the plugins work. You can check the "ReHLDS" branch of OrpheuSignatures.
https://github.com/GabeIggy/OrpheuSi...es/tree/ReHLDS

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Hey Gabe, my servers are currently down, and I was working on getting them back. I'll get in touch as soon as things get better. Thanks for helping out again :)

Re: MatterAMXX: Chat relay between many services [Includes API]
 

I can't get pass the matterbridge install. I am running debian linux and used snap to install matterbridge, but the instructions go cold after not sure what to do from there. Any idea where it installed as I can't issue the start up commands

Re: MatterAMXX: Chat relay between many services [Includes API]
 

.toml is the configuration file, you need to run the executable file.

Easier way to do it is to download the binary file for your OS (assuming it's 64-bit Linux)
Making it executable
Then running it

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Thanks.

I got my matterbridge install going. I can't get the module loaded on amxmodx 1.9.

It's placed in the addons/amxmodx/modules folder but it wont auto load. I have also placed the word grip inside the modules.ini and rebooted the server it still won't load.

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Which version of gRIP are you using? For some reason, the repo owner marked a 0.0.0 "test" version as latest release, this doesn't work.

Last stable release is 0.1.5 which you can download here:
https://github.com/In-line/grip/releases/tag/0.1.5-beta

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Was using "grip-0.0.0.0-test-i686-unknown-linux-gnu". It loads now with the newer version you linked.

I get the message below in my console. I have also pasted my matterbridge.toml config. The bot is connect to irc but it's not relaying chat. Is there something wrong in my config?

Re: MatterAMXX: Chat relay between many services [Includes API]
 

What's the value of your amx_matter_bridge_url cvar?

Re: MatterAMXX: Chat relay between many services [Includes API]
 

my ip and port:1337.

Matterbridge is also launched on port 1337.

Is apache required for this to work?

-update

I also tried with port 27015 and cross referenced the config you posted here. No luck in getting it going.

current cvar:
"amx_matter_bridge_url" is "http://localhost:27015"

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Managed to replicate the error you have in my installation.

This is caused if the cvar value is not in quotes.

Change it to
Apache is not required.

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Thanks got it going. After I added my discord settings to the config it started working.

Re: MatterAMXX: Chat relay between many services [Includes API]
 

New version released: 1.5

Main Changes

• Deprecated the usage of amx_matter_bridge_url, users are encouraged to use the new cvars amx_matter_bridge_protocol, amx_matter_bridge_host and amx_matter_bridge_port.
• The plugin will no longer try to query the incoming protocol, it will now respect the format specified on the matterbridge.toml file.
• Introduced system messages, a message marked as "system message" won't be printed to other game servers.
• User's SteamID is now included in the Matterbridge payload.
• Added cvar amx_matter_bridge_incoming_dont_colorize. Only for Counter-Strike, by default it will colorize any message with a simple format (green username) but if set to 1 it will not colorize anything, leaving the admin to handle any colorization in the matterbridge.toml file.
• Fixed a lot of errors related to Counter-Strike and rendering text with colors.
• Removed amx_matter_bridge_outgoing_chat and amx_matter_bridge_outgoing_chat_team cvars, these will now be managed by a single cvar: amx_matter_bridge_outgoing_chat_mode. Add the sum of the desired behavior:
  
  • Send all chat = 1
  • Send team chat = 2
  If you want to send everything, you must put 3.
  
• Added amx_matter_bridge_incoming_ignore_prefix. Useful to ignore bot commands.
• Server messages now support multi language.
• Quotes no longer get removed from players' messages.
• Made Sven Co-op use the alternative language file, the game doesn't support rendering "%" in chat.

Sub plugin changes

• API
  
  • Added support for system messages.
  • matteramxx_print_message now includes the userid field.
  • Plugins now can specify an alternative Matterbridge gateway.
  • matteramxx_send_message is now a native.
• CONSOLE
  
  • Console output won't be escaped if amx_matter_rcon_code_block is on.
  • Ignore commands coming from other game servers.
  • It will now use the user id instead of the name for admin checking.
  • Removed support for listip/listid commands, changed error message for a better explanation.
• LAG CHECKER
  
  • Fix missing localization strings.
  • Fixed using wrong lag percent formula.

Special thanks
Th3-822
MaNa

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Someone who can make a video tutorial, because I don't understand anything XD

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Very interesting sir. Great work
Glad to see the community still pushing forward

Re: MatterAMXX: Chat relay between many services [Includes API]
 

You can easily add ReAPI support. This will help you if you want to do that.

And another way to get the FPS https://forums.alliedmods.net/showpo...5&postcount=14

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Any idea why i have this problem? i believe it caused by grip but how?


I tried to switch to a different grip module but the same issue happen.
- 0.1.5-beta -- CRASH
- myarena grip -- CRASH

Oh btw i'm using debian based OS

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Remake /etc/resolv.conf. That is out of Amxx scope.

Re: MatterAMXX: Chat relay between many services [Includes API]
 

Thanks for the respond, nevermind i use windows grip now https://github.com/In-line/grip/issues/242
Thank you whoever made it to support win32.

Re: MatterAMXX: Chat relay between many services [Includes API]
 

You are welcome. Interesting timing of release. For those who do not prefer Windows and have exhausted all efforts.

1 line resolv.conf
chmod +i to immunize the file from further boot corruption until handled.