Posted 4 months ago by

Hey everyone! In this news post we'll be:

1)Announcing what we'll be doing in the weekends! (Finally)

2)Clarifying our new rules for emulators and other mobile-related rules

IL Sundays Rebooted (ILS #2):

Ever since HWRL ended in the summer, we've taken a bit of a hiatus on weekend events in the server. Now, we're back! The way IL Sundays #2 is gonna work from now on is we'll be switching between 2 types of ILs every week. One week we'll do a regular AFL or mobile level, the next we'll do a semi-recent TJF level, and repeat! The AFL/mobile level we play will be based on recent strategy creations and possible exciting world records that makes grinding them as a community make sense, and the TJF level will be picked by the mods to showcase good levels that are still being made that might go under the radar! It can also be used as a way to showcase cool levels by our community members! The first level we're playing in this new iteration of IL Sundays will be Happy Green Hills, at 8pm GMT! This is because of the new strategy (and world record!) by LethalPotato using pogo, and it'll be a chance for all of us to get good times using it! If you're not already in the discord, join us! It's highly encouraged we all do this in VC and try to help each other out!

IL Sundays 2: November 12th, 8pm GMT: Happy Green Hills

New emulator and mobile rules:

With all the new mobile WRs performed on emulator, we thought it was a good idea to start making rules regarding emulation to maintain the competitive integrity of the game across all platforms going forward. These are the new rules you need to follow if you're doing a run on emulator (Both IL runs and Character Set runs)

  1. A full recording of your attempt session that you got WR on is mandatory (it doesn't have to be super long, but the more footage of before and after the WR run it includes, the better)
  2. Have a constant framerate of 60 (occasional dips to 59 are ok)
  3. Show the framerate throughout the run (Go to the gear icon on the side toolbar > Preferences > Display FPS during gameplay (set to on)
  4. The layout of Bluestacks needs to be visible (Easy way of doing this is just recording your desktop instead of a specific window)

(Note: The emulator you're using needs to be Bluestacks, all other emulators are banned)

Regarding ads in mobile and how we'll deal with them in Character set runs, for iOS we require you use this iOS adblocker for every WR run on character set. For non-WR runs, we'll be removing 8 seconds off your final time for every ad you get (there is an 8 second waiting period between every level; see Jedqwerty's run)

For Android, we require that WR runs use this Android adblocker , and we strongly suggest non-WR runs also use this. If they don't, we'll be looking at runs on a case by case basis to see what time we can subtract.

(^ These rules are subject to change based on community reception, so tell us your thoughts in the discord or in the comments of this post!)

Just a quick note, we've added a few categories lately, mainly some ILs in Category Extensions, so make sure to check those out and submit your runs!

That's all for now, we'll be looking for your thoughts on this, and hopefully we see you at ILS #2!

Read more
Posted 8 months ago by

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) ^^^ 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) 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.

^ THIS IS NOT ALLOWED (1:1 SMF)

^THIS IS ALLOWED (1:1,2 TrapTrac)

^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

Read more
Posted 8 months ago by

Hey everyone! I'm very happy to be making this post given tomorrow (Saturday July 1st, 6pm GMT 1pm CT) we are officially starting Happy Wheels Racing League. All relevant information about this event will be here, which you should be reading if you're thinking about participating!

First of all, what is the event about?

Each Saturday from now until the end of August, we'll all gather in the server (which, incase you aren't a part of, join here: https://discord.gg/bUpVgtqzgT ) and compete on brand new user-made levels straight from our community. The level will be published at exactly 6pm GMT, and the community will have 1 hour to compete on the first of the 2 leaderboards. For the 2nd leaderboard, the times will be counted by the end of 2 days (so Monday 6pm GMT). The times are counted through the totaljerkface website, so a TJF account is required in order to participate, and you'll need to save your replays in order for them to count. If a replay is saved after the time limit, it won't count for that specific leaderboard. For each leaderboard individually, the points work like this:

1st place - 5 points 2nd place - 4 points 3rd place - 3 points Top 5 - 2 points Top 10 - 1 point

The following are banned:

  1. Pause buffering and lag abuse If there's a suspicion of pause buffering or lag abuse it will be looked into, and if someone is found guilty it could result in a ban from the community as a whole. Play fair, we're all trying to have fun!

  2. Hoarding replays/strats until the very last moment If you have a strat that gives you WR and you're keeping it until the very end of either leaderboard so people can't see it, that will be punishable, and may result in you losing points or being disqualified from the event, depending on intentions and how big the advantage was.

  3. Secret/Developer wins This is for level creators. If there are multiple finish lines, or multiple ways to get to a finish line, you must declare all of them before the level is played. If a creator uses a shortcut which the community deems they made for themselves/deliberately kept secret, that creator could have points reducted.

We still need levels, so if you think you can make a level and have made ok levels in the past, feel free to contribute! We need the help, haha! First level we're playing is Chrepuhon's. If anyone has further questions, feel free to DM me or ask in the server! See you all there <3

--|| In other news ||--

  1. We're now also merging Flash and Java for category extensions!

  2. The rule for what levels can be submitted to category extensions that was always there and wasn't really followed, will now be applied for all future level submissions, but not retroactively. This means levels being submitted must have over 1000 plays , not be self-made, be winnable in a reasonable amount of time, and not be an insta-win level.

3.Regarding the FPS floor rule (20 FPS floor for normal runs, 25 for WR runs), exceptions can be made for especially laggy levels. The ones we currently have listed are:

-Chaos City -Happy Wheels Future (neon area) -Taken 3 -DoTD lv.7 -Subway Rampage -TX Chainsaw Massacre

This list will most likely be updated, so be sure to check the pinned messages in general to see the list!

That's all from me, bye!

Read more
Posted 1 year ago by

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!

Read more
Posted 1 year ago by

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:

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!

Read more
Posted 1 year ago by

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.

  1. 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!

Read more
Posted 1 year ago by

This week we are hosting the inaugural event of the Happy Wheels Racing League. Every week will have a slightly different format, but this week it will be a single map time attack race, where better placement earns you more points. All you need to do to participate is have a verified TJF account by 3pm CST (8pm GMT) on Saturday, when it will be taking place, and you can spend as much or little time on it as you like. learn more here https://discord.gg/73E2zuTxgq

Read more
Game stats
Followers
321
Runs
4,704
Players
499
Latest news
IL Sundays 2 and new emulator/mobile rules

Hey everyone! In this news post we'll be:

1)Announcing what we'll be doing in the weekends! (Finally)

2)Clarifying our new rules for emulators and other mobile-related rules

IL Sundays Rebooted (ILS #2):

Ever since HWRL ended in the summer, we've taken a bit of a hiatus on weekend

4 months ago
Latest threads
Posted 6 years ago
0 replies
Posted 5 months ago
Posted 7 months ago
4 replies