Skip to content

Conversation

@Agiel
Copy link
Contributor

@Agiel Agiel commented Sep 29, 2025

Description

This is intended to replace the current hard speed cap that comes with the neo_ghost_bhopping cvar. Air friction is applied when going faster than the current max walking speed (based on class and active weapon), and scales linearly with how much faster the player is going.

The friction can be controlled with the following new cvars:

  • sv_neo_airfriction (Default: 0): The amount of air friction applied to everyone.
  • sv_neo_airfriction_objective (Default: 0.5): The amount of air friction applied to the ghost carrier, VIP and juggernaut.
  • sv_neo_airstopspeed (Default: 0): The minimum stopping speed when in the air. Doesn't seem necessary with the default friction value of 0.5, but it's added for parity with ground friction.

For testing purposes, a cheat protected cvar has been added to allow jump buffering.

  • sv_neo_jump_buffer (Default: 0)

For reference, the max speeds set by the nt-anti-ghosthop plugin are:
#define MAX_SPEED_RECON 255.59
#define MAX_SPEED_ASSAULT 204.47
#define MAX_SPEED_SUPPORT 204.47

The default friction value of 0.5 gives us speeds in the same ballpark (tested with jump buffer enabled). Further testing will let us know if the value needs to be tweaked further.

Toolchain

  • Windows MSVC VS2022

Linked Issues

  • fixes
  • related

…gr. This replaces the neo_ghost_bhopping cvar.
@Agiel Agiel requested a review from a team September 30, 2025 10:48
@DESTROYGIRL
Copy link
Contributor

For testing purposes, a cheat protected cvar has been added to allow jump buffering.

image

I know where this is going, skip to the day long bikeshedding debate

@sunzenshen sunzenshen requested a review from a team October 2, 2025 03:11
@Agiel Agiel merged commit 204e841 into NeotokyoRebuild:master Oct 2, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants