AlliedModders

AlliedModders (https://forums.alliedmods.net/index.php)
-   New Plugin Submissions (https://forums.alliedmods.net/forumdisplay.php?f=26)
-   -   AMXX Chat Relay [Discord <=> Ingame] (https://forums.alliedmods.net/showthread.php?t=318610)

endnch 09-09-2019 17:21

AMXX Chat Relay [Discord <=> Ingame]
 
3 Attachment(s)
AMXX client for the Discord bot in this plugin:
https://forums.alliedmods.net/showthread.php?t=311079

Introduction

Communicate between Discord & In-Game, monitor server without being in-game, control the flow of messages and user base engagement!

Features

- Recieve and send messages bidrectionally
- Channel configuration for powerful setups
- Setup is incrediblily easy with Discord bot commands and simple config files
- Upon disconnect, game servers will attempt to reconnect at a fixed interval

Prerequisites

- AMX Mod X 1.10 (tested on build 5378)
- Server to host the relay binary on (with MySQL if not external)
- A Discord bot token (https://discordapp.com/developers/applications/)
- Discord Bot v2.0.0 (https://github.com/rumblefrog/source...relay/releases)

Bot Installation

https://rumblefrog.me/source-chat-relay/setup

Plugin Installation

- Copy the plugin to your plugins folder
- Add the plugin filename to your configs/plugins.ini file
- Copy the config file to you configs/plugins folder
- Edit the config file
- Change map to load the plugin
- You should get a "[AMXX-Server-Relay] Successfully authenticated" message if you did everything correctly

JocAnis 09-09-2019 21:28

Re: AMX Chat Relay [Discord <=> Ingame]
 
Finally something really new and interesting in "New Plugin Submissions"

I successfully did a connection so amxx will trigger a discord bot to write something in the specific channel, but could do opposite, to read command and react on them...how it seems your work is doing right that

Can you exaplain in detail what does this mean?

Server to host the relay binary on (with MySQL if not external)
(mysql is must-need?)

Also why amxmodx 1.10 ... :D

endnch 09-09-2019 21:48

Re: AMX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by JocAnis (Post 2666465)
Finally something really new and interesting in "New Plugin Submissions"

Can you exaplain in detail what does this mean?

Server to host the relay binary on (with MySQL if not external)
(mysql is must-need?)

Also why amxmodx 1.10 ... :D

You need to run the Bot software so the game server can communicate with your Discord server. You can run the software on your computer, or you can run it on a server so it stays online 24/7. The software requires a MySQL database to store information about the clients that connect to it and the channels in your discord server. You can run this database in the same computer/server as the software or you can run it externally in another server.

I put 1.10 because that's the version I tested it on, in the code I use some functions that were introduced in 1.9 so technically it should work in 1.9 too, but I haven't tested it.

DON KHAN 1 09-10-2019 06:07

Re: AMX Chat Relay [Discord <=> Ingame]
 
Very Nice plugin.
One thing there is 1.8.2 is latest version of amxmodx i have seen in amxmodx.org so u should make this plugin work on 1.8.2.
BTW its very nice plugin.

Mistrick 09-10-2019 06:28

Re: AMX Chat Relay [Discord <=> Ingame]
 
Don't use blocking socket for every chat message.
Do you know about curl or grip?

OciXCrom 09-10-2019 07:25

Re: AMX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by DON KHAN 1 (Post 2666489)
Very Nice plugin.
One thing there is 1.8.2 is latest version of amxmodx i have seen in amxmodx.org so u should make this plugin work on 1.8.2.
BTW its very nice plugin.

It's 2019, start using new stuff. 1.8.2 will soon be an unsupported version, so there's no point in doing that - simply not worth it. Discord didn't even exist when that version came out.
------------------------------------------------------
Word of advice - maybe a better name for the plugin will be "AMXX Chat Relay". AMX is a very old and no longer supported version of AMXX.

PS: you don't need to include "amxconst" and "cvars" manually - they are already included in "amxmodx".

HamletEagle 09-10-2019 07:32

Re: AMX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by OciXCrom (Post 2666502)
It's 2019, start using new stuff. 1.8.2 will soon be an unsupported version, so there's no point in doing that - simply not worth it. Discord didn't even exist when that version came out.
------------------------------------------------------
Word of advice - maybe a better name for the plugin will be "AMXX Chat Relay". AMX is a very old and no longer supported version of AMXX.

PS: you don't need to include "amxconst" and "cvars" manually - they are already included in "amxmodx".

"Soon"

LearninG 09-10-2019 08:21

Re: AMX Chat Relay [Discord <=> Ingame]
 
was looking randomly to code , and saw these :
Code:
new sKillerName[MAX_NAME_LENGTH]; get_user_name(killer, sKillerName, MAX_NAME_LENGTH); new sVictimName[MAX_NAME_LENGTH]; get_user_name(victim, sVictimName, MAX_NAME_LENGTH); new sWpnName[MAX_NAME_LENGTH]; xmod_get_wpnname(wpnindex, sWpnName, MAX_NAME_LENGTH);
why not using charsmax(sKillerName) , charsmax(sVictimName) , charsmax(sWpnName) ?
Code:
format(sMessage, MAX_COMMAND_LENGTH, "\*\*\* %s killed %s with a headshot from %s \*\*\*", sKillerName, sVictimName, sWpnName); } else { format(sMessage, MAX_COMMAND_LENGTH, "%s killed %s with %s", sKillerName, sVictimName, sWpnName);
why not formatex() ?

iceeedr 09-10-2019 09:07

Re: AMX Chat Relay [Discord <=> Ingame]
 
Why not?

PHP Code:

 formatex(sMessageMAX_COMMAND_LENGTH"\*\*\* %n killed %n with a headshot from %s \*\*\*"killervictimsWpnName);
}
else
{
formatex(sMessageMAX_COMMAND_LENGTH"%n killed %n with %s"killervictimsWpnName); 

Since it is for using the functions of amx 1.9 + ...

endnch 09-10-2019 11:57

Re: AMX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by DON KHAN 1 (Post 2666489)
Very Nice plugin.
One thing there is 1.8.2 is latest version of amxmodx i have seen in amxmodx.org so u should make this plugin work on 1.8.2.
BTW its very nice plugin.

I actually started developing it in 1.8 but when I got to creating the cvars I said "screw this" and switched to 1.10. Anyhow I added a 1.8 compatible version, it has no cvars so to configure it you have to modify the source and compile the plugin yourself. Also the messages coming from discord won't have any color.

Quote:

Originally Posted by OciXCrom (Post 2666502)
Word of advice - maybe a better name for the plugin will be "AMXX Chat Relay". AMX is a very old and no longer supported version of AMXX.

PS: you don't need to include "amxconst" and "cvars" manually - they are already included in "amxmodx".

Changed the plugin name and removed the includes.

Quote:

Originally Posted by LearninG (Post 2666512)
why not using charsmax(sKillerName) , charsmax(sVictimName) , charsmax(sWpnName) ?

I fixed that, thanks.

Quote:

Originally Posted by LearninG (Post 2666512)
why not formatex() ?

Quote:

Originally Posted by iceeedr (Post 2666523)
Why not?
Since it is for using the functions of amx 1.9 + ...

Is formatex really that much faster than format? I changed it anyways.

iceeedr 09-10-2019 12:05

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Code:

Format specifier
Specifier        Description
%b        Binary digits in the value
%n        Requires a client index. Expands to a string containing the player's name.
If the client index is 0, the string will be: Console
%N        Requires a client index. Expands to 1<2><3><4> where 1 is the player's name, 2 is the player's userid, 3 is the player's SteamID, and 4 the player's team name.
If the client index is 0, the string will be: Console<0><Console><Console>
%l        Translates a phrase from a key. Similar to %L with the difference it will use the client's index set internally by the function.
This is only allowed in functions which act directly on one or more clients.
Note:To complement this, a new ⇅ SetGlobalTransTarget native to set the current index has been added.
This is useful to be used before with natives which are not player-oriented", like a bunch of formatex.

PHP Code:

formatex(sMessageMAX_COMMAND_LENGTH"\*\*\* %n killed %n with a headshot from %s \*\*\*"killervictimsWpnName);
}
else
{
formatex(sMessageMAX_COMMAND_LENGTH"%n killed %n with %s"killervictimsWpnName); 


endnch 09-10-2019 12:08

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Yeah I was just looking into that, will try to use the %n specifier.

Edit: Done.

Alber9091 09-11-2019 15:45

Re: AMXX Chat Relay [Discord <=> Ingame]
 
1.10 is to ahead, 1.90 would had been appreciated, even the latest [5249] will also be considered great.

iceeedr 09-11-2019 15:53

Re: AMXX Chat Relay [Discord <=> Ingame]
 
MAX_NAME_LENGTH is already set by default in amx 1.9+

Alber9091 09-11-2019 16:31

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by iceeedr (Post 2666699)
MAX_NAME_LENGTH is already set by default in amx 1.9+

I haven't seen plugin, but Aurthor in post mentioned Requirement AMXX 1.10

iceeedr 09-11-2019 16:52

Re: AMXX Chat Relay [Discord <=> Ingame]
 
And that is why I warned the author that it is not necessary to define "max_name_lenght" in the plugin, since the definition already exists by default in amxx 1.9 +

endnch 09-12-2019 10:21

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by iceeedr (Post 2666699)
MAX_NAME_LENGTH is already set by default in amx 1.9+

Fixed.

hckr 09-27-2019 18:19

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Thanks for this job, I'm new at this and would like to know ¿How to install it for counter strike 1.6? ¡greetings!

OciXCrom 09-27-2019 20:51

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by hckr (Post 2668224)
Thanks for this job, I'm new at this and would like to know ¿How to install it for counter strike 1.6? ¡greetings!

It's nice to read the first post before asking questions that are already answered.

hckr 09-29-2019 21:52

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by OciXCrom (Post 2668228)
It's nice to read the first post before asking questions that are already answered.

It's also good to read that I mentioned that I'm new at this and so far I've only used amxx plugins to copy and paste, and the guide to this is a little difficult for me, this message goes with !the best energy!


pd_ I know it's a lot to ask before such work done, but if someone makes a video guide how to install these great files would appreciate =D

OciXCrom 09-30-2019 05:32

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Being new doesn't mean you can't read. I'm pretty sure there are hundreds of tutorials on how to install a simple plugin, so please search for them. Every plugin is installed in the exact same way.

rautamiekka 10-01-2019 08:15

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Found 1 typo: in
Code:

public authenticate() {
you've
Code:

authenticacion
.

OciXCrom 10-01-2019 09:25

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by rautamiekka (Post 2668482)
Found 1 typo: in
Code:

public authenticate() {
you've
Code:

authenticacion
.

What?!

RumbleFrog 10-07-2019 10:34

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by hckr (Post 2668396)
It's also good to read that I mentioned that I'm new at this and so far I've only used amxx plugins to copy and paste, and the guide to this is a little difficult for me, this message goes with !the best energy!


pd_ I know it's a lot to ask before such work done, but if someone makes a video guide how to install these great files would appreciate =D

Documentation is available at https://rumblefrog.me/source-chat-relay/

Note that it talks about the Sourcemod plugin, so you have to switch it in your case for the AMXX variant.

RaZ_HU 10-13-2019 08:54

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Feature request: add a file where we can list phrases to be ignored.

Also please ignore messages starting with " / " (commands) and whitespace:
Code:

public handleSay(id)
{
        new sMessage[MAX_COMMAND_LENGTH];
        read_argv(1, sMessage, charsmax(sMessage));

        if (strlen(sMessage) == 0 || sMessage[0] == '/' || sMessage[0] == ' ')
        {
                return PLUGIN_CONTINUE;
        }

Plugins and the relay bot are both awesome, thank you guys.

Edit:
@endnch I have changed your SMA code to support exclusive list, if needed I can send it to you and check it (I am sure there are stuff that could be done better in it).

RumbleFrog 10-14-2019 02:52

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by RaZ_HU (Post 2669652)
Feature request: add a file where we can list phrases to be ignored.

Also please ignore messages starting with " / " (commands) and whitespace:
Code:

public handleSay(id)
{
        new sMessage[MAX_COMMAND_LENGTH];
        read_argv(1, sMessage, charsmax(sMessage));

        if (strlen(sMessage) == 0 || sMessage[0] == '/' || sMessage[0] == ' ')
        {
                return PLUGIN_CONTINUE;
        }

Plugins and the relay bot are both awesome, thank you guys.

Edit:
@endnch I have changed your SMA code to support exclusive list, if needed I can send it to you and check it (I am sure there are stuff that could be done better in it).

Those already can be done on the server-side: https://rumblefrog.me/source-chat-relay/filters

RaZ_HU 10-14-2019 07:20

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by RumbleFrog (Post 2669711)
Those already can be done on the server-side: https://rumblefrog.me/source-chat-relay/filters

Wow, I missed that somehow. Thank you :D

Mark.uG 10-20-2019 13:55

Re: AMXX Chat Relay [Discord <=> Ingame]
 
1 Attachment(s)
On 1.8 does not seem to work after mapchange unless you restart the bot then works as normal


I ran a log alone side the bot. Heres the file I removed some personal info from it but anyone know what this is saying lol.

RumbleFrog 10-21-2019 19:08

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by Mark.uG (Post 2670402)
On 1.8 does not seem to work after mapchange unless you restart the bot then works as normal


I ran a log alone side the bot. Heres the file I removed some personal info from it but anyone know what this is saying lol.

Should be fixed in v2.1.1

SERGE90 10-29-2019 18:06

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Hello!
Thank you for your plugin. It works great in CS 1.6 server, but Could you adapt it for Half-Life 1? :up:

https://thumb.cloud.mail.ru/weblink/...ssia%40mail.ru

Enrory 11-01-2019 13:04

Re: AMXX Chat Relay [Discord <=> Ingame]
 
hi
why need chat stuff
csx module?
can make plugin for more games?

RumbleFrog 11-01-2019 22:40

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by Enrory (Post 2671613)
hi
why need chat stuff
csx module?
can make plugin for more games?

Elaborate?

DruGzOG 11-14-2019 19:08

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Attempted to run this plugin for a while. The source relay works fine on the sourcemod queries but does not work on the hl1 games we have it running on. We get the following error:

"[AMXX-Server-Relay] Error connecting socket"

Anyone able to help or know why its causing this?



Edit:
Found the fix. Default .cfg file needs to be renamed to AMXX-Server-Relay.cfg and not AMX-Server-Relay.cfg :/

Mark.uG 11-18-2019 23:12

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Plugin works great and should be approved

RaZ_HU 11-23-2019 21:12

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Hi!
It was working perfectly until 2 days ago, I get this in server console (latest AMXX 1.10 build 5388, running cstrike):

Code:

[AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: epresmoha : asd

[AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: epresmoha : 2324l1l455l

[AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: epresmoha : test message

[AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code:

Yes, this is 4 line.

I have updated the relay server to the latest one from Github, but it still happens.
Maybe related to this change? https://github.com/alliedmodders/amx...053db8dd7f8902

Mark.uG 11-25-2019 15:44

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Mine is still running without problems

iNvectus 11-27-2019 02:28

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by RaZ_HU (Post 2674231)
Hi!
It was working perfectly until 2 days ago, I get this in server console (latest AMXX 1.10 build 5388, running cstrike):

Code:

[AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: epresmoha : asd

[AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: epresmoha : 2324l1l455l

[AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: epresmoha : test message

[AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code: [AMXX-Server-Relay] Invalid messagetype code:

Yes, this is 4 line.

I have updated the relay server to the latest one from Github, but it still happens.
Maybe related to this change? https://github.com/alliedmodders/amx...053db8dd7f8902

Nope, not possible. It seems it is receiving wrong message from the server. Probably something has changed in the source. Will take a look in my spare time.

RaZ_HU 11-30-2019 04:57

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Solved: I had to reconfigure it, my DC bot token changed (but why?), it works again.
Sorry :D

UNU_ 05-26-2020 14:17

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Can you make a version to use multiple channels and get ingame chat for separate channels adminchat/ playerchat:)

thEsp 05-26-2020 14:41

Re: AMXX Chat Relay [Discord <=> Ingame]
 
Quote:

Originally Posted by UNU_ (Post 2702424)
Can you make a version to use multiple channels and get ingame chat for separate channels adminchat/ playerchat:)

There's a much better extension that is actively being developed and ready for more features. https://forums.alliedmods.net/showthread.php?t=319940


All times are GMT -4. The time now is 06:51.

Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.