Today is a major milestone for us, both in our efforts to deliver on long-held promises to the community, and to enable major new updates due later this year and beyond.

In this post we're going to cover what's new with today's launch, the recent history of the site, detail some work left to do, and preview what's coming later this year.

# Major changes

We had two main objectives with the new site:

1. Better serve the communities and users on Speedrun
2. Make it easier and faster for us to continue delivering on goal 1.

In order to meet these objectives, we rebuilt the whole site, back-end and front. Our release date was "when it's ready", which... just so happens to be today!

There's too much change to go into everything, but here are some of the highlights:

- **Fresh look and feel.** You may have noticed, but things look a bit different. We tried to keep the original spirit of Speedrun, but update it to look and feel like a website should in 2023. It's faster, prettier, and more reliable. Give it a try, we think you'll like it.
- **Game pages and leaderboards.** [Leaderboards](/only_up) are now wider, faster, and have a variety of new features. You can easily see the world record history, filter by more details (including verification status), and more! Check out a game page to see it in action.
- **Individual level support.** Level navigation is now built into the main leaderboard, and game pages now have a new separate [Levels tab](/pizza_tower/levels) where you can see an interactive summary of level record holders. This view can be filtered in the same way as the main leaderboard, including by subcategory!
- **Game management.** Game management has been completely overhauled. Speedrun is a complicated platform with a lot of configuration options for game moderators. We rebuilt it all with the primary goal of making sure that moderators felt confident when making changes. The site now explains every single option, warns about dangerous changes, and exposes new options to customize your communities.
- **Moderation tools.** We released the Moderator Hub feature almost 2 years ago to mixed reactions. We've been listening and taking notes, and are happy to say that we've rebuilt it from the ground up to address major points of feedback. The pending run list is now more dense, it's easy to search, you can assign runs to moderators, and the run review interface has been much improved.
- **Search.** Search is now faster, more accurate, and finds more content across the site. There's a new dedicated search results page where you can filter results. You can also easily bring up the search box with your keyboard, just press **/**. 
- **Game Discovery.** We've improved the [Games page](/games) to show popular new games and help you discover new games on different platforms and decades. We also standardized game cover image sizes (you may need to update them for the games you moderate.)
- **User pages.** [User pages](/users/Meta) got a fresh look and new features, including the ability to embed your Twitch stream when live, and improved access to various types of content like threads, comments, followers, and pending actions.
- **User following.** You can now follow users (in addition to games), and their runs will show up in your feed on the home page. User pages have Followers and Following tabs to help you discover new friends. We hope this will help you keep tabs on old friends and discover new game communities.
- **Group messaging.** We've overhauled [direct messaging](/messages) so you can make plans with the whole squad.
- **Guides and Resources.** We've given guides and resources a minor facelift, with more improvements planned in the future. You'll be happy to know that you can now drag and drop images and videos to upload them directly into guides, resources, news posts, etc.
- **New text editor.** The old Speedrun supported a weird markdown-ish text format, but didn't have an easy way to use it. We now have a new text editor with multiple modes (rich text, markdown, preview), which should make it a bit more pleasant to contribute guides, resources, news posts, or just express yourself when submitting a run or comment.
- **Internationalization.** Accessibility is important, and there's nothing more inaccessible than a webpage that you can't read. Speedrun is now fully translated into 17 different languages. The current translations are machine-generated, and their quality can best be described as "usable". Despite this, we see this as an important step forward for speedrunners who don't speak English, and we plan to make improvements.
- **Single sign-on and verified social connections.** You can now sign in with Discord, Google, or Twitch. Additionally you can [verify your Discord and Twitch](/settings/socials) accounts, giving your visitors confidence that they're talking to the real you.
- **... and lots more!**

It really should simply be *"more, better, faster"*.

We tried to make sure that all major existing functionality of the old site has been preserved or accounted for, but please let us know if we missed anything. The best place to do so is either in [The Site](/forums/the_site) forums, or by creating a [Bug Report](/support/tickets).

# History and lessons learned

Elo (the company that owns and operates Speedrun) acquired and began operating the site in 2020. Back then the site was struggling just to stay online. You may or not remember the famous **"Under Pressure"** error message that used to appear on nearly 40% of page loads.

