OutdatedDestiny 2 External Bot Final + Source

Posts 316–330 of 635 · Page 22 of 43

Originally Posted by yashspartan1

So I did exactly that, compiled it (deleted the old .exe), but when I try to run it, it says this: https://gyazo.com/2eba487f3c4669febc95dfcb68b6e05d

Here's what I have in MouseMoves2 after edit:

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)), *65 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)), *45 healthbar2.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)), *35 healthbar3.bmp
if(AimPixelX != "" && AimPixelY != "")
{
GoSub GetAimOffset1
GoSub GetAimMoves1
}
}
Return

same here please help

Originally Posted by flores2323

same here please help

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)), *35 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)), *35 healthbar2.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)), *35 healthbar3.bmp
if(AimPixelX != "" && AimPixelY != "")
{
GoSub GetAimOffset1
GoSub GetAimMoves1
}
Return

try this

Still error

Originally Posted by flores2323

Still error

take a screenshot send it me

Originally Posted by flores2323

Still error

Try this. Adjust the *N name.bmp files as needed

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)), *65 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)), *45 healthbar2.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)), *35 healthbar3.bmp
if(AimPixelX != "" && AimPixelY != "")
{
GoSub GetAimOffset1
GoSub GetAimMoves1
}
}
}
Return

Error: Missing "}"

Line#
--> 079: }

The program will exit

- - - Updated - - -

Originally Posted by 3andrew

Now i got it!!! THANK YOU!

Your welcome. Im in the process of testing some of the proposed suggestions ATM. Thank you all so much fore the input!!!!!

Originally Posted by 3andrew

Your welcome. Im in the process of testing some of the proposed suggestions ATM. Thank you all so much fore the input!!!!!

Btw, is this something you can answer? Thanks!

Can I use my previous my settings I had on the old AHK Aimbot on your new one? Or Should I only be using whats in your ******* files??

I'm also 1440p. My brightness is on 4 and my in-game sense is 3 and mouse dpi 1600

Here are my old settings.ini on the previous AHK Aimbot

[settings]
sen=3.3
FovX=4.3
FovY=3.5
AimX=85
AimY=49

Originally Posted by viking805fan

Certainly. The only one I question is the brightness due to the way we now have to use variance but you can try. If you dont know, I'll briefly explain what those settings do.

Sensitive - how fast the bot tries to correct. Too high and it gets wobbly, too slow and it lags far behind. The sensitivity number in the settings.ini you use must be adjusted if you change the in game sensitivity.

FOV - Is essentially the box size of the scan area. The smaller the better here but too small and someone can move outside the box and cause it to loose lock.

Aim x and y - this is the offset of aim from the target lock. Since we are locking to a health bar, we need to adjust to aim center mass on the head. I wouldn't mess with the x axis but you can adjust the y. I prefer aiming mid neck to account for recoil so I prefer a larger deviation from the aim point. This means the y number must be larger. I believe I use around 60 for that.

Originally Posted by 3andrew

Ah i see, thanks for explaining it to me. So the higher the Y-axis the lower the vertical aim will be on the enemies body? For sens you use 3.4 right? would my 3.3 really be that crazy of a difference? Also, do you recommend i change my brightness settings?

a little tip...Vibrance makes magic

Originally Posted by Forsaga

a little tip...Vibrance makes magic

Can you share a little insight? I've yet to play around with this. Is this a setting in the nvidia control panel? Does it have any effect on the bot?

- - - Updated - - -

Originally Posted by viking805fan

Yes about the y axis. That's why I prefer the higher number so my aim point lands around the top of the neck. Helps with pulse rifles especially (2 burst kills!). 3.3 and 3.4 will be hardly noticable. If your not wobbling along the x axis, I'd just leave it as is. Changing the brightness could effect the bots snapping because there is a change on overall color. You would have to do a little testing there.

Originally Posted by 3andrew

Can you share a little insight? I've yet to play around with this. Is this a setting in the nvidia control panel? Does it have any effect on the bot?

- - - Updated - - -

Yes about the y axis. That's why I prefer the higher number so my aim point lands around the top of the neck. Helps with pulse rifles especially (2 burst kills!). 3.3 and 3.4 will be hardly noticable. If your not wobbling along the x axis, I'd just leave it as is. Changing the brightness could effect the bots snapping because there is a change on overall color. You would have to do a little testing there.

thanks for all the tips. I went and changed the sens back to 3.4 just because. lol. I will stay at the current brightness and see how it affects the aimbot. I also made small change to the Y-axis, going with 55 for now and will test. 55 seems like a good number between yours and my old one.

i ve tested a lot of new hp bars yesterday till i rich like 5.0k\d per game.
1) Vibrance makes magic. Im using on 90% (its a bit hard for eyes since game become so fu**** bright , but for *imagesearch* seems to be good)
2) Hp bars...i made like 2 screenshots of guys in pvp with FULL hp on dark and white background.
3) Splitted this hp bars for like

DARK - 1st image - almost full hp (about 80% of full length of hp bar) this have *40 rgb vars
2nd image - about 40% hp (about 35-40% of full length of hp bar) this have *30 rgb vars
3rd image - about 10% hp ( about 20pixel length) this have *20rgb vars

and same shit for WHITE background hp bars with same rgb vars.

-----------
in code its smth like this

MainSub:
if (trackRedMode = 1) {
imageSearch, AimPixelX, AimPixelY, %sx1%, %sy1%, %sx2%, %sy2%, *40 dark1.bmp
if(AimPixelX != "" && AimPixelY != "") {
GoSub FindOffsetToTarget
GoSub DoMousemove
return
}
imageSearch, AimPixelX, AimPixelY, %sx1%, %sy1%, %sx2%, %sy2%, *30 dark2.bmp
if(AimPixelX != "" && AimPixelY != "") {
GoSub FindOffsetToTarget
GoSub DoMousemove
return
}
imageSearch, AimPixelX, AimPixelY, %sx1%, %sy1%, %sx2%, %sy2%, *20 dark3.bmp
if(AimPixelX != "" && AimPixelY != "") {
GoSub FindOffsetToTarget
GoSub DoMousemove
return
}
imageSearch, AimPixelX, AimPixelY, %sx1%, %sy1%, %sx2%, %sy2%, *40 light1.bmp
if(AimPixelX != "" && AimPixelY != "") {
GoSub FindOffsetToTarget
GoSub DoMousemove
return
}
imageSearch, AimPixelX, AimPixelY, %sx1%, %sy1%, %sx2%, %sy2%, *30 light2.bmp
if(AimPixelX != "" && AimPixelY != "") {
GoSub FindOffsetToTarget
GoSub DoMousemove
return
}
imageSearch, AimPixelX, AimPixelY, %sx1%, %sy1%, %sx2%, %sy2%, *20 light3.bmp
if(AimPixelX != "" && AimPixelY != "") {
GoSub FindOffsetToTarget
GoSub DoMousemove
return
}
}
return
if (automaticGunMode = 1 && AimPixelX = "" && AimPixelY = "") {
Gosub, doRelease
}
return

PS !!!!automaticGunMode and if (trackRedMode = 1) must be deleted if u dont using full source from topic starter!!!(external 3.6 version)

You wouldnt happen to have health bar pictures for 90% digital brightness?

Posts 316–330 of 635 · Page 22 of 43

1112122233343

This thread is closed for replies.

Tags for this Thread

None

OutdatedDestiny 2 External Bot Final + Source

Similar Threads

Tags for this Thread