No ill will towards anyone involved and i wont be naming people, personally find it inexcusable and wrong
Hydra for a while, has had weird commands hiding within the anti dt:
Aside from having crashers/ laggers and whatever else to mess with peoples gameplay, these were supposed to be for ayultie only.
But it didnt stay that way a lot of random or "toxic" people had these commands used on them. example:
people also have crashed seemingly out of the blue.
All commands used:
There also was a plugin on the server running killing of any data one could get from radar angles by spoofing it with a randomint ranging from -180 to 180, only because using this was somehow "unfair" and defeated the purpose of some anti aim tech(Certain cheats use this for resolver feedback, evidently breaking their resolver in the process):
however the biggest problem i have is the data collection that has happened, there was a plugin running on the server from the 8th of august till the 16th of september, and im sure it could be redeployed at any time
All the data collected during the period it was running. which was used to make an ai "neural network" resolver for a hack.
The only reason this was made is because these actions were "excused" because playing the game to collect data wasnt fun
Hydra for a while, has had weird commands hiding within the anti dt:
Aside from having crashers/ laggers and whatever else to mess with peoples gameplay, these were supposed to be for ayultie only.
But it didnt stay that way a lot of random or "toxic" people had these commands used on them. example:
You must be registered for see links
, random person seemingly doing nothing gets hit by sm_prederror
meme:
L 09/21/2026 - 00:19:19: [antidt.smx] "ruzh<1575><STEAM_1:1:423063678><>" set prediction error probability for "Zyy<1581><STEAM_1:1:716557896><>" to 100% for the current round
L 09/21/2026 - 00:19:27: [antidt.smx] "ruzh<1575><STEAM_1:1:423063678><>" set prediction error probability for "Zyy<1581><STEAM_1:1:716557896><>" to 0% for the current roundpeople also have crashed seemingly out of the blue.
All commands used:
You must be registered for see links
There also was a plugin on the server running killing of any data one could get from radar angles by spoofing it with a randomint ranging from -180 to 180, only because using this was somehow "unfair" and defeated the purpose of some anti aim tech(Certain cheats use this for resolver feedback, evidently breaking their resolver in the process):
however the biggest problem i have is the data collection that has happened, there was a plugin running on the server from the 8th of august till the 16th of september, and im sure it could be redeployed at any time
All the data collected during the period it was running. which was used to make an ai "neural network" resolver for a hack.
Collected data:
server_tick game_time client userid view_pitch view_yaw view_roll lower_body_yaw foot_yaw anim_on_ground
velocity_length_xy simulation_time pre_origin_x pre_origin_y pre_origin_z post_origin_x post_origin_y post_origin_z
layer_count l0_sequence l0_cycle l0_playback_rate l0_previous_cycle l0_weight l0_weight_delta_rate l0_order l1_sequence
l1_cycle l1_playback_rate l1_previous_cycle l1_weight l1_weight_delta_rate l1_order l2_sequence l2_cycle l2_playback_rate
l2_previous_cycle l2_weight l2_weight_delta_rate l2_order l3_sequence l3_cycle l3_playback_rate l3_previous_cycle l3_weight
l3_weight_delta_rate l3_order l4_sequence l4_cycle l4_playback_rate l4_previous_cycle l4_weight l4_weight_delta_rate l4_order
l5_sequence l5_cycle l5_playback_rate l5_previous_cycle l5_weight l5_weight_delta_rate l5_order l6_sequence l6_cycle
l6_playback_rate l6_previous_cycle l6_weight l6_weight_delta_rate l6_order l7_sequence l7_cycle l7_playback_rate
l7_previous_cycle l7_weight l7_weight_delta_rate l7_order l8_sequence l8_cycle l8_playback_rate l8_previous_cycle l8_weight
l8_weight_delta_rate l8_order l9_sequence l9_cycle l9_playback_rate l9_previous_cycle l9_weight l9_weight_delta_rate l9_order
l10_sequence l10_cycle l10_playback_rate l10_previous_cycle l10_weight l10_weight_delta_rate l10_order l11_sequence l11_cycle
l11_playback_rate l11_previous_cycle l11_weight l11_weight_delta_rate l11_order l12_sequence l12_cycle l12_playback_rate
l12_previous_cycle l12_weight l12_weight_delta_rate l12_orderThe only reason this was made is because these actions were "excused" because playing the game to collect data wasnt fun
