CS2 & Loader Update (25.05.2025)

lost

Administrator
Staff member
CS2
- Improved grenade prediction accuracy
- Improved visibility check
- Map parser doesn't rely on VPK files anymore
- Non-official maps are supported much better than before​
- Vastly improved speed of initial parsing​
- Added visibility based player ESP colors (must enable "Visibility based colors" under master switch)
- Added flashbang color overlay
- Added detailed out of view mode (draws most esp info on indicator)
- Added player distance ESP flag
- Added overlay in-game button to radar (sets the radar's position and size to match that of the games)
- Added force high GPU priority (reduces FPS drops but may cause higher latency/lag in other software)
- Added projectile ESP
- Grenade prediction now traces the path of the grenade instead of showing the whole path
- Grenade prediction accounts for early detonation cases now (e.g throwing molotovs towards the ground)
- Grenade prediction now accurately uses the jump throw data
- Grenade prediction now immediately stops updating grenade data when a throw is detected (results in more accurate data)
- Radar now supports the cl_radar_scale cvar
- Fixed a crash related to custom hitsounds
- Fixed defuse kit flag color not working when using icon mode
- Fixed bomb flag color not working when using icon mode
- Fixed a bug where out of view indicators wouldn't show up when a player was behind you
- Fixed a bug where secondary color of ESP bars would always have full alpha
- Fixed map parser using incorrect collision groups on some maps
- Fixed a bug where map data wouldn't be updated after map changed

Loader
- Added command line options:
--start - Automatically loads the set software​
- Usage: --start=<id> or --start=<id>/<build>​
- Note: The live build is used as default when no build has been set​
--nogui - Disables user interface when opened​
- Usage: --nogui​
- Note: Available only when --start is in use​
- Usage examples:​
--start=cs2 (equal to --start=cs2/live)​
--nogui --start=altv​
- Fixed a rare case with specific builds of Windows 11 24H2 where injection wouldn't work as intended
 
Top