OutdatedDestiny 2 External Bot Final + Source

Posts 526–540 of 635 · Page 36 of 43
So I'm new to destiny 2 cheating, but could someone point me to a resource to what .ahk files are? Are there no separate .exe applications to run?

Thanks in advance
Quote Originally Posted by kaalaron View Post
So I'm new to destiny 2 cheating, but could someone point me to a resource to what .ahk files are? Are there no separate .exe applications to run?

Thanks in advance
I was the same as you about 2 weeks ago. Just Google search what it is and what they do like I did. Not trying to be a dick, unless you are asking for direct code translation or meanings.
The ahk file is part of a program called Auto Hot Key. You have to first install that app.
Create a blank notepad file and copy the code into it, then save. Rename the file from .txt to .ahk.
Now right click the .ahk file and press compile. This will make it an exe file you can run.

Quote Originally Posted by kaalaron View Post
So I'm new to destiny 2 cheating, but could someone point me to a resource to what .ahk files are? Are there no separate .exe applications to run?

Thanks in advance
- - - Updated - - -

So the precision for actually hitting someone in the head is amazing. It's better than before for me.
Right now mine is very jumpy though so it's kinda hard to play like that and makes it quite obvious.
I'm gonna mess around with different settings today and see if I can smooth it out. Thank you though.

Quote Originally Posted by fatdoobie View Post
Code:
#NoEnv
#Persistent
#SingleInstance, Force
#KeyHistory, 0
#InstallKeybdHook
#UseHook
#HotKeyInterval 1 
#MaxHotkeysPerInterval 127
SetBatchLines,-1
SetKeyDelay,-1, 8
SetControlDelay, -1
SetMouseDelay, 0
SetWinDelay,-1
ListLines, Off
SendMode, Input
CoordMode, Mouse, client

