Thank you for this addendum :)

I found that obvious, but I can see how some people were confused. And yes I have no idea why anybody is thinking we shouldn't be using this.

@@n4tri some people have a bind that sets their sensitivity based on which level they are on

@@ewan1165 Interesting, but how does the bind know the level? And aren't there still multiple values per level?

there is only one answer to the viewsnap debate which is: you keep policing this and soon enough every speedrunner will be forced to use the same setup

Ngl in the past like 6 months I haven't had to leave a game because of bots, sometimes they join but we can just kick them

mh Pain

@@artminer6 Yeah, this Halloween, actually, of the 5 hours I played the game, I only encountered one lobby that was overrun with bots.

@@AkumuVids You obviously didn’t attempt the los muertos contract

@@aliterallumpofcoal9577 i played the los muertos contract twice. Once by myself and with a friend. Only map that was overrun for me was helltrain.

"I got so bored of babysitting Employee 427 that i decided to speedrun Portal"

How the hell did you comment this 8 hours ago

@@ttimmythy Probably Patreon early access or something.

fight club reference

Narthan A. Torres (A.K.A Narrator) has been a staple of the speedrunning community for years, so fair enough that he got the WR.

Aimbot itself is basically just a *Tool* that can be used in *Tool* Assisted Speedruns.

@@angeldude101 it's not aimbot, it's just using pixel skip in their favour, by changing the sensitivity and dpi

@@Gadottinho True, It just looks like aimbot, hence the title of the video. And even if they were using actual aimbot, all that would mean is that it's now a TAS rather than RTA.

It is TAS idk why they say it’s not. using the “console”(tool) to do things that are entirely impossible for humans in a speedrun is a TAS. Unfortunately the moderators for the speedrun didn’t pay much attention in English classes which is the leading factor in them having very little understanding of the words tool and assisted.

​@@reprep8423Okay well the Portal Gun is a tool therefore everything is a TAS Oh actually the fact that you can even see anything at all is a Tool This logic is stupid. Tool in this context means external programs or objects that aren't inherent to what the developers provided. Stripping away that context makes you the one who failed Literature.

quite funny to imagine if this where not possible, and instead runners would have to speedrun typing out commands in console

I had already thought of this shortly after he mentioned changing the sensitivity.

you coul probably also set it up sp they toggle/cycle

@@-YELDAH they'd still probably have them on a spreadsheet or have them all copied to clipboard at the same time in a fancy way

@@ziwuri technically macro software

We quite literally did this in Stray any% (sleep paralysis, penis clip, Seamus clip, etc). Me and a group of probably 10 other people spent hours on end bashing certain corners and walls to try and find ways through.

@@FAT9L did it work

@@CRT_YT of course it did, a speed game wouldn't be complete without that lmao

@@FAT9L im sorry *what* clip

@@tiddly5 you havent seen?

nothing usable on normal servers but cleavers clipping trough glass on trade plaza was always fun to do

Those aren't true seamshots at all since they're still inbounds, just parts of the map where the developer forgot to add collision. The source engine REALLY doesn't like it when maps have any sort of "leak" out into the void, so the whole map has to be completely enclosed in order for it to load correctly. That's also why out-of-bounds objects in source engine games are always placed in their own little rooms. The seamshots in this video are leaks so small that even the engine isn't aware that they exist until you shoot through them, so they don't cause any issues when creating the map. Another fun fact: If I remember correctly, those shutter doors only have collision on the shutter itself, the frame that surrounds it is a separate model that isn't solid by default. So if the map creator forgets to make it solid or put something solid behind it, the doorframe can leave a gap above the shutter that's wide enough to shoot through.

@@asdffdsa8885 in fact, it's not like they are too small for the engine to notice, they are literally 0 in the map, but the engine itself trying to play safe and adding a some space, ends up reducing it because of a SINGLE typo in the code

Himself*

@@Ten_Thousand_LocustsI can tell you ain’t gooning

yes. it is

for that joke i sentence you to pun jail for 10 years

@Pixel I will bail him out

Haha, I like that one

attmay joke yaaay

Heyo pancake

@@Minefnafer22 hi minefnafer o/

