972364075 (08-22-2017),ashui2011225 (09-18-2017),Chaos_Trill (12-16-2017),dreiker (11-15-2017),leixi (07-14-2018),maksumus1087 (07-17-2017),poolfish (07-03-2017)
Recently I founded this code and added this script in my mouse.
This code manage to control all type of AR and SMG recoil while tap or spray with normal scope, dot scope, and holographic.Code:function OnEvent(event, arg) OutputLogMessage("event = %s, arg = %d\n", event, arg) if (event == "PROFILE_ACTIVATED") then EnablePrimaryMouseButtonEvents(true) elseif event == "PROFILE_DEACTIVATED" then ReleaseMouseButton(2) -- to prevent it from being stuck on end if (event == "MOUSE_BUTTON_PRESSED" and arg == 4) then recoil = not recoil spot = not spot end if (event == "MOUSE_BUTTON_PRESSED" and arg == 1 and recoil) then if recoil then repeat --Sleep(35) Sleep(8) MoveMouseRelative(0, 2) until not IsMouseButtonPressed(1) end end end
But I wasn't able to make 4x scope and 8x scope's recoil steady. Can someone help me out with this and I am trying to make it when I press a certain key it will switch between all type of scope recoil.
972364075 (08-22-2017),ashui2011225 (09-18-2017),Chaos_Trill (12-16-2017),dreiker (11-15-2017),leixi (07-14-2018),maksumus1087 (07-17-2017),poolfish (07-03-2017)
It would take testing, but depending on the amount of recoil you want adjusted, raise or lower the Sleep(X) to get more recovery or less recovery.
Higher number of sleep will mean it has less recovery and lower number will mean it has more, like i said tho, it will take testing to get it perfect for 4 and 8 times scopes.
If it isnt enough you can also raise or lower the MoveMouseRelative(0, X) to increase the amount it jumps every time the seconds tick, but i would focus more on the Sleep and less on the Distance otherwise it wont be so smooth when it adjusts
Last edited by Syruz; 05-09-2017 at 11:48 PM.
while testing the 4x scope, when every I tap more then 3 times the scope move to left or right. How can I keep it to the center? I am not understanding how "MoveMouseRelative(0, 2)" this really work.
Find out which direction its going then u can make 0,2 into 1,2 or -1,2 Depending on the direction
Basically what it means is:
--Sleep(35) // Makes it wait 35 Miliseconds
Sleep(8) // Makes it wait 8 Miliseconds
MoveMouseRelative(0, 2) // Makes the mouse move 2 pixels down (although I would think -2 would be down and 2 would be up)
In MoveMouseRelative(X, Y) the first number would be ur left or right and the second number would be up and down.
Last edited by Syruz; 05-10-2017 at 12:07 AM.
linksys12 (04-02-2018)
Should not use scripts as Battleeye will ban you, and especially public ones. Just drag down lol, its ez.
In this case no, the macro is at driver side (inside the logitech software), it's not at autoit script, it cannot be found by BE.
On the other side, it makes the "manually" shots too exact timed, so you could be caught (but not because of the macro).
In BF (especially BF3) this type of macro were widely used and they started to trace it (with the method above), but I doubt they'll do anything similar here.
Nope, BE does not ban this type of scripts.
- - - Updated - - -
I am trying to make it when Press mouse button 4 it will activate "MoveMouseRelative(0, 2)" and press mouse button 5 will activate "MoveMouseRelative(0, 6) MoveMouseRelative(-2, 4)"Code:function OnEvent(event, arg) OutputLogMessage("event = %s, arg = %d\n", event, arg) if (event == "PROFILE_ACTIVATED") then EnablePrimaryMouseButtonEvents(true) elseif event == "PROFILE_DEACTIVATED" then ReleaseMouseButton(2) -- to prevent it from being stuck on end if (event == "MOUSE_BUTTON_PRESSED" and arg == 4) then recoil = not recoil spot = not spot end if (event == "MOUSE_BUTTON_PRESSED" and arg == 1 and recoil) then if recoil then repeat --Sleep(35) Sleep(8) MoveMouseRelative(0, 2) until not IsMouseButtonPressed(1) end end if (event == "MOUSE_BUTTON_PRESSED" and arg == 5) then recoil = not recoil spot = not spot end if (event == "MOUSE_BUTTON_PRESSED" and arg == 1 and recoil) then if recoil then repeat --Sleep(35) Sleep(8) MoveMouseRelative(0, 6) Sleep(8) MoveMouseRelative(-2, 4) until not IsMouseButtonPressed(1) end end end
But in when I press 4 or 5 it still doing "(0, 2)".
I tried it out and it works perfectly! Didn't even know that something like this is possible with my G502
Therefore, lets hope this will stay safe but i think so
And razer mouse? Someone have?
Scripts are scripts, whether they are run through drivers or though programs or injected into the game, if they give an advantage to the player over other players they are bannable, and if BE can scan your computer and all running processes (you agreed to it when installing the game), they can easily scan for something like this running, just look at overwatch, all those people got banned for using that Autohotkey aimbot script, but using autohotkey in general didnt get you banned, thats because it was the script, not the program, same as this, its just running through logitech program instead of autohotkey.
You could be banned for using an external scripting engine (as I specified in my previous post), such as AHK.
The embed software used by Logitech is at driver level, it is a macro, and it is transparent: the command are like being sent by the mouse itself (imagine a hardware macro), that's why it cannot be detected by BE or any other anti-cheat software, neither by scanning your PC (there's no executable or compiled script): there's no additional software running apart the official driver, that could be scanned or intercepted.
When Logitech released the G-Series, on most fps forums, many users start to moaning about it and about the impossibility to block or trace it: you should block the whole Logitech Gaming Software, and it wouldn't be possibile for obvious reasons.
But... as I mentioned in the previous post, you can trace a macro user with other methods (like it was done in BF3)... I doubt they would lose their time doing a such check, it would be simpler to make the recoil completely unpredictable (that is the solution used by most fps to nullify the macro-recoil cheaters) to resolve or mitigate the issue.