Nope

You are allowed to use the Speedrun Tool which enables FPS limiting and autosplitter, but I think so far that is the only allowed mod.

TBH The pros outweigh the cons by quite a bit to me. Don't know how it would make competition less consistent, considering everyone would probably play with the same modifiers if they were found to make the game faster, but they probably aren't by that much.

As for the name of the category, I’d go with Any% NG+, but if you’d rather make a subcategory, you could make the names “Fresh File” and “NG+”

My rule suggestions would be:

• Time starts upon spawning into The Hub after clicking anywhere on the screen.

• Time ends upon interacting with Frazzer after his boss fight.

• Complete all four paths, this includes:

1. Communications

2. The Armory

3. The Study

4. Frazzer’s Room

• Your save file used in the run must be already completed upon the beginning of the run.

So Any% involves beating the game from a fresh file, which includes the cutscenes, sometimes having to grind for blips/blueprints, etc. I think there should be an NG+ category in which you go through the four levels (Communications, The Armory, The Study, Frazzer's Room) from a used save file, it'd be a more fast-paced category and cut off a ton of time from Any%. More beginner-friendly as well IMO.

Often times when I get on, most runs are already verified. Tuotelly's been doing a great job with it, and we have no categories or anything to add, or rules to change, so there's really nothing for me to do. Thanks for the concern though.

yeah?

I messaged you on twitter, and you know FOR SURE that there is a discord because you were IN IT BEFORE YOU LEFT. You obviously didn't care about this game, so I stopped contacting you. I messaged you on Twitter that I know you were active on, and I haven't had motivation to message you on speedrun.com because I assumed I still wouldn't get a response.

Your lack of activity toward this community left me baffled at how someone can just take the Irish exit by not saying anything before leaving. Even just a discord message saying that you're going to take a step back would've been nice before you left the server.

Secondly, it is not "devaluing runs." It's a bug that has been patched since, and makes it more fair among runners if we exclude the text overflow glitch. Separation of leaderboards for patched and unpatched is already a bad idea, and the leaderboards were filled with runs that were from years ago on a slower version. Should I have archived the categories in a spreadsheet? Probably, so I apologize for that. But a leaderboard wipe was, frankly, long overdue. It made no sense to keep runs that:

1. Used a glitch that is very uncommonly achieved and gives an unfair advantage to those who do get it.
2. Were ran on an older version that is slower in almost every way.

I’ll try clarifying everything here.

1. We wiped the leaderboards because they were filled with runs that were mostly from the original game. Now that it has been patched to be faster, the runs should have been removed anyway, or at the very least archived, because nobody would play on the older version of the game anyway due to it being slower. The “Buddy Edition” at the time of us wiping the leaderboards, had only been out for about 2 months, so there weren’t even that many new patch runs. After extensive testing and talk with the developer, we got a massive bug fixed and we’re super glad he could help us fix this bug that fucked up the leaderboards, because it could either happen or it couldn’t. It was weird.
2. Dividing the runs between patched and unpatched then puts a pressure on newer runners to play on the patched version so that they are on equal playing ground. Having a severance would not be the way to go.
3. @feminine I don’t even know what to say to you. I have messaged you repeatedly and despite my pleas to either just talk to us, be a moderator with us, even at one point me asking you to demote yourself because you do NOTHING, I have not gotten a response from you since 2019. Quite frankly, it is embarrassing that I had to consult a runner and the developer of the game for what decisions I could make, because I knew I could not rely on you.

All runs that did not use the text overflow glitch but are from the unlatched version can be submitted and verified. I will no longer reject runs that are from the previous version as long as they don’t use that glitch. I’ll manually review the video and use my better judgment to see if it was used. If you have any questions, don’t hesitate to DM me. JokerFactor#7021.

Sorry for the late reply, but yeah of course.

The only place where this would work is All Notebook and Any%, though. We don't accept double runs of Any% and Secret Ending together because they are technically different endings.

There's already a category called "Character Movesets," you can use Luigi in that

For a joke, I don't think it's very funny.

"All Achievements" would require RNG because you can mostly only get them in online games. I can see an exception being made for if all players agree to do the run, but you must also take into account that it has to be done on a clean, wiped steam/Among Us account. On top of that, nobody would run it.

Next slide, please.

...it is a category. Go to "All Endings" and select "22 Endings" in the dropdown list

I believe a comparison was done by moderators and it was concluded that the difference was too miniscule to count for much, or something like that.

I believe the only reason the IL leaderboards are split into EMU and Console are because you can use things like your mouse, a trackpad, or a trackball on EMU. Console forces you to use the touchscreen with either your finger or a stylus.

While still co-developed by Innersloth LLC., it is a separate entity from "Among Us." Those who have Among Us will not automatically get Among Us VR. It will be counted as a separate game.

@SARNEYA Too much luck involved and also it would reach the most optimal time very quickly

Hourglass right next to the search bar > View All... > Click your run > Three dots in the run panel > Edit run > Edit time > Submit run

It should work on either version