OutdatedDestiny 2 External Bot Final + Source
transparency and "shiny" like slide
After a good night^W half a day sleep and a cup of coffee I did what every sane person should - I read the fucking manual about ImageSearch. It seems it allows for the variance of the image.
So I modified the imagesearch like this:
and took new color samples.
The aim started to follow the hp bars sometimes but it seems unreliable and doesn't aim exactly at enemy. Also it sometimes snaps to random colors on screen.
*n (variation): Specify for n a number between 0 and 255 (inclusive) to indicate the allowed number of shades of variation in either direction for the intensity of the red, green, and blue components of each pixel's color. For example, *2 would allow two shades of variation. This parameter is helpful if the coloring of the image varies slightly or if ImageFile uses a format such as GIF or JPG that does not accurately represent an image on the screen. If you specify 255 shades of variation, all colors will match. The default is 0 shades.
Code:
imageSearch, AimPixelX, AimPixelY, 0 + (A_Screenwidth * (xrange/10)), 0 + (A_Screenheight * (yrange/10)), A_Screenwidth - (A_Screenwidth * (xrange/10)), A_Screenheight - (A_Screenheight * (yrange / 10)), *4 healthbar.bmp
The aim started to follow the hp bars sometimes but it seems unreliable and doesn't aim exactly at enemy. Also it sometimes snaps to random colors on screen.
Can one edit the, normal AHK aimbot? Nobody needs the trigger. I do that via the mouse settings. I'm already saying thank you...
Dam. If there was a way to read the files saved onto our PCs and directly find the code for the color of the hp bars, it would've been so much easier.
thats the code ! Im not sure how to change the color but if you know what to do give it a try
- - - Updated - - -
the code I posted above is without triggerbot btw
Code:
; <COMPILER: v1.1.24.01>
#SingleInstance, Force
#Persistent
#NoEnv
#Warn
SendMode, Input
SetWorkingDir, %A_ScriptDir%
DirX := 0
DirY := 0
F1::
#Persistent
#KeyHistory, 0
#NoEnv
#HotKeyInterval 1
#MaxHotkeysPerInterval 127
#InstallKeybdHook
#UseHook
#SingleInstance, Force
SetKeyDelay,-1, 8
SetControlDelay, -1
SetMouseDelay, 0
SetWinDelay,-1
SendMode, InputThenPlay
SetBatchLines,-1
ListLines, Off
CoordMode, Mouse, client
PID := DllCall("GetCurrentProcessId")
Process, Priority, %PID%, Normal
ZeroX := A_Screenwidth/2
ZeroY := A_Screenheight/2
CFovX := 80
CFovY := 200
ScanL := 660
ScanR := 1250
ScanT := 280
ScanB := 610
inicount := 9
fileread,settings,settings.ini
stringsplit,settings,settings,`n
if !(fileexist("settings.ini")) || (settings0-3 != inicount)
{
iniread,rx,settings.ini,settings,sen, 6
iniread,xrange,settings.ini,settings,FovX, 4.3
iniread,yrange,settings.ini,settings,FovY, 3.5
iniread,xa,settings.ini,settings,AimX, 85
iniread,xy,settings.ini,settings,AimY, 49
}
Soundbeep, 750, 500
Loop,
{
GetKeyState, Mouse2, LButton, P
GetKeyState, Mouse3, RButton, P
if ( Mouse2 == "D" ) || ( Mouse3 == "D" )
{
GoSub MouseMoves2
}
GetKeyState, Key1, Numpad1, P
if ( Key1 == "D")
{
Soundbeep
break
}
}
MouseMoves2:
imageSearch, AimPixelX, AimPixelY, 0 + (A_Screenwidth * (xrange/10)), 0 + (A_Screenheight * (yrange/10)), A_Screenwidth - (A_Screenwidth * (xrange/10)), A_Screenheight - (A_Screenheight * (yrange / 10)), healthbar.bmp
if(AimPixelX != "" && AimPixelY != "")
{
GoSub GetAimOffset1
GoSub GetAimMoves1
}
else
{
imageSearch, AimPixelX, AimPixelY, 0 + (A_Screenwidth * (xrange/10)), 0 + (A_Screenheight * (yrange/10)), A_Screenwidth - (A_Screenwidth * (xrange/10)), A_Screenheight - (A_Screenheight * (yrange / 10)), *4 orangehealthbar.bmp
if(AimPixelX != "" && AimPixelY != "")
{
GoSub GetAimOffset1
GoSub GetAimMoves1
}
}
Return
GetAimOffset1:
Gui,Submit, Nohide
AimX := AimPixelX - ZeroX +xa
AimY := AimPixelY - ZeroY +xy
if ( AimX+10 > 0)
{
DirX := rx / 10
}
else if ( AimX+5 > 0)
{
DirX := rx / 15
}
if ( AimX+10 < 0)
{
DirX := (-rx) / 10
}
else if ( AimX+5 < 0)
{
DirX := (-rx) / 15
}
if ( AimY+.25 > 0 )
{
DirY := rx /13
}
if ( AimY+.25 < 0 )
{
DirY := (-rx) /13
}
AimOffsetX := AimX * DirX
AimOffsetY := AimY * DirY
Return
GetAimMoves1:
RootX := Ceil(( AimOffsetX ** ( 1 )))
RootY := Ceil(( AimOffsetY ** ( 1 )))
MoveX := RootX * DirX
MoveY := RootY * DirY
DllCall("mouse_event", uint, 1, int, MoveX, int, MoveY, uint, 0, int, 0)
return
the code I posted above is without triggerbot btw
I tried making 'pixels' out of screenshots but it is unreliable and works only if the target on the same background. I dunno how to make pixel ranges in ahk.
Is there a setting in-game to change the transparency? I'm at work, so I can't get in-game to check.
It does not work anymore. The life ad has changed. An AHK aimbot sounds nice! Update please.
It looks like PixelSearch allows for variation. https://autohotkey.com/docs/commands/PixelSearch.htm
Would PixelSearch be useful for the code? It has a variation capability for the specified color. Only question is would it slow things down? Wouldn't the program would be checking for every variation of that color to a certain parameter set?
This thread is closed for replies.
Similar Threads
Destiny 2 HacksDestiny 2 External Bot v3.4 (GUI, PvE Mode, New Triggerbot + More)KI 144 Destiny 2 Hacks[v3.5] Destiny 2 External Bot (GUI, PvE Mode, Triggerbot +more)KI 2 CrossFire Hacks & CheatsUndetected Cheat Engine Final: SourceTH 2 WarRock - International HacksUndetected Cheat Engine Final: SourceTH 3 CounterStrike (CS) 1.6 Hacks / Counter Strike: Source (CSS) HacksUndetected Cheat Engine Final: SourceTH 2
