Re: Fortnite Battle Royale: Turbo Instant-Build AIO Script
Posted: Mon Aug 13, 2018 12:33 am
alanmcgregor wrote:PuckItYolo wrote:... is there a reason the aim assist/abuse options are set to ADS or ADS+Fire? And not Fire or ADS+Fire? I'd figure the second way would be more practical in shotgun or smg situations. Or does it interfere with the fast-build code?.
Is set to ADS because the ADS spams works better, it requires a bit of delay to truly lock in-to target and stay lock it while tracking objectives at distance. The ADS spam only while Firing was requested to make it more subtle.
Firing and going automatically ADS + Spaming is a poor choice, for this game. IMO this is not CoD, and specially with shotguns or close range engages, because first you hinder your field of view, second people in this game jumps and moves all the time at close combat, getting automatic ADS for a split of a second will make you stiff, and overall you should HIP fire at close range... that's 101 at any shooter.
Being able to win a 1 v 1 at close combat facing directly the enemy it always be a matter of luck. In reality you should never do that... or avoid it, your positioning should be always give you the advantage, like shooting from top, peek waiting the shoot in a corner, shooting from the back... that's how you win a close combat gunfight.
I wasn't talking about ADS Spamming, I was simply using ADS+Fire as an example for the activation button for Auto-Aim. Is there no way to program a false "Entity.GetAbsOrigin" into the API scripting reference to where once you press the fire button, the script will use Auto-Aim assist to lead/or not lead your shot depending on where you thumbstick or reticle is moving? The AbsOrigin would just basically pull the current location of your reticle or thumbstick position as a Vector once the Fire button is engaged and use whatever mathematical functions necessary to aim-assist based off that position. Typically this method is used in other games to pull the current location of an enemy or entire as a Vector, but since you are unable to directly pull an enemy targets location as data frm this game through Titan Two, I figured the Users targeting reticle could serve as a substitute for that since it could just be based off thumb stick positioning.
Idk if that even made sense to you, but I tried my best to get across what I was trying to say. Maybe you can't even pull a reticle location to manipulate with the Titan Two, if so, then I'll just treat this tool as a slightly more advanced AutoHotkey program with a hint of C based scripting added when I begin making my own scripts. I'm just used to being able to do a lot more when scripting is all.