(Mods - i understand some of the things i'll post here might be crossing the line but not sure. Just edit out anything that is too much please!)
Ok, found the forums where they are discussing.
So i see a report of someone getting a week ban back in March. So FD are obviously detecting things.
Onward, let's see if i can find any evidence of them producing new versions to get around fixes FD are implementing....
Well, at least one mention of needing a new version to make it work, but that could be just general FD updates breaking the hack unintentionally, i won't consider that direct proof that FD made changes to break the hack.
Woah, found the changelog, some of the stuff it enables you to do... these hackers are damn good!
Ah, well, we have something, not what i was looking for. Initial release of this cheat was august 2018. So if the previous version got shut down around November 2017, it means FD stymied these guys for over half a year, that's pretty impressive. Of course, it doesn't prove that there were not other cheats available during that period.
Ok, talk of some unsafe options that are likely to get you detected, i'm not downloading the hack to see which ones are considered unsafe, although from the previous versions i know jumping too far could get you detected. Ah, setting energy consumption is a big red flag apparently.
October 2018, report that its detectable, reply that using in solo and carefully should be no problem.
October 2018 - ohhh, some conflict between the previous devs and the new dev. Spicy!
Ah, a hint there are two versions, one with the original devs (on the Discord that has been mentioned?) and this new guy who is public and used their code to make a new version.
Over to another forum, same cheat....
September 2018, someone reporting they were detected 3 day shadowban.
Using the cheat can cause crashes in some circumstances (possibly fixed in later versions)
Someone boasting that after their ban they could continue using, no follow up ban at the time of posting (just being more sensible?)
Another ban in October 2018 - 3 day shadowban.
November 2018 - someone reporting the version at that time is detectable, several of posters friends reported getting bans.
Creator of the other version reports the creator of this version missed some checks to avoid detection.
November 2018 - trainer not working with current version. Again, no evidence whether this is due to FD making intentional changes to stop the hack or just general patch breaking the hack.
Found Discord link for the original hackers but link expired....
December 2018 - hack stops working again. Update required.
January 2019 - stopped working again.
Feb 2019 - report of someone getting banned for 72 hours despite not using any unsafe options (no indication when this happened though)
April 2019 - trainer not working again
3 weeks ago - panic starts over trainer being exposed on FD forums.
Haha, a report from a cheater bragging about forcing a ganker to run... i must admit, i did have to smile at that. Running cheats is not right, but giving gankers a taste of their own medicine is rather priceless.
5 days ago - report of getting a 3 day shadowban, they suspect from using an unsafe option.
1 hour ago - someone just copped a 7 day shadowban. As far as i can tell, not certain they used any unsafe option.
TL;DR/Conclusions:
1) FD have been taking action against those they detect for a long time.
2) The punishments are weak. 3 day shadowban seems the norm, 7 day ban was the max reported. However, permabans have been noted in the past, specifically in 2016 and 2017. Probably repeat offenders. My guess is its something like 3 days, 7 days, then perma.
3) Detection mechanisms are weak. Some functions unsafe. Some functions fairly safe, although maybe not any more (based on the last report).
4) Patches tend to break the hack. How much of this is intentional by FD making changes to stop hacks working and how much is just due to things changeing due to the patches so the hack needs tweaking (memory addresses etc), is not possible to determine as no direct comments regarding this from the hackers.