After we took over, the first task was stabilizing the site and solving some of the most obvious problems. Then we went and started adding features - some went over well, others most certainly did not (sorry). Through it all we experienced a lot of growth (site traffic more than doubled in a year), and learned some important lessons.

The biggest thing we learned? We needed to slow down, communicate thoughtfully, and deliver on the promise and potential of the site.

# Making big improvements

In mid-2022 we recognized that it was simply too hard to make progress on the features that users cared the most about, and we struggled to resolve complex bugs. Under the covers, Speedrun is actually an incredibly complex platform (you wouldn't believe the nuance involved in determining the place of a run!), but the software wasn't scaling in the way it needed to. The old site (PHP) was really showing its, and making improvements was both difficult and dangerous - not a good combination.

***... we had to rebuild it ...***

Rebuilding a complex piece of software is a last resort. It's especially difficult and complex when you need to do it at the same time as you keep the existing site up and running. Still, we think it was a necessary step to making the major improvements the site needed. It took a while, but we're happy with the result! Even more importantly, we now have the ability to iterate on the site (introduce features, fix bugs) much faster and more thoughtfully than before.

For the curious: the old site was written in PHP, and the new site is Go (backend) and TypeScript (frontend) - just over 300,000 lines of code. We store data in MySQL and Redis.

# We're not done yet

As with any big migration, there are bound to be limitations and loose threads. The biggest limitation with the new release is that we were not able to make any changes to the mappings between categories, levels, and variables. The reason is simple: so long as the old site was involved, it'd be nearly impossible to correctly introduce new mapping logic. We did manage to make some improvements in this area, but it's far from our true goal of arbitrary custom mapping. So, this remains on our todo list - we hope to accomplish it later this year.

Another area for improvement is internationalization. As described above, it works, but the translations are not very good. We plan to improve them in the coming weeks and months.

# Looking toward the future

We're incredibly excited to launch the new Speedrun, and are already hard at work on making more improvements. Once the dust settles, we're confident you'll enjoy using the site.

Additionally, we have a few areas of focus that we'll be working on this year:

- **Make it easier to improve your PB.** We plan to introduce new features that will help you understand your runs, learn from other runners in the community, and improve your times. It's going to get *fast* in here!
- **Discover new communities and friends.** The Speedrun community is social by nature, but it can be hard to find new activities. We plan to make it easier to stay connected with existing friends, meet new ones, and improve all of our game communities.
- **Encourage the spirit of competition.** Speedrunning is competitive by nature, but it's far from organized. We think we can help bring some excitement and order to the chaos. Buckle up!

Big updates aside, you can expect a fairly steady stream of minor improvements over the coming months.

# Closing thoughts

We hope that you're pleased with today's update. It's been a long time coming!

I'd like to offer a special **THANK YOU** to our [Speedrun Supporter](/supporter) subscribers. For those who aren't aware, Supporter helps you contribute directly to the development and growth of Speedrun. It offers a variety of features to improve your experience on the site, including making the site faster and more enjoyable to use by removing all advertisements.

For those who aren't subscribed to Supporter but like what you see here, please consider it! Your support means a lot to us, and it really does provide us with the resources needed to continue making major improvements.

Now, where was I in [Tears of the Kingdom](/totk)...

We're excited to launch the new Speedrun website! Read on to learn more about what's new, how we got here, and what's coming next.

Welcome to the new Speedrun

@michael_00006 technically the "Galaxy Cycle" bc i found it already found it before him, and naming strat names based on usernames like ex. "AggeL cycle", "Zora Skip", or "The Quadro Route"  etc. Is just pretty cringe and lazy 

omg im pissing and screaming out cum, this is so ijnsane 

@Raf_The_Gamer The level isn't even on 1.70.

You forgot to credit Alex for making the 1.70 patch lol

@Michael_00006 why are you responding to 2 year old posts lol.

Happy Wheels

Pudding Monsters

There are a few important rule changes that will be implemented from now on, and I'm gonna try to explain them in this post. If you have any questions regarding the rule changes, feel free to message me or any moderator! 

1)Live recordings for Flash / JavaScript IL world records are now required (this doesn't apply to mobile runs)

From now on, replays of runs that are WRs won't be accepted into the leaderboards. This is to prevent pause buffering, which is banned for individual level runs (still allowed in RTA timed categories like Demo or AFL). In order for your WR run of an individual level to get verified you'll need to record it in real time, instead of using the "view replay" function of the game or recording a TJF replay. Anything that isn't a WR run can be recorded using replays. So, to recap

Live recordings of runs: Required if the IL run is a WR
In-game replays: Can be submitted for any IL run that isn't a WR
TJF replays: Can be submitted for any IL run that isn't a WR *IF* you have verified your TJF account using this level https://totaljerkface.com/happy_wheels.tjf?level_id=10767808

It is also HIGHLY recommended that your WR run is above 20-25 fps , as intentionally slowling down the game is banned. Any IL run that isn't WR should still be above 15 fps.

2) 90% speed floor for mobile world records

