Our Drox Operative Trainer is now available for version 1.043 and supports STEAM, GOG.
Our Drox Operative message board is available to provide feedback on our trainers or cheats.
Kresher posted on Jun 29, 2013 9:50:24 AM - Report post
Please update the trainer for the new version 1.012, thank you.
ELITE
prd744 posted on Jul 12, 2013 10:38:06 PM - Report post
Please update the trainer to be compatibe with the 1.014 patch.
ELITE
TheBob posted on Aug 29, 2013 12:21:47 AM - Report post
Would you be able to update the trainer for V1.02 please?
INACTIVE
Lintman posted on Sep 20, 2013 5:24:20 PM - Report post
Can you guys update for the 1.24 version, please?
Thanks!
ELITE
nuhlir posted on Oct 24, 2013 9:25:17 PM - Report post
I know its been asked before and I hate to bug you guys, but could you please update the trainer for the 1.24 version? I appreciate your hard work and hope that you might be able to fit this little game into your schedule.
Thanks a bunch.
ELITE
FARSLAYER posted on Oct 31, 2013 12:00:04 PM - Report post
You're going to hate this but v1.028 is out.
ELITE
kangaxx posted on Jan 13, 2014 8:56:04 AM - Report post
1.034 released. i have sent you an email contains game exe. thank you for not abandoning this game.
[Edited by kangaxx, 1/13/2014 11:02:54 AM]
It Is A Good Day To Die
ELITE
kld79 posted on Feb 09, 2014 6:51:12 AM - Report post
I am having trouble with the latest trainer. When run in Win8.1, it throws a .NET framework error: Bad Method Token.
My system has all of the MS updates and this happens even using compatibility mode. If you continue past the error instead of quitting, it looks and sounds like it is working but the cheats don't work and the hotkeys are all set to numpad1 instead of numpad1-7 per readme.
The full details are:
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text ************** System.BadImageFormatException: Bad method token. at System.Runtime.CompilerServices.RuntimeHelpers.PrepareDelegate(Delegate d) at System.AppDomain.add_UnhandledException(UnhandledExceptionEventHandler value) at jBsNoK4fAPCjd4D5dB.aMM8feCu9CkR2eHVMf.aYwNude8BSiVedn1jed(Object , Object ) at jBsNoK4fAPCjd4D5dB.aMM8feCu9CkR2eHVMf.gGa7wM6Bd(Object , EventArgs ) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.