Destiny dDeadPark Aimbot Forsaken - Only 1080p

[kaldingo87]

Need some feedback for this script guys! I'm still using fatdoobie's gui-less version and I'm not banned, but let me know if this script got better performance

been using it for a few days, no problems with ban. only issue is sometimes it goes crazy shakes like hell from wall to head to other wall depending on the map.

[saulob]

Is there any way to play it with 720p?

I'm unable to choose 1080p

[ricardmark1]

been using it for a few days, no problems with ban. only issue is sometimes it goes crazy shakes like hell from wall to head to other wall depending on the map.

That is because it is an earlier build not optimized.
It was like one of first drafts from fatdoobie and andrew.
How da hell this passed under Bungie radar?
It's even bad comparing to the one we got on the last fatdoobie versions.

Can't understand how is not detected. No protection against mouse events (which are being detected right now) and ahk are bannable in the moment.
My bet is simple > every people using this will be caught on the next ban wave.

[kaldingo87]

That is because it is an earlier build not optimized.
It was like one of first drafts from fatdoobie and andrew.
How da hell this passed under Bungie radar?
It's even bad comparing to the one we got on the last fatdoobie versions.

Can't understand how is not detected. No protection against mouse events (which are being detected right now) and ahk are bannable in the moment.
My bet is simple > every people using this will be caught on the next ban wave.

which version are you using?

edit: i was using it on my smurf/free account. ill keep you guys posted if it gets smacked with a ban

[TearL2]

Hey again, thanks for the answers.

I'm using fatdoobie's script now. It's undetected if you know what to modify. Performance is quite ok!

[johnny mac]

will this work if i open d2 on a limited user account but this aimbot with admin privileges?

that should prevent d2 from reading processes and snooping around too much right?

an extra layer of safety

[ricardmark1]

Hey again, thanks for the answers.

I'm using fatdoobie's script now. It's undetected if you know what to modify. Performance is quite ok!

You know that you are the 2nd person to say that right?
It's not undetected...
It's detected... me and others with the owner already confirmed that. Please don't send falase information for the people.
People using dPark or even Fatdoobie version are tagged for the next ban wave > should be when annual big update appears.
@TearL2, it's not undetected if you know what to modify > that is false... even the owner of the ahk (fatdoobie) and people with plenty of knowledge were banned. I fully understand that the ahk versions here work... why not? nothing has changed besides the fact that is DETECTED by Bungie.
It's up to you everyone.

The owner got a Cease&Desist from Bungie themselves... do you still think it's undetected?

- - - Updated - - -

will this work if i open d2 on a limited user account but this aimbot with admin privileges?

that should prevent d2 from reading processes and snooping around too much right?

an extra layer of safety

No. Lol.
This is not what will ever give any safety.

[TearL2]

@ricardmark1

I said if you know what you're doing you can make this undetected..

[ricardmark1]

@ricardmark1

I said if you know what you're doing you can make this undetected..

So. Even the owner (that had the most customized version) and other people here (that also changed/switched everything) got banned. but you have a highly undetected version that Bungie let it pass even if right now Bungie has mouse event detection > that unless you have a new hack not in ahk you can't avoid it.

So that is what you are trying to telling us?
Feel free to message fatdoobie, me or even andrew about this so called customized version because either you do it in anything like C++ or you are on the future ban list... Ban days are every friday and also when update drops...

You need to tell more than "if you know what you're doing" to go ahead with such a bold statement.
I belive that you are not banned > this is OK.
I don't believe it's undetected > for sure you are on the future ban list.

Let me be clear on what is detected even after customization:

1) adding small pieces of code to avoid detection
2) ash change doesn't work
3) mouse event injection is detected
4) using the GUI of the hack (even changed) is equal to a ban
5) running the script directly without GUI = BAN
6) having a code to generate new instances and delete after use = ban

So please enlighten us

[TearL2]

Seriously, how can you say mouse_events are detected? Use another program that moves your Mouse and check if you're banned...

[ricardmark1]

Yes, they are.
Only Xaim and Rose had mouse_event injection protection and they stay safe.
fatdoobie himself said he didnt had that protection.
Go use any mouse program to test it.
You will see...