huh?

There was actually this guy called Skilloz, who made a documentary about the WR progression of "Blue Yourself", an MK8D speedrun category. He referred to himself in the third person, and talked about how he had invented and performed a strategy called "Glider Strats". Using this method, he got the WR.

In one of Summoning Salt's videos on Punch-Out, he completely glosses over the fact that he holds a record in the game (Might've been more than one actually)

@@cutetigger1037 Msushi used to refer to himself in the third person, but he stopped for some reason.

"players basically shooting portals through the corners of walls" was in several speedrunning PORTAL 1 videos uploaded after 2016

Same here. Msushi's content is always 10 out of 10. Cant tell you how many times I've rewatched most of the vids

Play at a higher dpi but lower your in-game sense to keep the same edpi, you can find calculators for this. This should increase the "resolution" you can use. It may make you more jittery until you get used to it. I use this technique in valorant to teach others how to aim when they start out. From 400 to 800 to 1600 dpi, any higher doesn't really make a difference. I stand corrected, 3200 DPI does actually make a difference. But only in certain edge cases. Playing aim labs I find that I either overshoot or undershoot and upping the DPi seems to give me a little more leeway when aiming, despite having the more then enough resolution to hit a target.

Yeah, 800 dpi is a good one to go for. Also don't forget to increase mouse polling to at least 500hz.

@@gemigames154 true, mine is at 1000hz witch is the highest mine goes.

Video just came out. kzfaq.info/get/bejne/iciqpph6q6nTfYU.html Now you also might have to worry about this deviation in some cases.

@unsubtract 400 because I like the sens of 400

You should watch Karl Jobst, his stuff is epic.

m_pitch is (effectively) cheat protected

Source games can alias entire scripts to a bind which is very useful in doing multiple actions in a single bind in tf2

@@kerbonaut2059 yep, i use a lot of those to the point playing the game without them is so hard because each key does so much at once

We do all these things

that's basically becoming TAS at that point

cringe pfp

@@josephleebob3828 damn bro this was really necessary and added to the conversation

I was thinking about only allowing integer sensitivity values, but now that you mention it, why is console allowed during runs at all?

@@TlalocTemporal A lot of people use alternate keybinds for things, and the console is used for recording demos. Doing away with the console wouldn't really work.

Not all glitches should be patched out though. Keeping some of them around can be a net positive if people find it fun to play with and it doesn't interrupt normal gameplay.

@@cassidy8307 Rocket jumping, bunny hopping... #NotAllGlitches

@@doommaker4000 My favorite thing is how Valve tried to remove bunnyhopping from Source but just made an even more broken variation: accelerated back-hopping.

@@cassidy8307 my approach as a developer is to remove all bugs but replace the ones that add gameplay value with features that are the same or similar but more stable and balanced

@@doommaker4000 is rocket jumping even a glitch though? I feel like it's an intended mechanic in a lot of games

Hello friend

@@00Svo 👀

just thought u might want to know that "enjenuity" is spelled "ingenuity"

Is there anywhere on this website where you aren’t?

cringe pfp

@@josephleebob3828 and do you have problem ?

@@stanke6585 your pfp is cringe its an universal proflem

@@josephleebob3828 and why are you so concern about my pfp?

cringe pfp

im not a furry, not apart of lgbtq and i dont like anime nor gacha so take this from a guy who in your eyes is "normal" you are quite literally the definition of that scene in toy store with all of those buzz lightyear clones in the store. went from being a 9 year old playing roblox and mobile games on your channel to having puberty hit you hard and turn you into the generic edgy teenager: "lgbtq more like lbbq", using the word cringe unironically, "cursed" pfp that is infact not funny at all and im sure that there are other generic traits like that about you which im just not aware of yet. get a life and stop being like edgy teenager who just hit puberty#6885858 "comment too long 🤓"

@@josephleebob3828 something that i can respect about you however is that engineer avatar on roblox. now thats something that i can vibe with.

But only if you have raw input disabled, right? Traditional game input works by periodically re-centering the invisible cursor on the screen and polling its position as a vector of motion, so it's quantified further by the screen resolution. But with raw input on, the actual mouse data is received and scaled by sensitivity (as well as m_yaw and m_pitch that define how large of an angle 1 unit of horizontal/vertical sensitivity is) to get changes to yaw and pitch. That said, people are stating that an average 800 dpi mouse is roughly pixel-equivalent to a Full HD resolution, so you can expect similar results by dropping hardware sensitivity to about a third of that.

Simply: they spend some of the largest amounts of time on a game trying to figure out how to spend the least amount of time on it, it’s funny thinking about it that way.

And using the dev console.

@@renakunisaki use of dev console allows for a lot of qol and such which is accepted by the community as legitimate, and disallowing it’s use entirely would be pointless (since pretty much everyone is fine with dev console anyway) and impossible to incorporate considering how commonplace it is and has been for years in runs.

Then they’d become features, like in Celeste

they are nothing alike, what?

Damn I guess you could say he’s pretty baisted

Just like me fr

most sane osu player

that would just be awful

would cause a problem for seamshots/precise shots without viewsnap where people typically lower their sensitivity. there’s a reason this simple seeming resolution has not been implemented after all of the discussion around this tech

WYSI

is this number scary

OMG ITS THE FUNNY NUMBER WYSI

It's not really the same. In general, the rulesets for both Portal 1 and 2 aren't based on sv_cheats protection: that may be taken into consideration but it's certainly not the defining factor. So ch_createairboat unambiguously *was* cheating, and everyone knew that: but someone joked about it being allowed, hence those runs and that category. This, on the other hand, is just adjusting an option which the game gives normal users: you could do it without even enabling the developer console. On that note, there's a bit of a difference between Portal 1 and Portal 2 here. Portal 1 provides the user with a text field in the options so they can input any sensitivity; this means anti-viewsnap sentiments don't really have an objective basis because they can literally be performed without doing anything a normal player wouldn't do. In Portal 2, however, we only get a sensitivity *slider* which caps out at 20 - this was the main justification for the 20 sens cap that was temporarily implemented. However, we already allow sensitivities far below 1 (the minimum on the slider), so it was much more logically consistent to not have the ban (and as Msushi discussed, capping sens at 20 didn't stop viewsnaps anyway). Last note: binds. You could argue that the bad thing here is that you can press a single button to change your sensitivity, and that a bind should only be allowed if it can be set in the menu. That's a reasonable opinion: it's what we'd call a more "purist" perspective but it's totally valid. But the way these communities have evolved has led, through essentially community consensus, to the rules for what binds are allowed being more open than that: Portal 1 is much stricter than Portal 2 but is still significantly less strict than the purist interpretation.

@@mlugg5499 Thanks for the input. Honestly I still don't like it much. It feels like it both uses control methods outside of what would be available to a typical player as well as ignores certain limitations of the game. (can the slider actually be used to set the game, say, to sensitivity 19.97561? To quote the video, "it's more like a grid, where your mouse can only be at certain points at a given time". Is there actually a point the mouse can be in that corresponds to those settings?) But I suppose at that point it's a matter of opinion. Although a last question: Why was sensitivity below 1 accepted in the period when sensitivity above 20 was banned? I don't really understand that part.

Not really. HL1 and 2 both have scripted categories, and it's all allowed. I can see this being set to its own category, though, but I doubt it.

> It feels like it both uses control methods outside of what would be available to a typical player as well as ignores certain limitations of the game This is nonsensical because the console has been available (either by default or activatable from the in-game menus) in Source Engine games since the HL1 days. Moreover, you don't even need the console because you can achieve the same by editing config files directly (and setting up the necessary binds there). Arbitrarily limiting the precision with which you can set your sensitivity is just that: arbitrary. > Why was sensitivity below 1 accepted Pure speculation, but you can't really ban sens below 1 unless you want to lose a ton of players, because if you are a low sens/high DPI player then banning any sens below 1 pretty much bans you from playing the game. For instance, my current sens in CSGO is 0.9@1000 DPI, which isn't that low in the community as it is around 42 cm/360. If I played at a higher CPI my in-game sens would need to be even lower to compensate. Banning sens above 20 may make more sense initially because nobody *actually* plays on low CPI and ultra-high sens (this is not beneficial in any game). but it was still ultimately a dumb decision. > I don't really like it since it's essentially making macros that automate These are just sensitivity change binds. You might as well ban ADS in single player shooters with ADS since that changes your sensitivity as well. Also, an important distinction making binds different from macros is that binds only allow you to execute one change with one keypress, while macros (using alias in console) allow you to perform several actions. Binds are pretty universally allowed in both speedrunning and pro scenes, while actual macros are banned. For example, in CSGO it is fairly easy to create a jumpthrow macro, which releases your fire button at the same moment as your jump, allowing you to throw 100% consistent smokes. This macro is banned in pro play and also 3rd party leagues, precisely because it is a macro, but achieving the same effect by binding -fire to a key next to the spacebar and pressing both buttons at the same time is not.

@@falsche921 yeah, chances are the slider couldn't actually be used to enough precision to set values that precise anyway. Like I say, this issue only affects Portal 2 (in P1 you literally get a text box where you can type any number your heart desires) but it's still a fair point since there's no reason the games' rules should be in sync. As for why sens < 1 was allowed: essentially, this rule was put in place to try and ban viewsnap, because people deemed it a trick that didn't think should be allowed. Of course, that's not really what happened, but it was the intention. Sensitivities under 1 are a crucial part of the run, and have been for years: they're the "usual" method for performing these incredibly precise shots (such as seamshots). On a strictly objective basis, there's not really a reason to prefer sens < 1 to sens > 20, but in the context of this rule, sens > 20 was the "problem" and banning sens < 1 was essentially impossible because of how widely used and liked it is.

The issue with making it a category is that... well, effectively it's the exact same run, the same route and strategy. It's just that in one case players would spend a few extra seconds firing portals into a corner until they shoot through, and in the other one they won't. Airboat% was different enough to make it a category, this just isn't

@@falsche921 So, if this isn't enough to need another category, this isn't enough to have a debate in the first place, right? So... Nothing changed.

allowing console =/= allowing every console command source games usually have a whitelist of commands and noclip is not on there

macros, clipboard pastes ready for the console, basically any way you can think of normally changing your mouse sens???????

@@finx10097 how is that not cheating. seriously. you're setting the value using a console because the game wouldn't normally allow you to do so. that's what we call cheating.

@@ruinenlust_ In source engine games you have "sv_cheats", which basically turns cheats on and allows cheat commands. With it turned off (by default), it only allows commands that were not considered cheats by developers.

@@mythicalgod You understand that I, as someone who's not familiar with all this, saw this video and was confused right? It even says no cheating in the title but lo and behold it uses console commands. To me it still seems like cheating. Weird rule.

@@ruinenlust_ ok so they also aren't allowed to manually line up the seam shots because they use the pos values screen that have to be enabled via console? Like where's your logic? They pressed the console key so it must be a cheat. Also this is used for OOB speedruns which is also not intended by the Devs for you to be able to do, so the whole category is invalid because they're cheating?

Heyo Dusty

@@Minefnafer22 hi mine, massive industrial fan

@@dustyhob0 omg, me too!

WYSI

Next you're gonna tell me we can't use the word “slope” to describe an incline, because 60 years ago, our grandparents were using it as a racial slur? Get over yourself.

@@hellterminator no, I'm telling you that "spaz" is an ableist slur, because it is. have a nice day :)

@@chluff And I'm telling you languages evolve, so it's not anymore. :)

Spaz isn't a slur in America, it just means to be a klutz. Kind of like how "fanny" refers someone's butt in the U.S., but is a synonym for vagina in other former British colonies.

@@hellterminator if you want to use ableist slurs just because you exist in an environment in which they are considered acceptable, that's up to you. but the vague hand-waving of "languages evolve" is just a post-hoc justification. it simply *is* a slur - what you want to do with that information is up to you.

pretty sure higher max dpi just generally means better quality sensor, since dpi is limited by how sensitive and accurate a sensor is. it's a correlation not causation thing.

i mean even if you don't get this explanation you can sort of figure it out because dpi is the actual input and sens is just magnifying this input, therefore it's obvious you should have it higher