Numpad1::
Keywait, Numpad1, U
fileread,settings,settings.ini
stringsplit,settings,settings,`n
iniread,rx,settings.ini,settings,sen
iniread,xrange,settings.ini,settings,FovX
iniread,yrange,settings.ini,settings,FovY
iniread,xa,settings.ini,settings,AimX
iniread,xy,settings.ini,settings,AimY
iniread,tolerancered,settings.ini,settings,tolRed
iniread,tolerancewhite,settings.ini,settings,tolWhite
DirX := 0
DirY := 0
ZeroX := A_Screenwidth/2
ZeroY := A_Screenheight/2
X1 := 0 + (A_Screenwidth * (xrange / 10))
Y1 := 0 + (A_Screenheight * (yrange / 10))
X2 := A_Screenwidth - (A_Screenwidth * (xrange / 10))
Y2 := A_Screenheight - (A_Screenheight * (yrange / 10))
foundSmall := false
foundMedium := false
tolRed2 := tolerancered - 10
tolRed3 := tolerancered - 20
Soundbeep, 750, 500
loop, {
	if (GetKeyState("RButton", "P") || GetKeyState("LButton", "P")) {
		GoSub MouseMoves2
		continue
	}
	if GetKeyState("Numpad1", "P") {
		Keywait, Numpad1, U
		break
	}
	Sleep, 1
}
Soundbeep, 500, 250
return

MouseMoves2:
if (!foundMedium && !foundSmall) {
	imagesearch, AimPixelX, AimPixelY, %X1%, %Y1%, %X2%, %Y2%, *%tolerancered% healthbar.bmp ; big red bar
	if (AimPixelX != "" && AimPixelY != "") {
		GoSub, getnewoffsets
		imagesearch, newX, newY, %newX1%, %newY1%, %newX2%, %newY2%, *%tolerancewhite% secondimage.bmp ; secondary reference point
		if (newX != "" && newY != "") {
			gosub, GetAimOffset1
			gosub, GetAimMoves1
			return
		}
	}
}
if (!foundSmall) {
	imagesearch, AimPixelX, AimPixelY, %X1%, %Y1%, %X2%, %Y2%, *%tolRed2% healthbar2.bmp ; medium red bar
	if (AimPixelX != "" && AimPixelY != "") {
		GoSub, getnewoffsets
		imagesearch, newX, newY, %newX1%, %newY1%, %newX2%, %newY2%, *%tolerancewhite% secondimage.bmp ; secondary reference point
		if (newX != "" && newY != "") {
			foundMedium := true
			gosub, GetAimOffset1
			gosub, GetAimMoves1
			return
		}
	}
}
foundMedium := false
imagesearch, AimPixelX, AimPixelY, %X1%, %Y1%, %X2%, %Y2%, *%tolRed3% healthbar3.bmp ; small red bar
if (AimPixelX != "" && AimPixelY != "") {
	GoSub, getnewoffsets
	imagesearch, newX, newY, %newX1%, %newY1%, %newX2%, %newY2%, *%tolerancewhite% secondimage.bmp ; secondary reference point
	if (newX != "" && newY != "") {
		foundSmall := true
		gosub, GetAimOffset1
		gosub, GetAimMoves1
		return
	}
}
foundSmall := false
return

GetAimOffset1:
AimX := AimPixelX - ZeroX +xa
AimY := AimPixelY - ZeroY +xy
if (AimX > 10) {
	DirX := rx / 10
} else if (AimX > 0) {
	DirX := rx / 15
}
if (AimX < -10) {
	DirX := (-rx) / 10
} else if (AimX < 0) {
	DirX := (-rx) / 15
}
if (AimY > 0) {
	DirY := rx /13
} else if (AimY < 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

getnewoffsets:
newX1 := AimPixelX - 50
newX2 := AimPixelX - 10
newY1 := AimPixelY - 30
newY2 := AimPixelY + 10
return
2. Open notepad and save the following text as settings.ini

Code:
[settings]
sen=9
FovX=3.7
FovY=3.6
AimX=67
AimY=40
tolRed=60
tolWhite=15
Quote Originally Posted by slayerh4x View Post
The ahk file is part of a program called Auto Hot Key. You have to first install that app.
Create a blank notepad file and copy the code into it, then save. Rename the file from .txt to .ahk.
Now right click the .ahk file and press compile. This will make it an exe file you can run.



- - - Updated - - -

So the precision for actually hitting someone in the head is amazing. It's better than before for me.
Right now mine is very jumpy though so it's kinda hard to play like that and makes it quite obvious.
I'm gonna mess around with different settings today and see if I can smooth it out. Thank you though.

Thanks so much for the brief explanation, I really appreciate it. Do I need to put the file anywhere specifically? Is it as simple as copy, paste, save, and run? Or do I need to do anything else?

Which are the most important settings that I should be tweaking? Is it just in the settings.ini?
Quote Originally Posted by OldTimeGmer View Post
works quite well down to the last 10% health best out there just now by far, nice work
you can send upload file your folder.thank you
Quote Originally Posted by hellking297 View Post
Didnt work as intented in 1440p it snapped a lot to different spots
Try increasing the size of secondimage.bmp and reducing the white tolerance.

If it's snapping to something which is NOT a red health bar, it's finding false positives for the secondimage which it should never do.

If it's just not snapping reliably to red bars, either your red tolerance is too high or too low, or your images are wrong.

Quote Originally Posted by Taylor Swift View Post
I don't even know where to try to start with this thing tbh. Am I supposed to hit numpad 1, and then hold right click, or what? Because when I do that it does nothing..
Yes, press Numpad1 to turn it on (high pitch beep), then holding left or right click will activate the script.

I'm not going to run short courses on how to understand autohotkey code, if you cant figure this out even with that wall of text I made for you guys, then idk what to tell you. It works great for me and I've made sure it works for other people as well.

edit: Someone with 1440p monitor, if you want you can screenshot an enemy in pvp and post that for me. Preferably as far away from you as possible so their hud is at minimum size. I can then make a proper set of images for those on 1440p.

Same goes if you have a smaller resolution than 1080p, take a pic of an enemy's hud in pvp and post it for me.


Quote Originally Posted by alolod View Post
this Pictures come in the same Folder with the whatever.ahk but how can i start the script or find the script this Pictures on my desktop too?
I'm not really sure what you're asking, but just put all of the files into the same folder together. The script is going to look inside whatever folder you put it in.

edit: if you mean you want to put all the files on your desktop, that's fine. The desktop counts as a folder to windows.
Quote Originally Posted by fatdoobie View Post
I'm not going to run short courses on how to understand autohotkey code, if you cant figure this out even with that wall of text I made for you guys, then idk what to tell you. It works great for me and I've made sure it works for other people as well.
C'mon man lets rent out a classroom.
Quote Originally Posted by slayerh4x View Post
C'mon man lets rent out a classroom.


And remember guys, I'm not saying my script is perfect, it just shouldn't try to aim at walls and shit. Also I'm using static offsets for everyone on where to look for the level box, it's a pretty generous search zone (40x40px), but that might still even be too small for some resolutions, so I'll need some help to figure it out for you guys. Again, if someone with a 1440p or other resolution can take a pic of someone in pvp and share that for me, it'd be great.
Quote Originally Posted by fatdoobie View Post


And remember guys, I'm not saying my script is perfect, it just shouldn't try to aim at walls and shit. Also I'm using static offsets for everyone on where to look for the level box, it's a pretty generous search zone (40x40px), but that might still even be too small for some resolutions, so I'll need some help to figure it out for you guys. Again, if someone with a 1440p or other resolution can take a pic of someone in pvp and share that for me, it'd be great.
Hey there thanks so much! I just had a quick question since I'm relatively new to this, but how "safe" is it to use a .ahk file? Is there a reason why it uses one instead of a precompiled .exe file or something?
Quote Originally Posted by kaalaron View Post
Hey there thanks so much! I just had a quick question since I'm relatively new to this, but how "safe" is it to use a .ahk file? Is there a reason why it uses one instead of a precompiled .exe file or something?
Imo there's no real difference between using a compiled AHK exe and AHK itself. Both unpack into the memory exactly the same. The only difference running an exe is that Bungie would need slightly more sophisticated methods to detect you, but still really nothing special. As far as I can tell, they don't really consider AHK to be a problem and treat it on a basis of "if they get reported, we'll deal with it then". They DO however target paid sites with actual banwaves.

Quote Originally Posted by slayerh4x View Post
Fat add me on battle.net so I can talk to you. I keep getting DB error and can't load this site. I have 1440 video and images for you and we can do some testing in private match if you want. I have it working pretty well for me right now.
Yeah this site goes down a lot for some reason lol. If I were you I would edit that post though bro, Bungie definitely snoop around these threads, even if you don't use the scripts with that account I still wouldn't do that. If you want you can PM me and we can figure out a better way to chat though.

Quote Originally Posted by kaalaron View Post
Do I need to put the file anywhere specifically? Is it as simple as copy, paste, save, and run? Or do I need to do anything else?

Which are the most important settings that I should be tweaking? Is it just in the settings.ini?
As long as all of the files (script.ahk, settings.ini and the images) are all in the same folder, you're fine.

Your AimX and AimY values will determine where the script actually aims, and thats pretty important. If you find that the script is trying to aim but it seems to go to the wrong spots, this could be your problem. You can test the script in PvE by setting "tolWhite" to 255 in settings, so try that and go somewhere without a lot of red/orange/brown on the map. It's not going to be perfect at every distance, so just try to find a nice middle ground, or set it up with a specific gun in mind (eg pulse rifle long-mid range). Once you get these values good enough, set tolWhite back to 5-15 so that it only works against actual PvP enemies and not red terrain.

-- edit

Also guys, currently I'm working on a version which uses only relative sizes for every screen measurement, I think I've got it working but I'll just do a couple more tests. So assuming that Bungie also use the same relative sizes for resolution (can only assume so), it should work for anyone.
Quote Originally Posted by fatdoobie View Post
Also guys, currently I'm working on a version which uses only relative sizes for every screen measurement, I think I've got it working but I'll just do a couple more tests. So assuming that Bungie also use the same relative sizes for resolution (can only assume so), it should work for anyone.
Well i try it all day long, and its works for me. I only have problems with aim some time jump somewheare its not should to. I dont sure its couse i have too small pictures or what. Any way its works. And ussualy its way better then my own skill, its cappable for me to play every game with 3+ kda. The main problem for me, that i dont even know what resolution i have 1680x1050(is it 720?) i change my pictures to hb1 144x6, hb2 75x8, hb3 33x8, secondimage 4x1. Or i should take screnshots, i dont sure how i dont have people to take screens in private matches and even if i have with my "curved hands" i can easy fuck up with cut red bars from screens.
Quote Originally Posted by fatdoobie View Post
Again, if someone with a 1440p or other resolution can take a pic of someone in pvp and share that for me, it'd be great.
Fat add me on battle.net so I can talk to you. I keep getting DB error and can't load this site. I have 1440 video and images for you and we can do some testing in private match if you want. I have it working pretty well for me right now.
NotMe#1234
Quote Originally Posted by fatdoobie View Post
PM me
Looks like theres a built in chat system on here that I never knew about. I added you on there.
Quote Originally Posted by fatdoobie View Post
Originally Posted by slayerh4x
I sent you my "unmentionable chat service" if you have time to jump in there later.
Quote Originally Posted by slayerh4x View Post
I sent you my "unmentionable chat service" if you have time to jump in there later.
Do you think you could send a link to me too? I'd like to learn more about it.
Posts 526–540 of 635 · Page 36 of 43
This thread is closed for replies.

Similar Threads

Tags for this Thread

None

Talk with us