[asherkin]

The beta version of the SourceBans plugin integrates with the SourceMod API properly, and should Just Work.

[lyric]

We continually get "socket error 3 (errno 111)" connection refused when we try to use sourceirc bot to connect to gamesurge. I sent a ticket to gameservers.com and they said they only have ports 9000-9050 available and we tried changing the port to that but it still no connect.

is there mayb ea problem with the socket extension that needs looked at? since it's the only other thing we can think of that works with sourceirc since you are so sure it's not a problem with sourceirc. thanks

[asherkin]

The IP range is probably blocked from GameSurge (being a shared host and GameSurge have very strict connection limits), I suggest setting up a IRCd of your own.

[Azelphur]

Originally Posted by lyric We continually get "socket error 3 (errno 111)" connection refused when we try to use sourceirc bot to connect to gamesurge. I sent a ticket to gameservers.com and they said they only have ports 9000-9050 available and we tried changing the port to that but it still no connect. is there mayb ea problem with the socket extension that needs looked at? since it's the only other thing we can think of that works with sourceirc since you are so sure it's not a problem with sourceirc. thanks

Gamesurge doesn't listen on port 9000, the correct port is 6667

[Xaphan]

Hi Azelphur, Spoke with you over the irc channel.
Just a simple reminder to add authserv on the next release.... ;)

ty

[jholland]

The SourceIRC-RelayAll.smx plugin was failing for me with the following error, and I assumed it was because of the recent protobuf/bf changes to CS:GO.

L 03/08/2013 - 01:09:24: [SM] Unable to load plugin "SourceIRC\sourceirc-relayall.smx": Native "BfWriteByte" was not found

Compiling the .sp file with the new spcomp.exe seems to have fixed it, and most messages are relaying properly to my IRC channel again (Connections and such) but chat messages don't seem to carry over.

Any ideas as to why this would be? It doesn't seem to be returning any errors of any sort.

Also, I attached the updated .smx file for anyone else getting the bfWriteByte error messages. No guarantees chat will relay, though, obviously.

[MPFzunnie]

I am having the same problem with our server for CS:GO.
The bot seems to work but it does not relay messages to IRC.
The commands work though.

This is what i got in the config file, this is correct or not? :

        "channels"
        {
            "#mpf-csgo-arena"
            {
                "password"    "" // The channel password/key (+k) in most cases you should leave this blank.
                "relay"            "1" // Tell the RelayAll module to relay messages to this channel
                "cmd_prefix"    "!" // Ontop of calling the bot by name, you can also use "!" in this channel
            }
            "#mpf-csgo-arena-admin"
            {
                "ticket"        "1" // Tell the ticket module to send tickets to this channel
                "relay"            "1" // Tell the RelayAll module to relay messages to this channel
                "cmd_prefix"    "!" // Ontop of calling the bot by name, you can also use "!" in this channel                
            }
        }

Someone know what is up? Is it not compatible with CSGO?

[Azelphur]

It's broken in CS:GO at the moment, will work on it sometime soon

[MPFzunnie]

Ah ok, thanks for replying, i hope it gets fixed then soon
Thanks.

[jholland]

Originally Posted by MPFzunnie Ah ok, thanks for replying, i hope it gets fixed then soon Thanks.

You can get relay working from IRC -> CSGO by recompiling the sourceirc-relayall.sp file in the sourcemod\scripting folder with spcomp (Same directory). CSGO -> IRC won't work, though.

If you're not familiar with the usage, you can just drag & drop the .sp file onto spcomp.exe, and it'll show up in the \compiled folder (Windows). If you're on Linux, I believe it's just ./spcomp sourceirc-relayall.sp.

That'll give you an updated .smx file that works, half way at least, for the time being.