I will repeat > the creator of the hack that you use said mouse_events were not protected and Bungie detects those now.
AHK that started with Perung and KKONA back in the day all of them didnt had any protection for that.

At that moment, it didnt matter because Bungie has not detecting that.
Now they are and that is the reason they got andrew and fatdoobie releases.

Go ask him. He can tell you exactly that .

So again... either you literally escaped with your life as lucky motherfucker or you are just on the next ban wave as everybody currently using ahk.

I would go even further... not even Xaim or Rose would be safe now and they were the top dogs back in the day.

That is also the reason most people will simply not try again... it's not worth it. Either memory or nothing.

[SenpaiTOP]

Yes, they are.
Only Xaim and Rose had mouse_event injection protection and they stay safe.
fatdoobie himself said he didnt had that protection.
Go use any mouse program to test it.
You will see...

I will repeat > the creator of the hack that you use said mouse_events were not protected and Bungie detects those now.
AHK that started with Perung and KKONA back in the day all of them didnt had any protection for that.

At that moment, it didnt matter because Bungie has not detecting that.
Now they are and that is the reason they got andrew and fatdoobie releases.

Go ask him. He can tell you exactly that .

So again... either you literally escaped with your life as lucky motherfucker or you are just on the next ban wave as everybody currently using ahk.

I would go even further... not even Xaim or Rose would be safe now and they were the top dogs back in the day.

That is also the reason most people will simply not try again... it's not worth it. Either memory or nothing.

Perfect explanation on that.

[ricardmark1]

Thanks.
But still there is the mistery your version is still up and running dPark.
Doesn't make any sense.

[tinkomek]

Thanks.
But still there is the mistery your version is still up and running dPark.
Doesn't make any sense.

My previous account was banned at the last banhammer about 3-4 weeks ago. (Lost a year 1 account )Made a new account and intermittently been using the deadpark version. I decompiled the script, changed a few things like keys and image names. Nothing too advanced. I only run the script, never compile it. Compiling it creates an .exe fie.

It still goes crazy on any maps with red or orange in it. I can't use it on every pvp map.

I could never get Andrew's version to work. It just never locked on. If I turned sensitivity up high to like to 10+, it would kind of lock on.

My current deadpark settings for 2k resolution (2256x1440) is

sen=5
FovX=3.6
FovY=3.6
AimX=100
AimY=47

Mouse settings
Look sensitivity = .7
ADS = 1

I'm only doing this because it's still blantantly apparent players are using some sort of aimbot in pvp.
I'm not sure if I got banned for creating an AFK bot (which I only used in Rumble) or the Forsaken Aimbot.

[ricardmark1]

My previous account was banned at the last banhammer about 3-4 weeks ago. (Lost a year 1 account )Made a new account and intermittently been using the deadpark version. I decompiled the script, changed a few things like keys and image names. Nothing too advanced. I only run the script, never compile it. Compiling it creates an .exe fie.

It still goes crazy on any maps with red or orange in it. I can't use it on every pvp map.

I could never get Andrew's version to work. It just never locked on. If I turned sensitivity up high to like to 10+, it would kind of lock on.

My current deadpark settings for 2k resolution (2256x1440) is

sen=5
FovX=3.6
FovY=3.6
AimX=100
AimY=47

Mouse settings
Look sensitivity = .7
ADS = 1

I'm only doing this because it's still blantantly apparent players are using some sort of aimbot in pvp.
I'm not sure if I got banned for creating an AFK bot (which I only used in Rumble) or the Forsaken Aimbot.

You are banned because all these ahk are bannable right now.
You are clearly on a watchlist believe me because you keep using this.
The small modifications you are doing doesn't help at all since even fatdoobie/andrew (which was completely customized versions) were detected and banned.
Ofc if you would create an exe that would be even a bigger problem.

People here are trying to give advice saying that this is more than detected.
But for some reason people keep trying...

About what u see in pvp, well, one is people using the ahk bots and they will be banned as everybody was here.
The other part are the private cheats memory ones that goes up to 1k$ or even more.