Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 03/05/2016 in Bug Comments

  1. i reported a fix for this ages ago Fix (just incase they forgot):
    4 points
  2. I found the quickfix for Chrome users: 1. Go here - chrome://flags/#autoplay 2. select how it is selected in this printscreen: http://prntscr.com/jhqe68 or more simply "No user gesture required."
    3 points
  3. Fix was submitted earlier today and is applied whenever @Admins get to it. Done.
    3 points
  4. will fix at next release
    3 points
  5. Issue is caused because after going away or invis you dont get sent the scroller message again so on <i it resets scroller to empty or Live Mode stuff Fix: File: network.as Function: myOnXML (towards the end of the if statement "if (e.nodeName == "i")"
    3 points
  6. This is related to the Dunce power. Dunce allows a moderator to dunce another moderator, hence the "Kick" menu is available. Regarding the "Ban" menu, Dunce was originally placed on that menu and it seems like the administrators have forgotten to make this option unavailable when they moved it onto "Kick". Dunce power enabled Dunce power disabled
    3 points
  7. IPS confirmed there was an issue and escalated it to higher departments.
    2 points
  8. The forum is now running on the latest release. If you're still experiencing this issue then link to the exact content and I'll address it.
    2 points
  9. This is not an issue actually. The timestamp for pawns has expired and since HTML5 doesn't use this system, it works like a charm I emailed admins with explanations about this and should be fixed soon.
    2 points
  10. 2 points
  11. @Blacky The issue has been fixed now. Thank you for reporting.
    2 points
  12. We will need more evidence or details before we’re able to proceed! Thinks such as event logs could be useful, perhaps. Are you sure the tempmodded users weren’t kicked/dunced/yellowcarded etc ?
    2 points
  13. Users have been complaining about this in help chats. I wouldn't classify its priority as "normal" since users find it very inconvenient that they can't browse chats in a specific language.
    2 points
  14. A self note: you still can access the chat through the /go command. The bug has been transmitted to the administrators. I will post when it is fixed. Thank you for reporting.
    2 points
  15. Thank you for reporting. This bug seems to appear also on HTML5. I will post when this bug is fixed.
    2 points
  16. Changed Status to Status: Fixed
    2 points
  17. Changed Status to Status: Fixed Managed to reproduce on 1920x1080 screen resolution.
    2 points
  18. If i remember correctly, this isn't a bug. It was made like that due the lack of activity that xat Ayuda has.
    2 points
  19. Fix: File: xmessage.as Function: Smilie Replace: with if (Code.match(/#wc/g).length > 0 && !todo.HasPowerA(todo.Users[uid].Powers, 410)) { Code = Code.replace(/#wc/g, "#WC"); smc.u = ("C" + xatlib.xInt(smc.u)); }
    2 points
  20. Issue is caused by pools not being reset with <w packet (it doesnt get sent with chats that dont have pools) Before fix:After fix: Fix: (found problem with old fix added new one which is 100% now) File: network.as Function: myOnXML this goes at the end of the if statement "if (e.nodeName == "gp"")"
    2 points
  21. Thanks for reporting this, @DJFUNNY. We're already aware of this bug and it should be fixed in the next update.
    1 point
  22. This is not a HTML5 bug. @Angelo The bug he reported is when you add a "<3" on status, it will change your name (for other people) to "nope" which was done by purpose. Since this is not a HTML5 bug, i'm closing this thread.
    1 point
  23. We have found out that this is related to a chrome pop-up setting. If you click on a link while linkvalidator setting is enabled, Chrome will show up the "pop-up" blocked message indicating that the linkvalidator page is blocked from being opened automtically. The problem is that linkvalidator is already being opened regardless. So if the user chooses "Always allow pop-up", clicking any links will open the page twice henceforward. That being said, we do not think this is a bug related to the HTML5 chat. This rather seems to be a Chrome Browser issue, especia
    1 point
  24. Both (hearts) and (switch) should be playable now.
    1 point
  25. Update: This is happening on Windows as well by now. It could be caused by a Google Chrome / Chromium update which was rolled out slowly
    1 point
  26. Changed Status to Fixed Fixed on an upcoming release.
    1 point
  27. Please clear your cache and give me an update if it happens again @LaFleur. After clearing my cache, the editor loads considerably faster for me.
    1 point
  28. Yes, It is working perfectly, still being replaced the weird char, but not deleting anymore.
    1 point
  29. Should it show like that instead ? @Angelo
    1 point
  30. Changed Status to Status: Fixed
    1 point
  31. Changed Status to Status: Fixed Fixed on update 4.3. Confirmed.
    1 point
  32. No issue for me ? I refresh and was still working for me.
    1 point
  33. The scrollbar style has been temporary removed for now because of Firefox. It will be added back later in the near future.
    1 point
  34. Arabic, Estonian, Filipino, French, German, Hungarian, Italian, Portuguese, Romanian, Spanish, Thai and Turkish, redirects to Help chat too.
    1 point
  35. What the user reported was fixed.
    1 point
  36. This will fix two problems (not being able to do (RANDOM) and the problem listed above) Fix: @Admin File: xAvatar.as Function: xAvatar(constructor) Replace with if ((((((_arg_2.charAt(0) === "(")) && ((_arg_2.toLowerCase().indexOf("random") >= 0)))) && (todo.HasPower(_arg_5, 272)))){ var randavy = _arg_2.split("#"); for (var i:Number = 0; i < randavy.length; i++) { randavy[i] = xmessage.DoRandom(randavy[i], _arg_5); } _arg_2 = randavy.join("#"); }; File: xmessage.as Function: DoRandom
    1 point
  37. You would do so after getting into the pc and then clicking at the user again - then you get to the user dialog. But i don't disagree, it's quite inconvenient.
    1 point
  38. This issue has been fixed. Thank you ^^
    1 point
  39. this is correct its so users can register quick and easy. They can set a nick to anything they want right away. They can chose a reg name later.
    1 point
  40. For the second problem, this is something we can fix on the wiki. To be honest, we had much trouble with the Arabic translations. Send me a PM and we can try finding fixes for this.
    1 point
  41. I can see how you'd think that's a bug, but it's actually working as intended. The levels were changed slightly.
    1 point
  42. Changed Priority to Priority: Trivial Yes, can confirm this issue. Mute shouldn't be shown when being mod. Thanks for reporting.
    1 point
  43. I've looked into it but i can not confirm/reproduce this issue (tried with opera, chrome and edge). Is flash allowed for the ticket page for the users who have it?
    1 point
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • 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.