simple cs2 aimbot and esp, for linux only.
- FOV
- Smoothing
- Visibility check (VPK parsing)
- Head only/whole body
- Flash check
- FOV circle
- Box
- Skeleton
- Health bar
- Armor bar
- Player name
- Weapon name
- Player tags (helmet, defuser, bomb)
- Dropped weapons
- Bomb timer
- Min/max delay
- Visibility check
- Flash check
- Scope check
- Velocity threshold
- Head only mode
- Smoothing
- Aimbot
- Triggerbot
- RCS
- Sniper crosshair
Warning
These features write to game memory and carry ban risk.
- No flash (with max flash alpha)
- FOV changer
- No smoke
- Smoke color change
Caution
VACNet 3.0 is better at detecting aimbot and wallhacks. Do not use aim lock. Play with a low FOV. Use visuals sparingly.
sudo usermod -aG input $(whoami)
# Restart your machine (required)
git clone --recursive https://github.com/avitran0/deadlocked
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
Add "input"
to your user's extraGroups
in configuration.nix
:
users.users.yourname = {
isNormalUser = true;
extraGroups = [ "wheel" "input" ];
};
Then rebuild and reboot:
sudo nixos-rebuild switch
sudo reboot
After reboot:
git clone --recursive https://github.com/avitran0/deadlocked
cd deadlocked
nix flake update
nix develop
cargo run --release
Everything is configured in flake.nix
and nix/shell.nix
.
grep -E '^input:' /usr/lib/group | sudo tee -a /etc/group && sudo usermod -aG input $USER
# Restart your machine (required)
git clone --recursive https://github.com/avitran0/deadlocked
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
cargo run --release
Configs are saved in $XDG_CONFIG_HOME
if set (usually $HOME/.config
). Otherwise they're saved alongside the executable.
See radar.md
Best support:
- GNOME (Mutter)
- KDE (KWin)
Good support:
- SwayWM
- Weston
Fair support:
- i3
- OpenBox
- XFCE
Limited/No support:
- Hyprland (poor X11 support)
- Other Wayland-only compositors
Hyprland has poor X11 support for the techniques this cheat uses. This cannot be fixed.
The game still thinks it's running in 16:9 resolution. This cannot be fixed.
Your compositor or window manager doesn't support transparency, or it's not enabled.
The window couldn't be made click-through. This is a window manager/compositor limitation.
Your window manager doesn't support positioning or resizing windows.
Your window manager doesn't support always-on-top windows.