Hi, thank you for trying to fix it. I bought this injector 2 days ago while you were trying to fix it. Hopefully you add a week or two to my subscription. If this works out, I will def be buying permanent subscription.Quote:
For whoever purchased it while it was unstable (or everyone for that matter), don't worry, I'll add in a week or two to everyone because of the time delay.
Still trying to fix it, found methods and customizing it - trying to make it as safe as possible.
Awesome man! Thanks for keeping us up to date. Will definitly buy your injector, price won't matter.Quote:
Great progress so far! I'll be implementing a Kernel Manual Map DLL Injection. (The DLL will be purely exclusive to my injector so nobody can steal it =], I have set up small prototypes for testing.)
You'll be able to experience the first internal hack for DayZ SA 0.53 on ePvP in a few days.
Note that I am not replying on Skype due to heavy coding, forgive me if you are still awaiting a reply.
Expect the price of the injector to become higher after the update is released. And because of the long delay, whoever already bought it will have his subscription extended by the time it took updating.
These menus are never safe since they have been released to public, but you can change some variables making it undetectable for now.Quote:
Could someone help me please... there is not a single menu not banned out there at the moment did I get that right? Or can u still safely use the Necromancy/Jay/Lystic etc. or rather, were they ever safe? Sorry, I only used Maltilones external hack so far, still a noob :)
Quote:
These menus are never safe since they have been released to public, but you can change some variables making it undetectable for now.
Any menu can be used as long as you change most variable names.
Xenos is open source, it sure did help. But I'll be creating a whole new protection system.Quote:
Youre using Xenos driver for manual mapping? I read its working fine, so good idea!
Quote:
Xenos is open source, it sure did help. But I'll be creating a whole new protection system.
I've crashed my computer (and made it un-bootable) at-least 6 times attempting to create the kernel driver, then decided to go with Xenos' WinAPI itself haha.
I will keep the normal method for re-scanning, and add a new "Kernel Inject/Execute" button for 0.53+ (it will work on future versions as well)
On the update protection-wise, the hack will re-obfuscate itself upon launch (yes, literally) as well as all its component (the DLL to be injected will have a unique hash and name everytime)
It will contain dynamic data editing, so I won't be using ReadProcessMemory/WriteProcessMemory in case they're scanning for kernel32.dll and a lot more *secret* stuff to come!