[nco]

L 06/30/2016 - 16:38:28: [CallAdmin: Steam module] Failed to send steam message: (result: 3 [No recipients were setup prior to sending a message] | error: 0)

If i restart calladmin_steam.smx it works perfectly but over time its getting an error.
The bot is for a short time online but dont send a message out.

 SourceMod Version Information:
    SourceMod Version: 1.7.3-dev+5303
    SourcePawn Engine: SourcePawn 1.7, jit-x86 (build 1.7.3-dev+5303)
    SourcePawn API: v1 = 4, v2 = 6
    Compiled on: Apr 21 2016 13:21:28
    Built from: https://github.com/alliedmodders/sourcemod/commit/6317916
    Build ID: 5303:6317916
    http://www.sourcemod.net/

MMSource version: mmsource-1.10.6

I use the latest version of the calladmin and calladmin steam.
The bot works over a steamgroup and all is correctly set.
Thanks for your help!

[Impact123]

Messagebot's recipients list will be cleared (and filled afterwards by the steam module in all but the last case) under the following circumstances.

• The steam module starts the first time
• The steam module is reloaded
• The steam module's reload command is used
• The messagebot extension is reloaded

Unfortunately I don't really have a better answer other than that it shouldn't change unless one of these things happen. I'm always willing to look at cases like this in private though.

[Penetal]

I seem to have the same problem as nco (post 1531).

Penetal is about to be reported by Server for I had an urge and felt like it needed to happen Penetal (ReportID: 1) was reported by Server for I had an urge and felt like it needed to happen Current trackercount: 0 L 07/05/2016 - 00:16:58: [CallAdmin: Test] Loggingtest Plugin: CallAdmin: Test (handle: 1f001f) logged a message: Loggingtest L 07/05/2016 - 00:17:03: [CallAdmin: Steam module] Failed to send steam message: (result: 3 [No recipients were setup prior to sending a message] | error: 0) Plugin: CallAdmin: Steam module (handle: 520052) logged a message: Failed to send steam message: (result: 3 [No recipients were setup prior to sending a message] | error: 0)

Except I have a newer version of sourcemod.

sm version SourceMod Version Information: SourceMod Version: 1.8.0.5915 SourcePawn Engine: SourcePawn 1.8, jit-x86 (build 1.8.0.5915) SourcePawn API: v1 = 4, v2 = 11 Compiled on: Jun 25 2016 048:25 Built from: https://github.com/alliedmodders/sou...commit/688bbc9 Build ID: 5915:688bbc9 http://www.sourcemod.net/

The message seems to come through after I reloaded the calladmin_steam plugin.

sm plugins unload calladmin_steam.smx
sm plugins load calladmin_steam.smx

it also worked if I ran

sm_calladmin_steam_reload

and I got the steam message.

Is there something I can do to help debug the problem? I really want this to work, as it is now I think maybe I would have to put the reload command in the server cfg and hope that will work.

[BReeZ]

Does this plugin allow specifik reports to be reported to specifik admins?

Example: Admin drama between the admins, and one of the admins would like to report that to the head only.

Is such thing available in the configuration?

Either way, will set this up for my community in the upcoming days .

[Impact123]

@Penetal
I was testing the steam module with nco the other day and I'm pretty sure that it isn't caused by it. The messagebot extension is popoklopsi's speciality though so i can't test it myself.

You should be able to work around this for now by adding

sm_calladmin_steam_reload

to your server.cfg.

@banjomus99
No.

[ghostofmybrain]

Is there any way to hide it when a person types !call? I noticed you can hide the message that says who reported whom, but !call still broadcasts. I know in deathmatch servers, for example, !guns is hidden from chat, so I was thinking maybe the same thing could apply to !call?

[Impact123]

There are two types of so called chat triggers in sourcemod, a public one and a silent one which, for some reason, nobody knows about. Typing !call is the public chat trigger and will be seen by all, /call is the silent one and will not. This should work for all properly created sourcemod commands and his can be configured in sourcemod's core.cfg. We only do this with !abort to abort typing a reason for a report, but !abort is not a command. I think using a "command" (it's probably just hooking the chat) like !guns and hiding it is abusing sourcemod's conventions. I hope you understand that i prefer not to do that.

[ghostofmybrain]

Originally Posted by Impact123 There are two types of so called chat triggers in sourcemod, a public one and a silent one which, for some reason, nobody knows about. Typing !call is the public chat trigger and will be seen by all, /call is the silent one and will not. This should work for all properly created sourcemod commands and his can be configured in sourcemod's core.cfg. We only do this with !abort to abort typing a reason for a report, but !abort is not a command. I think using a "command" (it's probably just hooking the chat) like !guns and hiding it is abusing sourcemod's conventions. I hope you understand that i prefer not to do that.

Alright, thanks for the reply.

[llamaz]

Hey, I was wondering if anyone has or can make a email version of this, as the others can't apply to me and the bot doesn't seem to work no matter what I "fiddle" with. Thanks if anyone can!

[Impact123]

What problems do you encounter with the steam module? Maybe i can help to get it working.