i feel like this is more complicated than it has to be

Happy Wheels

Hey guys! We've decided to clarify a few things regarding the rules that weren't set in stone beforehand, and were the reason for a lot of misunderstandings, so I hope this post makes it more clear as to what you need in your runs!

**1. Audio Requirements:**

*For Demo Any%:* Any run that's faster than 4 minutes needs to have clear audio of the game, otherwise it will be rejected

*For AFL:* All AFL runs (1.87, 1.70, Any%, Max%, etc) need to have audio. This is done because AFL runs are already quite long and effortful, so having audio recorded isn't that much more effort.

*For Demo 100%:* All Demo 100% runs should have audio recording. This isn't as strict, and exceptions can be made, but please try to have audio recording.

*For Character Set mobile runs:* You should try to record audio for all of those. A specific time hasn't been set, and it's not an auto-reject if your run doesn't have audio, but if it's WR or a competitive enough time it should have audio, and a run not having audio can be grounds for rejection.

*For AFL Quarters (category extensions):* For the most part, all of those should have audio. If it's something obviously competitive, like a sub 30 Q1 , or a top 3 time, then that's almost always an auto-reject, but no audio can be grounds for rejections in less competitive runs too. Try to record audio in all categories whenever possible, it makes things a lot easier!

**2. Screen Stretching:**

Screen stretching has been both allowed and not allowed for a long while now, so this rule definetly needed some clarifying. We banned screen stretching in stuff like $1000 trip that'd allow you to see the win trigger, but if you look at the current Demo WR it's obviously slightly stretched, so what's the deal?

In an attempt to find a good balance between allowing a small amount of screen stretching that gives a bit of an advantage but still keeps it fair and balanced and not allowing extensive screen stretching that breaks the game and isn't fun, we went through multiple ideas and tested until **we settled on 1:1,2**. You might be wondering what that exactly means! I'll try my best to explain with examples, and give you an easy way to figure out how to measure this incase you aren't familiar with this sort of thing. So first off, this is an example of what around 1:2 looks like, aka normal full screen.

**1:2 (allowed, by a lot, obviously)**
![](/static/blob/rnq1j4ej.png)
^^^ The up/bottom sides are double the size of the left/right sides, thus 1:2 (close to 1:2). This is the standard way to play the game.

Here's what 1:1,2 looks like, aka the absoloute limit on screen stretching. This means that if the screen is anything below 1:1,2 , it gets rejected.

**1:1,2 (This is allowed, but is the limit on what's allowed. Anything below that is banned)**
![](/static/blob/7e9j4yn1.png)
**THIS IS ALLOWED ^**

Our original idea was 1:1, which means that the left/right sides and the up/bottom sides are equal, but that was deemed a bit too much, so we settled on a comprimise with 1:1,2. Now, incase you're wondering how to make your window 1:1,2 , here's what I did:

**1) Take a ruler**

**2) Measure the left or right side of your window**

**3) Multiply that by 1,2**

**4) The result is how long your up/bottom sides should be.**

If they're anything **LESS** than that, the run can get rejected. I recommend going a bit above 1:1,2 , to make sure you're still in the safe incase something went wrong in the calculations.

Another way, that's far more reliable, is instead of using a ruler, using a programme to count the pixels (Lightshot, the screenshot app, also does this! If you go to take a screenshot it shows you the exact resolution, and you can use those numbers to figure out what 1:1,2 is)

These are a few more examples on what's allowed and what isn't, so you get a better picture of what this looks like. You'll see *below each screenshot* text that either reads "This is allowed" or "This is not allowed". **The text refers to the image above it.**

![](/static/blob/7z36dqzd.png)**^ THIS IS NOT ALLOWED (1:1 SMF)**

![](/static/blob/qnyp7wnp.png)**^THIS IS ALLOWED (1:1,2 TrapTrac)**

![](/static/blob/4zjw12ek.png)**^THIS IS NOT ALLOWED (1:1 TrapTrac)**

**Note 1:** For this entire post I've been using "1,2". I know in some parts of the world that's written as "1.2". Don't get confused, it's the exact same thing.

**Note 2:** Pressing **"100%"** in the flash player is **banned**

**Note 3:** This was about vertical screen stretching. **Horizontal screen stretching is for the most part not allowed**. Quirks of the game or your monitor that show a bit more to the left or the right than you otherwise could are ok, as long as they don't give you a significant advantage.

**Note 4:** This applies to both full game categories and to ILs

**3. Handcam required for Demo WR:**
Given the competitive state of the Demo leaderboards, a clear handcam will now be required for all future world records in the Demo category. The handcam will need to have a clear view of your mouse and keyboard, and it's preferable that the camera has a top down view. **Any Demo World Record submission that doesn't have a handcam will be rejected.**

**4. Mouse cursor showing required for full game runs:**
Your mouse cursor will need to be visible throughout your run for full game categories for the same "sub x" requirments as having audio enabled (which you can see earlier in the post). That means your mouse cursor must be visible for these runs:

**Demo Any% sub 4**

**All Demo 100%, AFL quarter and AFL runs**

If any of you need clarification on any of these rule changes, feel free to DM or just comment here! Byeee <3

Audio Requirements, Screen Stretching + more rule changes! 

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!
