@Oreo321Oreo321 thank you

Hi, I've noticed an issue in the game's category (mod). If you add ils rules for a specific level, you can't see the specific level rules but only category rules, and at the end the level rules. It's possible to fix that and have a separate menu, like separate category, when a specific rules is added for each levels?

This is an example of what i mean:

https://prnt.sc/10xg8rw

I've added "Level Rules" above (to explain what need to be) and last line is first level rule.

@PeppinsPeppins the current behavior is intended; level rules (if they exist) are written below the category rules.
Most of the time you won't need level rules, because the IL category rules can cover all cases, and the level rules are needed for specific additions to specific levels.

I want ask another question about a possible bug: if a run is already verified but the runner edit it and submit it again for verification, WHY i don't receive the email about new verification request?

When a subcategory is empty, and the primary color of the theme is white, the "(empty)" text is still white on highlighted categories, and is not visible.

Links at the end of blockquotes do not lead to the correct address.

Ok, this is weird. A user submitted a run to the Slither.io Category Extensions leaderboard. The time that was submitted is 14 seconds 658 milliseconds, the intended time appears to be 74 Seconds 658 Milliseconds. I noticed the time discrepancy and edited the run but as soon as pressed submit, it reverted back to the other time. All other edits appear to stay but for some reason, the time I edited ended up changing itself back to the 14 seconds and 658 milliseconds. I attempted to submit a run on the user's behalf only to have the time also changed to the same number.

Here's the run link: https://www.speedrun.com/slitherio_extensions/run/zgg3n9jz.

If anyone is able to explain what is happening here, I'd appreciate it very much.

@GarshGarsh I can only guess that the site recognizes that 74 seconds is 1 minute and 14 seconds, so it's changing the seconds value but not the minutes value, which would be unintended. Are you typing 74 into the seconds box, or 1 into the minutes box and 14 into the seconds box?

@QuivicoQuivico, I haven’t touched the minutes box. This definitely could have something to do with it. Let me try that and I’ll get back to you.

Edit: Yep that worked, thanks! It seems like the site should do this automatically but it’s all good.

I think there is a memory leak in the site, when editing my profile and clicking the "Country" it glitches out and takes up 100% of my cpu, freezing chrome.

@MarioManPersonMarioManPerson What you’re describing doesn’t sound like a memory leak. A memory leak occurs when a program stores data in memory but doesn’t clear it out so it continually hogs more and more memory over time. This usually results from a mix of bad coding (been there) and using a coding language that doesn’t have a built in garbage collector function.

If the glitch exists as you’re describing (I was unable to replicate it myself) then it sounds like either a crash within chrome or a result of using a potato. The country list is large but not that large. On an average PC, it would probably take thousands maybe even hundreds of thousands of list entries to crash chrome unless of course you happen to be using a potato. Try it with a different browser (Edge, Firefox, etc), if the same issue occurs it is most likely that you are using a potato. If not, it could be a bug within your version of chrome which can be resolved by updating to the newest version.

Hi, Software Architect here. A few weeks ago my company encountered an issue with Chrome where all of a sudden opening a dropdown - every time our clients would open any dropdown regardless of list size - it would overload their CPU and crash Chrome. We eventually tracked down an issue where certain versions of Chrome around version 88/89 seemed to conflict with something in Bootstrap that caused the issue. The issue existed in Chromium so any Chromium based browsers had the issue (Google Chrome and Microsoft Edge for example). After examining nightly builds of Chrome and using version 91, the issue was gone.

Our leading theory is that Bootstrap and Chromium had a conflict somewhere around Chrome 89 and we had to manually set something in our application’s CSS to resolve the issue in older versions of Chrome. If I remember correctly, this site uses Bootstrap and if your version of Chrome is slightly out of date, you could be experiencing that same issue.

I would first recommend updating Chrome to the latest stable version, and if the problem persists I would try a non-Chromium based browser like Firefox. If my memory serves, Chrome 91 is slated for release in May, and Chrome 90 comes out this month if it’s not already out. So assuming Chrome didn’t mess up their build since the last nightly build of 91, the issue should eventually fix itself by by next month the latest (it might be fixed now if Chrome 90 is out). Or of course if someone on this site’s development feels like changing their CSS to try and manually resolve the issue with Bootstrap, that would also fix it. And no, I don’t remember the CSS we had to tweak to fix this off the top of my head.

Also, as a fun tangent, the issue didn’t happen for everyone on Chrome 88/89 so it could of also included specific hardware components, Bootstrap and Chromium all screwing up together.

TLDR: Try and update Chrome to the latest version and use Firefox as a last resort. Chrome 91 should fix the issue if Chrome 90 doesn’t.

Hi all! With the release of the Support Hub, all bug reports should now be submitted here - https://www.speedrun.com/knowledgebase/supporthub/report-bug