oSkill (08-02-2013)
Ok,i've been wondering if it's possible to make a propkill script,without using any Garry's Mod script;this means,without any bypasser needed.
I've succesfully discovered how,So i've decided to make a super little guide,here,on mpgh.
First: Picking the necessary.
You'll either need:
a) basic autohotkey coding capability
b) a macro-able mouse or keyboard
Without one of those,you'll have to wait for someone to code the script.
Second: Setting up.
The first part of the setting up is to bind a key to turn left/turn right inside gmod.
To do this,click on options,scroll all the way down and bind the keys. I use the left and right arrows.
Next,the turn speed.
Open the console (google how if needed) and type in: cl_yawspeed 2500.
Then,check the keys you've chosen work correctly (the screen should rotate incredibly fast.)
Third: The macro.
Pick up your hardware's macro editor (in my case,steelseries' setup) and bind any key to a macro doing this:
-Right arrow down
-hold 76 ms
-Right arrow up
-Wait 25 ms
-Mouse1 down
-Wait 25 ms
-Mouse 1 up
Right arrow can be swapped to Left arrow,to turn the other direction.
Right arrow and Left arrow can be changed with any key.
This will result in a (not totally perfect) 180° turn.
Doubling 76 ms to 152 ms should result in a 360°.
Dividing it to 38 ms will result in a 90° turn.
ALSO,remember the longer the keypress the higher the spread is.
With 76 ms,the spread can reach 20°(!)
But most of the times the spread is a 5-10°,perfect for a close throw anyway.
IF you have a more-advanced macro editor (lolwtf? good mouse u have there lol) then you can bind all the above to the keypress and bind the opposite (taking away the mouse1) on the release,so you'll end up like how you started (THE OPPOSITE MAY BE MORE PRACTICAL HOWEVER!)
Happy propkilling![]()
oSkill (08-02-2013)
This is actually a pretty good tutorial. One thing I would suggest is adding something that explains the core functions of AHK that would assist them.
Auto hot script is just a program that runs scripts,used mainly for macros.
How would this information improve anyhow? IF someone manages to make a AHK script,then i'll add more information like download link,main features and such,also how to use the script in detail. But at the current state i miss to see a reason to do so
---------- Post added at 08:35 AM ---------- Previous post was at 08:13 AM ----------
I've been doing some tests and:
1) FPS changes the degrees of the launch.
This means: you need to have a fixed amount of fps,anywhere anytime,else the throw will spread away.
2) having a 200-250 ms delay before pressing mouse1 will prevent the prop being thrown to the side. (caused by latency,if tested in SP the throw will always be precise)
The fps can be limited to a higher or lower amount than 55-60,this means the ms needed of turning are variable,from 65 to 200. depending on how many fps you have.
Derpmode.....
Last edited by austen407; 07-31-2013 at 09:44 AM.
change the speed of the physgun to 150 then scroll wile holding a prop
*KFC* (03-24-2015)
Very Creative, thanks for the post man. We need more people like this.
oSkill (08-02-2013)
More than that,i think in many cases the delay is rounded up. so it has a +/- 5ms precision.
Indeed,that'd perfectly explain what happens after a few tests:
around 60% of the shots (tested with the hl2 crossbow XP) go in an almost perfect 180°,while on the other 40%,the shots spread to either the right or the left,by alot.
This may seem fine,however when using it in a server:
1) ping gets into the equation
2) the server might handle your input and round it itself (rare)
Wich means MANY of your shots will miss and mostly the 20% that goes to the left is somewhat precise.
SO this either needs pixel's precision using a AHK script (check the thread "Is it possible to..." to see how it's going with AHK) or either it's almost unusable.
It shouldn't be that hard to prop kill, you just turn really fast and let go of the prop. I mean, it's so very simple, do people need an Automated Ass Wiper also?
The only problem I see is if someone is moving, or its a smaller prop and you need to aim exactly 178-182 degrees behind you for it to hit them, that you'd miss because you're off or they moved and if your horizontal view has shifted also or is not on level.