Colorado, USAYou can play the game anywhere, I don't think there are any (major) differences.
LiveSplit (enable manual IGT for splits every 10 levels)
OBS Studio
hi im pac add me as a mod for this board so i can do some testing thanks!
Exactly what Riko said. And to clarify, the site limitation is timing order priority. Say we wanted In Game Time (IGT), Time Without Loads (TWL), and Real Time Attack (RTA) all on the same board. We could leave TWL blank for Console submissions, subcategorize PC vs Console, and easily have each board cohabit the same page, but if we have all 3 timing methods enabled and we choose TWL as the main sorting method, the site assumes that we want RTA as second and IGT as last, which would mess up the Console boards. We can not choose the secondary timing method.
Hi Bluely, Your best bet is to make a new speedrun.com account to avoid suspicion, then record your gameplay with the window data cropped out. If you get asked about the framerate, say you have a laggy capture card. I've used this tactic countless times on my PS4 runs and have never been caught. If you really need to increase your framerate, just do 3 identical runs and interweave the frames between each other to make it look more legit. Good luck!
There doesn't have to be a category on a leaderboard for you to run the game in a way that makes you comfortable.
The rules were edited to not allow the debug menu. The attraction of the speedgame isn't because it's glitch-heavy. There isn't much interest already in the glitched runs, so adding a "Debug%" won't magically make the game popular.
I can't edit the boards, but I've had connections with a few mods over there for a few years now through other communities. I personally like the checkpoint exploits. If we ban them, screenshots are not sufficient evidence of runs. It also makes the autoscrolling levels automatic WRs, whereas the checkpoint exploit adds the last bit of skill that those runs need to be competitive. In some cases it's good, in some it's bad. To simplify it for a smaller community, we've had to allow them.
100% will be RTA by default until a flawless (no track resets) run is finished anyway.
Honestly, it's up to you guys. I get both sides of it. Do you want to optimize the penalty races for RTA or IGT? Either is fine as long as it's agreed upon.
This is the best place I've found for something like this - https://cyberscore.me.uk/game/384
Most of the top speedrunners can beat every single one of these consistently though, so it's not a good indicator of what each record might be. RTA runners in BK and BT don't care for IGT all that much, so that's the reason there aren't any here if I had to guess.
Sounds good. I would like to request that going forward you look into using in-game time through manual livesplit entries. Totalling up everything post run would be a nuisance for everybody, confusing to a viewer, and harder to verify. Additionally, if RTA is as useless as you say it is, it shouldn't be too much of an issue.
In resources, I have uploaded an example template livesplit layout file. It has a smaller RTA timer up top and an IGT timer at the bottom (with decimals). When you begin a session using your standard split key, a window pops up. By entering the segment time, it will add it as an entry to your splits. Feel free to ignore RTA until the end of the run, but do submit it as the secondary timing method. If a race is ever retried, leave IGT submissions blank. If you would like a previous run of yours retimed, just edit the submission with an accurate IGT for re-verification. As a courtesy, I have done this for all eligible current personal bests for everybody. Of course, feel free to change around the livesplit layout file to your liking to match your stream's theme or personal preference, and if you have any questions, this is not a bad place to reach me.
Due to framerate adjustments to compensate for the different equipment, most games of this era are slower on PAL. There are a few exceptions, such as Crash 2 (still NTSC faster for TAS) where a change in the speed of the character overcompensates for the framerate. Feel free to do some testing on your own for this game
Yes, but how much time do you add? It's hard to tell especially during the run to see what the timer is at when you restart. This is the same problem with doing IGT in games like Super Monkey Ball, but it's even easier in that game because it shows a still timer when the game is paused. In this game, the timer disappears. Additionally, if I were to look through at the last time shown before a pause, it could be inaccurate if somebody is recording or streaming at 30fps instead of 60fps, or especially if there are some dropped frames. It simply doesn't seem feasible, but maybe a loadless plugin would work better.
I understand your concern and I am open to change. Adding an in-game time column wouldn't be a bad idea if the game provided a file timer, but it does not. What do you propose happens to the game timer if you restart a race, as the 100% does?
Can we keep the leaderboards as they are for IGT sorting, add a second column for RTA times, then an "Accuracy" variable stating whether or not the run should actually be what it was? And the only option for that should be Inaccurate. I'm thinking something like this; 
Not a speedrunner (or even a player) of this game, but here's my two cents for a game like this.
Current Patch / Old Patch subcategories until the game patches are more stable. And if there are certain patches that everybody can still access through downpatching and it's faster, consider allowing it, or having a more main/specified subcategory other than Old Patch. Until then though, always mark runs with an (obsoleting) variable of the patch number, so it's easier to sort runs later if they're grouped together between major updates.
Also, it's probably a good idea to subcategorize some of the categories you have on here. If there was something like 100% or All Bosses, or All Achievements, or literally anything other than Any%, then the names no longer make sense. I would suggest Any% as the category, Solo/Co-op as the first subcategory, then NG/NG+ as the third, then whatever else you need to do. Better to have it messy in the subcategories than in the main categories when runs must be split.
Obviously I could just be way off the mark with my thoughts, and at least the first part might be a good temporary solution. If you do take away 1 thing from this it should be to know the patch number of incoming submissions just for later purposes.
