Jump to content
  • Temp[rank]ing a user only allows for integer input values


    Angelo
    • Status: Open Priority: Trivial

    It appears as if you can only temporarily rank someone for integer value hours on HTML5 (and mobile for this matter!)

     

    For example, trying to tempmem someone for 5.55 hours gives them a 5 hour temp.

    Giving someone a 6.66 hour tempmod gives them a 6 hour temp.

    7.77 hour tempown gives them a 7 hour temp.

     

    So on and so forth.

     

    I've also noticed this bug on mobile, although I was told to only make a post in HTML5.




    User Feedback

    Recommended Comments

    Update:

     

    I'm unable to verify whether or not this is purely a visual glitch. Earlier today I used the fexbot to tempmod a member on help for 8.5 hours (I was on mobile). On the chat it showed as 8 hours. I've recently looked in events and noticed that events has recorded 8:30 hours, or 8.5 hours. 

     

    OSrQc8i.png

    Share this comment


    Link to comment
    Share on other sites

    @Angelo This is indeed just a visual glitch, sloom checked this out.

     

    Since the issue has been forwarded, i'm closing this thread.

     

    You will be notified once it's fixed.

     

    Thanks.

    Share this comment


    Link to comment
    Share on other sites


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

×

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.