This is a discussion on Darkstorms 3.3.6 (Aimbot, 100% Crit, NoSpread ...)) within the Team Fortress 2 forum part of the Shooter category; THERES IS NOT MUCH NEW BUT ALOT OF FIXED THINGS !1!
Code:
Aimbot:
- FoV or Distance based aiming
- ...
THERES IS NOT MUCH NEW BUT ALOT OF FIXED THINGS !1!
Code:
Aimbot:
- FoV or Distance based aiming
- Melee recognition
- Specify Hitbox
- Optional key-based activation
- Team selectable aiming
- Aim at Sentries
- Aim at Stickies
- Smooth(humanized) aiming
- Triggerbot
ESP:
- Name ESP
- Health ESP
- Distance ESP
- Bounding Box ESP
- GFX ESP
- Class ESP
- Weapon ESP
- ÜberCharge ESP
- Structure ESP
Miscelanious:
- Constant Criticals
- Rapid Switch
- Bunny Hop
- Duck Shoot
- Duck Jump
- Speedhack
- Chams
- No Spread
- No Hands
- Remove Scope
- Wallhack
- Crosshair
Changelog,pls read
Spoiler:
Code:
[ChangeLog]
1/7/2011
3.3.0
~ Fixed crash related to Entity ESP.
* Fixed Wrangler being treated as a melee weapon.
- Changed console output to disclose my UnknownCheats user page instead of my MPC user page, which is now inactive.
1/7/2011
3.3.1
~ Fixed aimbot aiming at the wrong hitbox for Engineer.
* Added Aim Spot feature.
1/8/2012
3.3.2
~ Fixed LEFTLEG and RIGHTLEG using the foot instead of the leg.
~ Fixed GFX ESP showing as ON and OFF.
~ Fixed GFX ESP option 5 not working.
* Changed menu around.
1/8/2012
3.3.3
~ Added anytime injection.
* Centered watermark.
1/8/2012
3.3.4
~ Fixed No Spread missing from the menu.
* Fixed GFX ESP option 5 not using the correct rotation.
1/9/2012
3.3.5
* Added FrameStageNotify interval hook to call the panel creation code to help people with slow load times.
1/10/2012
3.3.6
~ Fixed crit weapon blacklist missing some weapons and incorrectly listing the Fish.
* Added the corresponding aim_spot hitgroup to the triggerbot.
* Fixed menu variables that use a number showing 0 instead of OFF.
* Fixed ÜberCharge ESP showing %percentage instead of percentage%.
- Made menu a little more efficient.
[Only registered and activated users can see links. ]
The Following 3 Users Say Thank You to Eth3rnitY For This Useful Post:
It's only detected if you use the Constant Crits option. The 3rd or so time you fire, it notices that you are always critting, and bans you. Works perfectly undetected as long as you don't use that op.