Destiny 2 Banning Virtual Input

[josephbrc]

Don't use these macros. Keep your account safe.

For any new viewers of this repository, I don't recommend you use these AHK macros. AHK in specific is very easy to detect with virtual input anyways. Bungie now announced they are banning virtual input. This includes macros. If you do use macros in this game, I recommend custom XML ones, or SendKeys method in C#.

Example of SendKeys method:
SendKeys.Send("{Enter}")
Using timers to pair with this in WinForms is very useful.

Custom XML macros could be Razer Synapse Macro Module etc.

[preco21]

Hi, thanks for letting me know about the announcement. I didn't notice that as it's been a while since I played Destiny 2.
By the way, that's kind of surprising Bungie is finally making a move for macros. (which was quite unlikely)

I will add a note and link to this issue in the front of README.

[josephbrc]

Completely understandable. The only reason why Bungie is targeting macros now is because players are getting XP too fast with it. It's seen as more of a cheat than a utility nowadays. Your macros are written very good! I have just seen new people viewing this repo lately and want them to stay safe.

[What-Gives]

Don't use these macros. Keep your account safe.

Bungie now announced they are banning virtual input. This includes macros. If you do use macros in this game, I recommend custom XML ones, or SendKeys method in C#.

Example of SendKeys method: SendKeys.Send("{Enter}") Using timers to pair with this in WinForms is very useful.

Custom XML macros could be Razer Synapse Macro Module etc.

I have seen no mention of Bungie banning virtual input. Where did you see

[Aholicknight]

@potatoexploder can you post the news / update that Bungie said they are banning the use of virtual input? I can't seem to find it anywhere.