From now on, recordings of mobile world records being less than 90% speed is grounds to have your run rejected. This shouldn't concern most players, as there are very few runs that go below 90% speed on the leaderboards. This is similair to the 20 fps rule for PC. 

These are the rule changes! Again, if any of you have any questions or want any clarification, feel free to message any of the 3 active mods! 

Small footnote to this post is that there are now new categories in the category extensions leaderboards. The current additions are Demo% Bloodless and segmented AFL runs (33-34 levels each, excluding the unbeatable levels, split into 4 runs) although other categories will most likely be added soon. If you have any suggestions make sure to post them in the #suggestions channel on our discord server or message a mod!

Important rule changes + Category Extensions

Hey everyone! I have some great news for the mobile players, as the apple/android split is finally into effect! Apologies for the delay. That means that starting today, the "Flash / Mobile" category is renamed to "Flash / iOS" (and all iOS runs are to be submitted there) and the Javascript category is renamed to "Javascript / Android" (and all Android runs are to be submitted there). It will take us some time to fix the leaderboards and put every run in the correct platform , but I'm hoping that by the end of November it will be fully sorted. If not, the blame is on me. 

Incase you're curious as to why this split is happening , watch @Michael_00006 's video on the split here: https://youtu.be/jFt78Okhw20

In addition to that, since we're doing work on the leaderboards, we will attempt to tidy up all the IL leaderboards (mobile and PC). By that I mean removing all real-time times and only leaving in-game time on all runs and correcting information (wrong platforrm, wrong charachter, wrong date, wrong time, etc). Incase you weren't aware, when submitting runs, you should only include the in-game time, and leave the real-time space blank. We usually fix it nowdays, but there are a bunch of runs from a few years back that are all messed up, so we'll be attempting to fix that by the end of November too. 

Thanks a lot for reading, I hope you all have a good day!

Apple/Android Split + Tidying up the leaderboads

Hi! A few things have been decided, so I thought a post here was neccesary. First of all, a clarification on the rule we set in July of last year to deal with pause buffering. 

Pausing during runs *IS* grounds for your run to be rejected, however that doesn't mean a pause = rejection. If the pause is deemed to not grant an unfair advantage or to not have effected your run, it may be verified. Try to avoid pausing during WR runs as much as possible though, to avoid having a chance of your run being rejected.  This is only for IL speedruns, not for full game categories. 

Incase any of you don't know, the 1.70 version of the game which can be found in the "resources" gives you a slight advantage in the levels it does include, over the 1.87 version (latest flash version) or the current TJF version. Times ending in xx.x7 in newer versions, get rounded up to xx.x6 in 1.70, so if you're grinding a level that's also included in 1.70 it might be worth looking into that and playing in that instead, as that difference *IS* counted in the speedrun.com leaderboards. 

Character set runs on iOS with advertisments will now have -8 seconds removed per ad (due to there being an 8 second long pause on iOS for every ad whenever you have data turned off). There's still an unfair disadvantage to iOS players for these runs tho, due to the slow-mo that's activated near the end of every level. For that reason, we made a sub category for iOS runs and android runs to be seperated in character set runs as well. 

