@emerson1975 I've to agree with all the others. Only that a program has the abillity to create macros does not mean that someone is using it. And therefore it's not banable. Also assigning keystrokes to extra buttons on the mouse shouldn't be a banable offense, especially if the GHub software in my case is officially supported and recomended by EA/Dice on BF2042.
Also I'm using the same computer and the same setup with the same background tasks also in the following EAC protected Games: Hunt, War Thunder, Division 2 and Ghost Recon Wildlands. Never were flagged and banned in one of those games. Not for GHub, not for my RGB Software or any other I'm running.
I've digged now more into EAC. At first one of my speculations that also killing bots in Solo could have been the cause as there are several points on different maps where Bots could be safely taken out from a distance without getting killed as the bots at these points are more focussed on killing other bots. I first thought this might have been considered boosting or exploiting.
But reading through the DEV-manuals of EAC how to implement and what to be aware off I can definitely say that this is not the cause of an EAC-ban... (At least if it was EAC which banned me)... EAC is not able to detect exploits and ban therefore. Regarding the EAC documentation those kind of things needs to be manual monitored by the Devs itself.
The following is directly out of the EAC Dev Manual:
Game Exploits
Game logic errors, bugs, or edge cases are often discovered and exploited by players. However, anti-cheat understands the game code to be working as written and cannot solve these issues. As the game developer, you must fix these problems as you continue to develop and new exploits are discovered.
Also it is stated in the docs that EAC could mabye not work as intended and produce false positives if it's not implemented in the way it should. I've seen the page but need to find it again before I couldd copy & paste it in here.
So this is at the moment my best guess. Dice or any other studio involved into 2042 must have screwed it up at some point.
But in the end I can't really tell you what happened as EA/Dice is not giving any information about the cause of a ban... If it was EAC or a manual one or for foul language in Chat or, or, or...
I got now a conversation running with a real human from EA tech support about giving me all the related data in this matter as GDPR in Europe makes it mandatory for them to do so. Will hopefully soon find out what the ban is about and then I know better how to action.