

Since Macros Are Not Banned....can Someone Give Me A Gauss One Click Fire Macro?
#1
Posted 17 December 2014 - 07:07 PM
So macro holds down button, and releases as soon as its ready. That way I can treat the weapon as a fire delay weapon instead of hold and release.
#2
Posted 17 December 2014 - 07:10 PM
#3
Posted 17 December 2014 - 07:18 PM
Kain Thul, on 17 December 2014 - 07:10 PM, said:
What he want's is possible. You'd just need AutoHotKey or something similar to, on activation (be that mouse or keyboard button down), to press the weapon group key for Gauss and automatically hold it for [gauss charge time] then release. It'd be trivial to do, but be bad, as you'd not be able to cancel shots that become unviable or choose the release moment. So, yeah you could do it easily, but it wouldn't be a good idea.
As to specifics, it depends on what he uses for macros.
#4
Posted 17 December 2014 - 08:22 PM
Kain Thul, on 17 December 2014 - 07:10 PM, said:
I think you've misunderstood. It can be done in a number of ways with a macro (or through PGI). I don't want to hold the charge forever, just make the macro fire as soon as the shot is ready.
No it wont be bad Wintersdark. Its bad the way it currently is for me. I don't like having all my weapons to be click to fire and hold down to keep firing and one out of nowwhere a weapon is both hold and release the same button to fire based on time. PGI could have given players an option on how to fire guass.
Here are 3 different ways it can be done with the current mechanic in place with just a macro or minor change from PGI.
1. Click fire button normally, as in press and release the way you normally "click" a mouse button. Shot charges to 0.75 seconds and immediately fires as soon as its ready regardless of how you click the button again (repeatedly or just once). Its click and forget. No way to cancel shot.
2. Same as above except clicking the button again before 0.75s is up cancels the shot
3 (my fav). Click button down and hold to charge, as soon as 0.75 seconds hits, shot fires, EVEN if you still hold the button down and don't let go. IF you let go before charge complete it cancels the shot.
If PGI made it like number 3 I would have no problem with the gauss mechanic.
I would like to suggest method 3 to PGI to be implemented, what is the best way to reach someone who could make this happen? Keep in mind it does NOT change the way gauss is currently implemented, it could be a simple menu option like arm lock throttle decay etc
Edited by l33tworks, 17 December 2014 - 08:25 PM.
#5
Posted 17 December 2014 - 09:02 PM
Because this is how you waste gauss ammo
#6
Posted 17 December 2014 - 10:12 PM

#7
Posted 17 December 2014 - 10:24 PM
#8
Posted 17 December 2014 - 11:44 PM
No one is helping the OP with their posts(some people are)... so here you go...
What mouse button do you want to use for the macro? Left Mouse button? Use the Number Pad Enter Key to turn this script off/on (well technically its suspended)... also bind the gauss to the weapon group 6 (and also 1 or your Left Mouse button)
Get Autohotkey for free and copy/paste macro below
#SingleInstance Force
#InstallMouseHook
#InstallKeyBDHook
NumpadEnter:: Suspend
#IfWinActive ahk_class CryENGINE
LButton::
while GetKeyState("LButton","P")
{
send {6 down}
sleep 800
send {6 up}
}
Here is for the Right Mouse button... incase you do not want your left Mouse button used..
#SingleInstance Force
#InstallMouseHook
#InstallKeyBDHook
NumpadEnter:: Suspend
#IfWinActive ahk_class CryENGINE
RButton::
while GetKeyState("RButton","P")
{
send {6 down}
sleep 800
send {6 up}
}
Edited by LORD TSARKON, 18 December 2014 - 09:28 AM.
#9
Posted 17 December 2014 - 11:57 PM
l33tworks, on 17 December 2014 - 07:07 PM, said:
So macro holds down button, and releases as soon as its ready. That way I can treat the weapon as a fire delay weapon instead of hold and release.
you should change your nickname before using a gauss macro

#10
Posted 18 December 2014 - 12:05 AM
Click able > not clickable for 1.5 seconds while charging > clickable
This way you can spam click while charging while saving gauss shots?
#11
Posted 19 December 2014 - 03:23 AM
LORD TSARKON, on 17 December 2014 - 11:44 PM, said:
No one is helping the OP with their posts(some people are)... so here you go...
What mouse button do you want to use for the macro? Left Mouse button? Use the Number Pad Enter Key to turn this script off/on (well technically its suspended)... also bind the gauss to the weapon group 6 (and also 1 or your Left Mouse button)
Get Autohotkey for free and copy/paste macro below
#SingleInstance Force
#InstallMouseHook
#InstallKeyBDHook
NumpadEnter:: Suspend
#IfWinActive ahk_class CryENGINE
LButton::
while GetKeyState("LButton","P")
{
send {6 down}
sleep 800
send {6 up}
}
Here is for the Right Mouse button... incase you do not want your left Mouse button used..
#SingleInstance Force
#InstallMouseHook
#InstallKeyBDHook
NumpadEnter:: Suspend
#IfWinActive ahk_class CryENGINE
RButton::
while GetKeyState("RButton","P")
{
send {6 down}
sleep 800
send {6 up}
}
Hi Lord Tsarkon. I have been not been on mwo for a few days. Just wanted to thank you for posting that and let you know I appreciate the effort you put in. Thanks. Yes mouse button one is fine. Will give it a go soon.
Edited by l33tworks, 19 December 2014 - 03:24 AM.
#12
Posted 19 December 2014 - 03:53 AM
l33tworks, on 19 December 2014 - 03:23 AM, said:
Hi Lord Tsarkon. I have been not been on mwo for a few days. Just wanted to thank you for posting that and let you know I appreciate the effort you put in. Thanks. Yes mouse button one is fine. Will give it a go soon.
I love how in response to a basic request a bunch of jackasses attack the OP before someone finally gives the OP useful information

#13
Posted 19 December 2014 - 03:58 AM
for jumpsnipers with PPC's this may had been some useful thing, but in most situations it wouldn't make sense.
#14
Posted 19 December 2014 - 04:09 AM
Which really makes it a pain for close up fighting. It needs some sort of secondary notice like the crosshairs changing color when charged or something.
#15
Posted 19 December 2014 - 04:10 AM
#16
Posted 19 December 2014 - 04:24 AM
#17
Posted 19 December 2014 - 04:26 AM
Edited by Helsbane, 19 December 2014 - 04:27 AM.
#18
Posted 19 December 2014 - 04:46 AM
#19
Posted 19 December 2014 - 05:18 AM
#20
Posted 19 December 2014 - 05:18 AM
Tahribator, on 19 December 2014 - 04:46 AM, said:
'Sniper Weapons' still fire when you pull the trigger. The break of the trigger is akin to the finest sheet of glass snapping under the pressure of your finger. Your option to abort the shot, is NOT to pull the trigger.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users