FAT Aim Assist 2.0

[ricardmark1]

Ay ay captain

[BioZo]

Sadly, I was only able to configure so that everything worked, and this morning I flew ban. No one knows for what time the game is blocked, if this is my first warning.

[ricardmark1]

Sadly, I was only able to configure so that everything worked, and this morning I flew ban. No one knows for what time the game is blocked, if this is my first warning.

What fatdoobie version did u use?

[BioZo]

What fatdoobie version did u use?

2.2 the fact that I did not have time to change the exe file. And as I understood I got banned forever.

[fatdoobie]

2.2 the fact that I did not have time to change the exe file. And as I understood I got banned forever.

You never opened any other version while destiny was running? Didnt you ask for help with 1.0

I doubt the bans were due to 2.2 tbh, the banwave was the same day as the release. Almost definitely 1.0 was the file they flagged, maybe 1.2 and 2.0 as well. If anyone *only* ran 2.2 and got banned, let me know.

Still would never open any of those exes again in any case.

[BioZo]

You never opened any other version while destiny was running? Didnt you ask for help with 1.0

I doubt the bans were due to 2.2 tbh, the banwave was the same day as the release. Almost definitely 1.0 was the file they flagged, maybe 1.2 and 2.0 as well. If anyone *only* ran 2.2 and got banned, let me know.

Still would never open any of those exes again in any case.

Usually I opened aim assist only when the character is fully loaded on the planet or in orbit. Honestly I will not put my mind on what version I was caught, the trouble is that bungie did not send letters with dates of violations or with any explanations at all.

[fatdoobie]

Usually I opened aim assist only when the character is fully loaded on the planet or in orbit. Honestly I will not put my mind on what version I was caught, the trouble is that bungie did not send letters with dates of violations or with any explanations at all.

Thats standard, usually a company flags a public exe and collects names on anyone who runs it for a week or two, then bans them. They purposely give as little info as possible to confuse us.

The reason I suspect it was 1.0 was that Bungie were made very aware of it by reddit / youtube. When they flagged that file, they (probably unknowingly) flagged everyone on mpgh as well. Or they are watching this thread, both are possible.

- - - Updated - - -

Earlier today everything was working as intended. Cannot get it to lock on now?

Working fine for me

[Masbka]

When I decided to costamize a little code
Bungie may have tracked the process and similar processes from other players (and then rather in name), as a result they banned from whom matches were found. Bans are issued by hand. The system of protection of the game does not recognize the script as harmful, there is no automatic ban, but there are 3 options for player complaints.
That's what I think about the situation

As always with respect, BUNGIE F U

[ricardmark1]

@fatdoobie, i understand why 2.3 is not working.

A lot of people were screen locked.
If i play on FULLSCREEN, everything is fine.
On windowed or borderless, when doing a Screenshot with lightshot i get a black picture.

So what to do now?
I know the script runs on fullscreen but is that efficient?

Thanks in advance.

- - - Updated - - -

You are screenlocked.

[fatdoobie]

When I decided to costamize a little code
Bungie may have tracked the process and similar processes from other players (and then rather in name), as a result they banned from whom matches were found. Bans are issued by hand. The system of protection of the game does not recognize the script as harmful, there is no automatic ban, but there are 3 options for player complaints.
That's what I think about the situation

Agreed. Same as every other game, completely external pixel scripts cannot be detected, only the process name or checksum can be added to a manual list.

Kivrin0’s 3.6 loader actually has a “fix” for that, but then there is the problem of them just flagging the loader...

- - - Updated - - -

@fatdoobie, i understand why 2.3 is not working.

A lot of people were screen locked.
If i play on FULLSCREEN, everything is fine.
On windowed or borderless, when doing a Screenshot with lightshot i get a blank picture.

So what to do now?
I know the script runs on fullscreen but is that efficient?

Thanks in advance.

- - - Updated - - -

You are screenlocked.

Interesting. I’ll have a look when I’m hone

[Masbka]

@fatdoobie, In connection with the current situation, the easiest way is to set the AHK, change the name of the script, for that I like the huge product line of Oracle , to make minor corrections to the script and to run the script itself.
If, of course, the total is not banned for the installed application AHK

[FlickFrack]

Just an fyi, you were thinking it was 1.0. I never had anything besides 2.0 and 2.2 downloaded ever... literally only used it for 10 hours max between yesterday and the day before, and those were the first time I used your AHK. I did not rename anything because I'm dumb obviously. But banned nevertheless.