[SOLVED] Null-movement is Broken :(

[hüligan]

Null-movement scripts, which rely entirely on aliasing their movement-based commands, seemed to be broken now. This is in spite of the patch notes suggestion (> Disallow aliasing any existing convars that are not movement commands).

Quite the annoyance to boot into a match and not be able to move, especially when these scripts have existed for years with no issue. Is there any legit reasons for this clamp-down on aliasing commands? I don't recall any exploits related to them. Maybe using them to bind commands for that sv_cheats exploit, but they listed that as a separate fix in the patch notes.

[hüligan]

Originally posted by puffy.:

does crouch jump script still work?

Can't say, I never used a crouch-jump script. Do you still notice that camera jitter you get when you crouch-jump with the script?

[shitreg]

Funny, I was half expecting my null-movement installation to stop working as well as my quick-engie config too, but both seem to be working for me. Are you using the mastercomfig variant? Maybe there's something about the way that one's implemented that makes it still work?

[hüligan]

Originally posted by doggy go woof woof:

Funny, I was half expecting my null-movement installation to stop working as well as my quick-engie config too, but both seem to be working for me. Are you using the mastercomfig variant? Maybe there's something about the way that one's implemented that makes it still work?

Nope, same old autoexec.cfg I've been using for a decade. Would you mind sending yours over?

[Niterux]

they work fine, nothing has changed in regards to null movement scripts, null movement scripts dont work by aliasing over existing commands

[hüligan]

Originally posted by Niterux | quickplay.tf:

they work fine, nothing has changed in regards to null movement scripts, null movement scripts dont work by aliasing over existing commands

Could you send over whatever commands/config you're using? I've tried some other solutions and none have worked so far.

[Niterux]

alias +mf"-back;+forward;alias cf +forward"
alias +mb"-forward;+back;alias cb +back"
alias +ml"-moveright;+moveleft;alias cl +moveleft"
alias +mr"-moveleft;+moveright;alias cr +moveright"
alias -mf"-forward;cb;alias cf"
alias -mb"-back;cf;alias cb"
alias -ml"-moveleft;cr;alias cl"
alias -mr"-moveright;cl;alias cr"
alias cf
alias cb
alias cl
alias cr
bind w +mf
bind s +mb
bind a +ml
bind d +mr

[Niterux]

make sure to not be putting these commands into config.cfg as mastercomfig overrides this file

[shitreg]

If you haven't already considered, I'd highly recommend using the mastercomfig setup @ https://comfig.app/app/
Lotta tweaks to play with but in your specific case, you're focusing on the Null-Cancelling Movement addon to add.

[hüligan]

Originally posted by Niterux | quickplay.tf:

make sure to not be putting these commands into config.cfg as mastercomfig overrides this file

Yup, no worries. Putting them into my autoexec, which is in the overrides folder, so it should work. Gonna test it now, thanks in advance!

[hüligan]

Originally posted by doggy go woof woof:

If you haven't already considered, I'd highly recommend using the mastercomfig setup @ https://comfig.app/app/
Lotta tweaks to play with but in your specific case, you're focusing on the Null-Cancelling Movement addon to add.

Already got mastercomfigs installed. Last time I tried using the null-movement addon, it didn't work so I went back to the tried and true.

[hüligan]

It worked! Thanks again.

It's really strange because this was basically the exact same as my existing config. Chalk it up to Source spaghetti I guess.