I don't know if this has been said or not, and if not, why it hasn't. The developers decided to have multiple .dlls for this game for modes and client and server and etc. The game will eject and re load .dlls dynamically depending on a giant list of things that we have no control of.

The trainer accurately injected into a .dll that is present, but if that .dll is "gone" or dynamically unloaded then reloaded, the trainer is no longer attached to the original .dll and no longer has code injection hooks into it.

There is nothing we can do about this and any mods or trainers for this game that are trying to accomplish anywhere NEAR what we are doing with our trainer is going to run into the same issue, namely that the game developers decided to go this tract.

Note, in case you haven't been told this either, that the game has multiple other issues making it quite difficult to work on.

1. game is using the SWARM engine, which runs data through the same functions. In other words millions of addresses are running through the same read and write functions, which we then have to find ways to isolate JUST the player HEALTH for example.
2. this engine is also using scripting in these functions, which the logic of the game isn't some function in a spot that is just reading PLAYER HEALTH or something. We have to isolate functions or scripts or isolate values to try and make things happen. Not so easy, takes time, and some things just aren't going to be possible.
3. Game injects and uninjects dynamically certain .dlls
4. Game has online modes and offline modes and all the differences that come with that.
5. Game uses shift assembly commands to "encrypt" data so that it's not readable in normal means. Health isn't just stored as a plain number like 100 nor ammo nor reload, etc.
6. Game is patching a lot, forcing updates possibly or checking code and all the changes and isolation of all these values and options and this could possibly be an enormous undertaking.
7. Game uses anti cheat and kernel mode drivers to lock down the game from being read and accessed by memory readers, searchers, trainers, mods. Successfully bypassing this is step 1 and doesn't allow any of the other steps.
8. Due to the nature of the game we are, ourselves, using custom .dlls to isolate data and enable easier manipulation of the game values. Some over zealous anti virus and malware software may see the injection into the game or the files themselves as false positive malicious and prevent the injection which will seem like the trainer "doesn't work" or flat out may crash.

I could go on, but PLEASE understand that most issues with the trainer are due to antivirus not allowing our tools to inject, people didn't use the launcher to run the game, the dynamic load or unload of the game's .dlls, or the fact people are trying to do things online (IDIOTS) which in the end is likely to cause the developers to crack down on this game and possible kill your ability to enjoy playing the game alone and with mods/trainers.

I hope this helps for people to understand.

best,
Cal