Results 1 to 5 of 5

Thread: chatbotScript only sees private messages

  1. #1

    Question chatbotScript only sees private messages

    I have got an ASH script (surprising, isn't it) that I would like to use as a chatbot script. The problem is, it only ever seems to fire for private messages. Regardless of what account I use it with and whether I am in GUI or CLI mode, the function

    Code:
    void main(string sender, string message, string channel)
    {
            print("DEBUG: ch=" + channel + " se=" + sender);
            // [snip - here be actual script]
    }
    only prints the debug messages if channel is an empty string. No channel messages, no events.

    I have double-checked and confirmed that in both the GUI and the CLI case I do initialise chat: the accounts I have run tests on do show as present in chat when I run /whois on them, "update" requests from clannies do get processed, and of course as I have already mentioned the script does see private messages.

    Of note is the fact that when run by a clannie, the very same script works fine. This might imply that some Mafia setting interferes with chat processing, unfortunately our configurations are vastly different so it is hard to identify the culprit. Having had a look at ChatManager source code has no revealed anything obvious either.

    Any ideas, guys? Thank you in advance, the only idea I have still got is to wipe my Mafia settings and start from scratch - and I would hate to have to manually reset many years' worth of fine-tuning.

    PS. I have tried this on r18370, r18453 and r18471.
    Last edited by Pineapple of Despair; 02-27-2018 at 04:16 PM. Reason: List SVN releases used for testing

  2. #2

    Default

    Of note is the fact that when run by a clannie, the very same script works fine.
    Originally Posted by Pineapple of Despair View Post
    That actually leads me to suspect a difference in KoL chat settings.

  3. #3
    Developer fronobulax's Avatar
    Join Date
    Feb 2009
    Location
    Central Virginia, USA
    Posts
    4,024

    Default

    our configurations are vastly different so it is hard to identify the culprit.
    Originally Posted by Pineapple of Despair View Post
    Sometimes a good diff utility applied to the settings files can help. I am partial to a side by side display and just jumping from difference to difference. I know a priori that some settings won't be of interest, even if they differ, so it can be only a few minutes. There is also a script out there that will help you find settings which are not at the default which might turn up something.

    But as noted elsewhere, check the KoL settings first.
    You just vehemently agreed with me
    Originally Posted by Veracity View Post
    I agree with frono.
    Originally Posted by Veracity View Post

  4. #4
    Developer
    Join Date
    Apr 2010
    Posts
    4,418

    Default

    Crazy thought (based on half remembered chat on another thread), is there a space in the name of the person it doesn't work for?

  5. #5

    Default

    I have figured it out - it was due to greenScreenProtection having been set to true in the global settings of my instance of Mafia. At first I thought that option implemented rate limiting of some sort (clearly I didn't look at the source code of CharManager carefully enough) but I when I found out what the corresponding preference-panel description was, all became clear.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •