Your argument is stupid, you are not allowed to do every command that isn't protected by sv_cheats. Like the commands give or ent_fire are not allowed.

First, explaining why a rule is allowed is kinda useless; but it has been added because people were confusing. So technically we don't need any justification for allowing something. Second, your argument is stupid; since non-sv_cheats-protected commands are not ALL allowed, changing the justification is not a good idea. So unless another Portal 2 runner gives his opinion, I think this thread should be locked or something; and I think Portal forums being "shitposted" by you and the fact PJC and Pomchee2 "liked" what I said are agreeing with me.

I don't get why it is allowed either. It's a console command that affects the gameplay, why should it be allowed? Console commands that affect gameplay in any way should be banned.

I don't agree with you @TheMilkMan47. Portal funneling has always been a setting you can enable disable like your resolution or your screen colors in both Portal games. If I thought like you, I would ban BHOP then. It's not how it works tho.

you can bind jump to mwheeldown/mwheelup without using the console

" that affect gameplay in any way should be banned" Affect the gameplay.

The idea that the entire list of non-cheat protected console commands has to be treated the same is kind of silly to me. Each command in question is dealt with on a case-by-case basis. Portal funneling was agreed by a majority of players to be OK, that it did not take away from the gameplay in a speedrun and also because of its presence in portal 1 it was viewed as a more natural option to use. In short, nobody had a problem with it based on what it does. Commands like phys_timescale on the other hand were widely viewed as distorting the physics of the game on a fundamental level and would only serve to worsen the gameplay.