In less significant news, 2 new roles have been added to the discord server! One is "Runner", given to anyone running the game (come by the server if you'd like it! https://discord.gg/bUpVgtqzgT ) and "WR Holder" given to anyone holding a WR of any kind (iOS, android and pc, IL and Full Game) excluding Apple Shooter , Rap Battle 3 and The Secret Code due to all 3 being low-effort tied WRs. 

That's all! Let me know your thoughts!

Pausing during runs rule clarification and more

Once again this summer we're hosting Happy Wheels Racing League for the 2nd time! In this post I'll try to address any questions you might have, more specifically:

**1: When and what is it?**

**2: How do the leaderboards/points work?**

**3: PRIZE POOL! (What do the winners get?)**

***1: When and what is it?***

The event will be held weekly every **Saturday** from **June 29th to August 31st** at **4pm GMT**. Conversions to each of your local timezones can be found via googling (ex. "4pm GMT to Greece").

We'll compete in levels made by the community specifically for HWRL. One level per week, that gets published at the exact time the event starts (**4pm GMT**). People outside the discord can participate and be listed on the leaderboards via saving replays on TJF, but they can't receive any prize (listed later in the post). The hub for HWRL is the discord server (which you can **join here**: [https://discord.gg/j8869puaMH](https://discord.gg/j8869puaMH "https://discord.gg/j8869puaMH")) and it's good practice to enter VC for the first hour from publication of the level, which is when most of the fun and strat sharing take place!

***2: How do the leaderboards/points work?***

*-Leaderboards*

There are 2 leaderboards in which you can compete for each level, the **1-hour leaderboard** and the **1-week leaderboard**. The former takes place exclusively during the first hour from publication of the level (so if everything goes well, 4pm-5pm GMT). At the end of the one hour we write down the times listed on the in-game TJF leaderboard, and give out points accordingly. The second leaderboard can be participated in until the next level rolls around, so the next Saturday at 4pm GMT (1 week since publication).

*-Points*

This is the model for how points are given out on each leaderboard by placement:

1st - 5 points

2nd - 4 points

3rd - 3 points

4th - 2 points

5th- 2 points

6th - 10th - 1 point

11th - ? - 0 points

The points are calculated throughout the event and the combined points from all leaderboards make up the final leaderboard which dictates the winners. There are some exceptions to the above giving of points, however, and that has to do with the **level creator** EXCLUSIVELY FOR THE 1-HOUR LEADERBOARD

The **level creator** gets 3 points regardless of placement, unless they are 1st place, in which case they receive 4 points. This effectively means the level creator has to work harder to receive the higher-end points to balance the knowledge of the level that the rest of the competitors don't have, but also automatically get 3 points even if they place low as a reward and a thank you for contributing a level. Again, this *ONLY* counts for the **1-hour leaderboard**, as by the time the 1-week leaderboard rolls around the rest of the players should have had enough time to catch up.

***3: PRIZE POOL (What do the winners get?)***

There's been an upgrade from last year, we now have MONEY! **Must be funny, in the rich man's world! Now alongside the designated roles that are given out (for *level creators*, *participants*, and seperate roles for *winner*, *2nd place* and *3rd place*) the top 3 will also receieve a **cash prize**. What Michael and I can provide is the following:

1st place - 15€

2nd place - 10€

3rd place - 5€

**IMPORTANT SIDE NOTE:** If anyone wants to "sponsor" HWRL and contribute to this prize pool you'd be more than welcome to, and thank you in advance! Even an extremely slight donation to increase the prize pool would be great and all of it will go to the winners.

If Michael or I end up in the top 3 we will donate our would-be earnings to a charity of our choice.

And that's basically it! If you have any other questions or concerns feel free to ask in the discord and @ either me or Michael so we can promptly answer. See you *VERY* soon!

**June 29th 2024, 4pm GMT FIRST HWRL 2024 LEVEL**

HWRL 2024 Official Announcement 

Hey everyone! In this post we will be announcing some very major rule changes for the SRC leaderboards. Incase you just want the summary, here they are very briefly: 

*NOTE: None of these rules will be enforced retroactively, just from this point (January 3rd 2025) onwards.*

**1. Every mobile WR on both iOS and Android now needs to have a real-time recording**

**2. Every PC WR will now require AUDIO alongside the real-time recording in order to be verifiable (tips on how to make this easier for you are included later in the post)**

**3. The following types of runs will now require a real-time recording to go along with it, regardless of whether it's WR or not:**

- Runs that use an **existing buffer** *(with slight exceptions; read post)*

- Runs that use what looks like a **slightly modified** version of an existing **buffer** or **run** *(grounds for rejection)*

- Every **helicopter launch** that is **top 3** for helicopter man within the given level

- Every run that uses **ghost hands**

- Every **Backyard Wrestling sub 4.60**

Those are the new rules, incase you'd like more details stick around

**1. Every mobile WR on both iOS and Android now needs to have a real-time recording**

Until now we were only enforcing this for PC runs, but due to recent discoveries we must also enforce it for iOS and Android runs. This means that the WR cannot be in the form of a replay, and can only be submitted if it was recorded in real-time. 

Also, this is obvious but might as well mention it, even for non-WR runs if you do submit a replay the replay needs to be accurate and showcased from start to finish. Only exception is the well known iOS bug where the replay is accurate but the finish screen with the final time doesn't pop up. In those cases, you should 100% show the beginning so that we know the time displayed with certainty.


**2. Every PC WR will now require AUDIO alongside the real-time recording in order to be verifiable**

This is *already upheld* by most top players (I checked the last **20** WRs submitted to speedrun.com for a sample, and ALL 20 had clear audio of the game in them) but we hadn't been enforcing it by rule until now. 

If you want to separate game audio from anything else you might be listening to, there's a tutorial on how to do that on OBS [here](https://www.youtube.com/watch?v=XUa7mrpIFoE&ab_channel=SlurpTech). You can still have other audio tracks audible in the final recording as long as the game audio is still relatively audible. 

This rule only applies to PC for the time being because we recognize that depending on what phone you have sometimes recording exclusively internal audio can be hard. This might change in the future depending on playerbase needs. 

**3. The following types of runs will now require a real-time recording to go along with it, regardless of whether it's WR or not:**


**- Runs that use an existing buffer**

Any run that uses a buffer that is known to exist in the community, regardless of leaderboard placement, will need to have a real time recording to go along with it to make sure it was performed in real time. 

A very noteable **exception** is the beginning of any **combine** wrecking ball run (as in there is no need to get that in real-time). There are definetly more in this list of exceptions, so if you're not sure whether or not something constitues a live recording, message us and we will clear it up. We will attempt to take this on on a case by case basis to see which ones make sense to enforce this for and which ones don't.

**- Runs that use what looks like a slightly modified version of an existing buffer or run** *(grounds for rejection)*

This is to avoid people taking existing buffers or runs, changing a few inputs up, and attempting to bypass the previous rule. If we suspect a run is using this method and the run doesn't have a real-time recording, it will be grounds for rejection.

**- Every helicopter launch that is top 3 for helicopter man within the given level**

Due to the easy-to-buffer nature of helicopter launches, any helicopter launch that is within the top 3 runs for helicopter man in any given level will require a real-time recording to ensure its legitimacy. This may be expanded to more than just top 3 in the future.

*Note: Stuff like doing a small launch at the end of levels like Make Way do NOT count towards this rule. This rule is exclusively referring to levels where the entirety of the gameplay basically consists of a helicopter launch.*

**- Every run that uses ghost hands**


Here's a brief explanation by @LethalPotato on what ghost hands are: 

"On TJF, if your character's hands are grabbing something (either via holding space or grabbing a non character vehicle), and you reset the level, it will cause your hand(s) to not have collision upon eject, which can cause replays to desync and be inaccurate. 

Ghost hands in general gives an advantage on most levels, as ghost hands on irresponsible dads child stops it grabbing the vehicle, and also can cause clipping walls to be easier for some unknown reason (levels like speedbridge and king of pop)

Holding space before ejecting with ghost hands causes them to maintain collision until letting go of space, which allows launches with HM to be the same"

Here is an example of ghost hands being implemented by @Demonic_Ninja in his [Ghetto Dunk 4.67
](https://www.youtube.com/watch?v=Cpd3HN0dn2Y&ab_channel=Demonic_Ninja)
Due to how ghost hands interact with replays, any run that uses this bug is required to have a real-time recording.

**- Every backyard wrestling sub 4.60**

Similar to helicopter launches, due to how easy buffering a backyard wrestling run lower than 4.60 (4.60 because that's the lowest time you can get without using the trick specific to this level) is, we're requiring a real-time recording for all sub 4.60 backyard wrestling runs

**These are the new rules!** If you have any questions after reading the entire post, feel free to ask either in the [Discord](https://discord.gg/j8869puaMH) or DM any of the active moderators! If you have any disagreements, also feel free to voice them, although I hope it's understandable why these rules had to be put in place to ensure the competitive integrity of the SRC leaderboards. Thank you!
