Jump to content
  • Protect time bug on gcontrol

    • Status: Open Priority: Normal

    This bug is occurring when you have a decimal number set as the protect time on the chat gcontrol options.


    Example: If you've set "0.1" for the protect time option, you wont be able to disable the protectior after enabling by command.

    xat allows you to turn on the protection but nobody can disable it (even an ID ranked as main owner cannot turn it off).


    Apparently any value with a dot breaks it. Examples: 0.2, 0.4, 0.8, 2.5, and so on.


    Adding a comma will force reset and return the input value to 1 (default time, an hour).

    Whole numbers (e.g. 1, 2, 3, etc.) are working fine as far I know though.


    I'm referring to this option (click here for the direct image link):





    Steps to reproduce bug: Step 1: 
    Step 2: 
    Step 3: 

    User Feedback

    Recommended Comments

    There are no comments to display.

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • 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.