To skip the tutorials, you have to play on medium or hard. I have made a tutorial for the entire run if you're interested: https://www.speedrun.com/the_lion_king_simbas_mighty_adventure/guide/ucvwk (I have to fix a few gifs, but the guide is pretty complete).

Concerning consoles: I'll add PS3, but I don't think PSP natively supports playing PS1 games without iso modification or emulator. If I'm wrong, please show me how, both for my own personal knowledge, and so I add it in the list of consoles.

I meant 1.0 vs 1.1, thanks for the answer and the extra details about that PC difference as well.

I'm curious, what tool did you use to TAS your mouse movement?

And I'm about as late as you are :P I had uploaded my runs to youtube, but never sumittted. I'll come around to doing so soon.

Emulator runs are allowed for accessibility. Most emulators will play slower than an actual 90k PS2 with FDS, or on par. If an emulator is faster than actual console or too inaccurate, it should probably be banned. Playing on emulator actually makes you play at a disadvantage.

Despite being allowed for accessibility, top level runs should be done on console to preserve the legitimacy. It could've went the route of only allowing them over a certain time (let's say anything over 23m). But instead was set to follow the WR time.

Neat. No use for me for now, but I like it.

NoReset Speedrun (bilingual french/english), a Québec-based speedrunning community with international events across North-America: https://www.youtube.com/channel/UCEQbsGUYuqh9cwXFiF1CKLQ/playlists

While this wouldn't be as useful for me now as when I asked about it back then (see reason below). Knowing at least the leaderboard size could still prove very useful to prevent some useless calls to the api when there's not enough runners.

Since then I've started using the time of all the PBs on a board to compare relatively to a specific run's time. As well as a bunch of other infos from the leaderboard. I've opted for a caching/memoizing system, with checkpoint on webworker timeout and eventually a requests pool as well.

This. And thanks for the workaround @ThePigKing , I forgot google could do that

@TheGaming100 I made this scoreboard, I appreciate the concern. The ID is something public you can easily obtain (for example, yours is here: speedrun.com/api/v1/users/TheGaming100 ). As far as the API key goes, it's never stored, and only used once in the login process, sent to speedrun.com's api over HTTPS to authenticate.

loading a file with ONLY 1-1 iirc I don't think that's possible without resetting the console. You get to choose to load files only once. Once in a save file, you can't load another (I might be wrong though) I very much agree the reset is annoying, though really it's not that bad and certainly not as bad as other games have it.

I'm usually more on the side of starting games from a fresh file when speed running (unless it's impossible or too impractical). Even if it doesn't seem to change anything. But that's really more out of principles. I don't think M&M Shell Shock will have some crazy glitch or become optimized to a point where it truly matters, as much as I would like to see that.

So I'm against. Not a hill I'm willing to die on though, so if ends up allowed, I'll go with it.

Your explanation makes sense, True Any% would indeed be PC competitive only (well, any console, but they'll be the same run as glitchless, kinda how a no map run is also a glitchless run).

The glitch I was referring to is a noclip glitch that a coworker showed me and is really easy to do (it requires an NPC and an arcana with specific behavior) and is absolutely still doable in the current patch. So if you find a shopkeeper before finding the miniboss, you can noclip and just run around freely without triggering any room (enemies still attack)

Just as a side note, because I saw no mention of it in the rules: "All glitches are just not allowed." For Glitchless only or all categories? Because there's no mention of it anywhere in the rules (appart from the obvious category title) "Currently there are to my knowledge no glitches in the current WoL V1.033B. So this makes Any%(Glitchless) just normal Any%", same here, there's no mention of not being allowed to go back to a previous version (for example if a boss have been buffed or for a glitch has been patched)

I have a pretty simple question: Why is there no true Any% category? One allowing glitches.

There's Any%(Glitchless), Any%(No map) and a few other categories. Meaning a run with glitches has to also abide by a more restrictive category's rules.

It's also worth mentioning that Any%(Glitchless)'s rules don't make any mention of not allowing glitches

<placeholder until I get to actually write and finish the entire guide, compiling all the jumbled informations from the discord>

Chariot maps Imgur album: https://imgur.com/a/b7An2Wb

8BitisGr8 managed to crush my WR with slightly tighter movement, and especially two new boss skips I,ve never seen before. While the first one is easy enough, 8Bit actually lost a lot of time to the second one with how long it took him to get it.

If anyone has any tips as to a consistent setup, feel free to share.

I have no issues with emulator runs (especially when they're slower than the original console), as long as they're clearly marked as such.

I added my Shortest path spreadsheet to the original post.

This game is available on Android and iOS as well. Can we add those platforms? As far as I'm aware the game is the exact same so no need for new categories or anything. Just the option of "Android" and "iOS" for the platform.

I wouldn't change the split time (last hit on Zira is last input). Just that you need to actually complete the level/beat the game (meaning see the end credits). If a video doesn't show the end credit, you just need to look at the paw count before entering Zira's fight (100 for easy, 300 for medium and 450? for hard). If you wanna change the split time, end on first frame of credits. Wich means you still need to mash through the end-level screen and invalidates most video proof.

Good tip, I'll try to remember to add the model number in the comment (I think I used to do that but then forgot about it).