Three things I'd like to request changes for:

1. Adventure is misspelled --> "advanUture"

2. I'd like to specify in the rules that when beating Zira, you need the required ammount of paws for the difficulty. Or in other words, you need to actually beat the level. Otherwise you don't even get the ending credit, meaning you didn't even beat the game.

3. Adding an optionnal Playstation model variable. Since different models can run PS1 games at different speeds (namely 90k being faster than 70k and 75k) I think it's a nice information to add on there.

Given the sheer number of different hardware and OS the game is run on. In my opinion it only makes sense to use in-game time. Plus, after current runs get converted to igt, it'll be easier and faster for mods to tally up full game runs just like in some Sonic Games.

Hey hoXiu and derek31047, current non-deserving Classic 25 WR holder here. This may be a long bit of text, so I hope you have some time to read. I fully appreciate that you're starting changes for this game. The leaderboard really REALLY needs a good cleaning. While I agree it's almost impossible to differentiate between a legit run and a fake one on the first look (unless badly photoshopped), I am comming to you today offering a complete solution while mitigating collateral damage.

First of, let's list all the known ways to cheat:

• Modifying the game files while the game is on
• Using a Cheat Engine-like tool to modify data as the game is running
• Using a Cheat Engine-like tool to slow the game down (that's what I used in the run you jsut accepted)
• Good ol' Photoshop

Then, let's separate run times into four categories:

1. "It doesn't really matter" wich should be verifiable simply using an image in the description (NOT in the video link slot, I'll come back to this later)
2. "Good times that need verification" Those are the regular runs that now need video verification
3. "Seemingly impossible" Where we should draw the line is addressed in the next paragraph. These runs NEED to be recorded externally and see the fingers move on the screen.
4. "Glitched"

So of course the question is now: Where do we draw the arbitrary lines? Well, let's try to make them as least arbritrary as possible. While I don't currently have a specific number for each category right now, I don't mind doing a few hours of first hand research TASing the game to come up with a well thought out number. Until then, we can use the numbers offered by Google Play's official leaderboard (for example in classic 25 it's 2 seconds) for "Seemingly impossible" and an arbritrary let's say 4 seconds for "Good times that need verification" (anything above 4 sec is easily achievable with 1-2h of practice, even less if you use the fast tiles setting only availabe on iOS (not on android and idk about windows phone). These days anyone can get themselves a cheap video recording setup that doesn't take much space if they actually want to grind for WR times. There's basically no excuse not to.

Glitched runs deserve their own subcategories, and just like "Good times that need verification", they should be at least screen recorded so that we can see the glitch in action. Glitches are totally in the spirit of speedrunning, but we need to be able to differentiate between seemingly impossible skill and lucky/cool glitch.

Now, once again, I understand you might not want to accidentally remove legit, well earned runs. But understand, this problem has spread literally like cancer. And I'm not saying that to be offensive, it has literally spread like it (or I guess plague is kinda close as well): it affected more and more runs to a point where we're not even sure wich are clean or not. To get rid of it, collateral damage is needed. And even then it'll never totally be gone, but we can keep it at bay if we took the right measures.

Altough one great way to mitigate unwanted collateral damage is by, (if that's even something mods can do), removing the video verification and moving the image links to the description. This way we can search through the leaderboard using the video-verified variable without flat out deleting old runs.

As for me, like I said I'm willing to spend some of my own personnal time to find well thought out arbritrary lines to separate categories by TASing the game and seeing what's even humanly viable as long as the mods are willing to put the efforts in fixing this leaderboard as well. (note here I said "viable", not "possible", there's always pleasant surprises in speedrunning :) ). Once you guys are on it, please also remove my time wich has been done by slowing the game down to 0.01x on an actual android phone for the mere reason of proving a point.

In hopes to restore all of this leaderboard's potential glory.

Edit: I can remove my own run myself, so that's been done.

I recorded a run in all language settings (but russian, technical issues), cut everything but the text speeches and here's the result:

In any%, english is the fastest and other than having to type different words in the texts prompts, one notable difference in gameplay is that you don't have to rebuild the hidden option to get the laser in any other language than english.

When going for individual levels, here's the best languages: Intro: Polish / Turkish (turkish is slower by milliseconds) Act 1: Danish Act 1 Boss: Doesn't matter Act 2: ??? Act 2 Desktop: ??? Act 2 Boss: English Act 3: English Act 3 Desktop: Turkish Act 3 Boss: English Final: Doesn't matter

Edit: It also seems that it's not worth it to change language mid-run. Changing languages would need to take less than 2 seconds. Here's my Shortest Path Solver spreadsheet to show that. https://www.dropbox.com/s/4dn2aq7m1mxb0uk/Pony%20Island%20Shortest%20path%20solver.xlsx?dl=0 If you wanna tinker with it, you'll need the https://opensolver.org/ add-in as there are too many cells for Excel's built-in solver.

This game seems to have a 1.0 and a 1.1 version. Is there any known differences between the two?

Using the best ¤official¤ hardware possible has always been a thing in speedrunning, that's not a problemI a all. But it doesn't help that consoles are set as categories. Why is that btw? Any%, 100% and All FLIK Tokens shoul be categories, not subcategories, and you already got variables to filter out different hardware. So unless there's actual route differences, you don't need them as subcategories even.

So far it looks like you are. The bot is currently going through every single one of the 87080+ users and should be done in roughly a week if nothing goes wrong. https://www.avasam.dev/global-scoreboard

I'll also release a tool to let people update any user they want one at a time. It already works, it's just not ready for a public launch.

Edit: Wow that link was outdated. It was still referencing an old google sheets from college days XD

This is gold.

I created an issue on Github, ( https://github.com/speedruncom/api/issues/45 ) but since I don't know how often you guys actually check on there, I'll make a post here as well.

Some context: I'm making a global leaderboard where a higher position gives more points based on how many people run the game/category/level/etc. (There's a few rules to make sure this system can't be abused, but this is irrelevant to the API)

My problem: I need to do a new request for every player's PB. Wich will make me hit the 100 request/minute really, really fast.

My suggestion: I need the runs returned by "/users/{id}/personal-bests" to also display the ammount of runners along the position of the run or support embed leaderboards so that I can count the runners myself.

This way I could know a run is 5th/23 place in one request instead of having to do a new request for every player's PB.

On most levels, shooting things stalls the game for a few frame. This is true of every level except for the non-corrupted butterflies (they just fly away) and the File Dump level. This is why you don't want to shoot at enemies near flagpoles or at Jesus. The last level is an autoscroller on a timer (~6:13, from the moment you start the filedump, I've yet to get the exact time), there is absolutely nothing you can do to speed it up or slow it down. It's a perfect time to go get a drink, stretch your legs, of practice the slowmotion glitch on Louey just for fun.

@LaurieDeBeaver Oh didn,t see you got that one as well. @Jarvis4825 3? I only know of this one, and repeating the Azazel startup sequence by clicking the core file too soon.

I also softlocked Beelzebub.exe by doing the fake crash skip too fast:

While I don't care much for running IL, I agree on a per level leaderboard.