Jump to content
  • Bot Power Configuration

    • Status: Fixed Priority: High

    The bot power edits are not applied on the new HTML5 Chat Editor, and doesn't properly show meta data on viewing HTML source on xat chat.


    Example; When a user tried to get a bot from ARCbots, he had to insert the bot's xatid in the bot power configuration so the bot is able to join. The bot was not able to detect the changes at all, even after an hour from applying changes, we also attempted to un-assign then re-assign, same issue.


    When the user modified the bot power using the old editgroup The issue was solved and the bot was able to detect the changes and enter normally.



    Bot's companies might be required to ignore the bot power, because the new chat editor doesn't apply changes (for the bot power at least).

    Steps to reproduce bug: Put the xatid of the bot then check if it was applied.
    Screenshots: Nothing to include

    User Feedback

    Recommended Comments

    • Wiki Translators
    11 hours ago, Abrahan said:

    I have tested the bug and it works for me, are you saving the changes correctly?


    Yes of course, this has been tested a couple of times by different people. I think your settings are cached or something.

    9 hours ago, Leandro said:

    Thank you for reporting this issue.


    You'll be notified when fixed.

    Great, thank you.

    • Like 1
    Link to comment
    Share on other sites

    This is now closed for further comments

  • Priority Definitions


    Trivial The issue is considered low priority.

    Normal This is the default priority.

    High A feature or service is not working properly, and it impacts a lot of people. The issue should be fixed in the near future.

    Critical The issue is show-stopping, meaning that a certain feature or service is completely broken with no available workaround. The issue impacts a lot of people and requires immediate repair.

  • Status Definitions


    Open The issue is pending, or we are still working on the issue.

    Fixed The issue has been resolved. The fix may not be immediately noticeable and may be released in a future version or update.

    Closed This record is either not considered an issue or is better suited as a suggestion. If it is an issue, it may not be reproducible.

    Won't Fix The issue will not be fixed because it is too low in priority. The issue is very minor. The resources required to fix the issue cannot justify the benefits received from fixing the issue. This means the issue is closed.

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.