rXYZ - Updated Rotation-based XYZ

[kpe]

Works perfectly! More smooth and faster than the original, without any DC! +1

[Buntaro]

Tyvm for the update

[gippy]

How do i stop it from shooting me miles forward in one direction and then it dcing me?

Nvm, i fiddled about with the settings and realised i had the clip distance set far too high :P

[PoSTReL]

Clip Dist 0.005
Sleep time 1000
DC me everytime i move after using hack (( ...

[Vaudville]

Hey Drakefish,

I'd really love to use this, but I seem to be getting an error. Something to do with .net I presume.

OS: WinServer 2k8 64bit.

I have the VC++ redist installed, and .net 4.

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.TypeInitializationException: The type initializer for '.' 
threw an exception. ---> System.BadImageFormatException: 
Could not load file or assembly 
'fasmdll_managed, Version=1.0.3262.20709, Culture=neutral, PublicKeyToken=null' or one of its dependencies. 
This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
File name: 'fasmdll_managed, Version=1.0.3262.20709, Culture=neutral, PublicKeyToken=null'
   at Magic.BlackMagic..ctor()
   at ...cctor()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

   --- End of inner exception stack trace ---
   at ..(Object , EventArgs )
   at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ComboBox.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)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
rXYZ
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Administrator/Desktop/rXYZ.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
BlackMagic
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Administrator/Desktop/rXYZ.exe
----------------------------------------

************** 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:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

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.

EDIT:
Nevermind, I fail miserably. I had another fasmdll_managed on my desktop. -.-' sorry.

[frozenthorn]

:-( so gm island is now unreachable.

With 4.0.3 I think they changed how the blue "wall" area works, because I was able to move right through it with Qwerxy's noclip feature, which I don't think worked in 4.0.1

[DrakeFish]

The Player Pointer didn't change in the today patch (4.0.3a) meaning this is still usable and updated. Happy "cataclysm" exploring!

Side note to the people having troubles using this: It could be either due to a very low fps or to a very high ping. This kind of hacks require a bit of synchronization with the server. Try to make the Clip Distance lower or the Sleep Time higher.

[Dariss]

Idk why, but with the new patch it shows the process available, but will not hook my players position at all.

[fatalpop]

It doesn't seem to work at all for me, I ran it as admin, attached it, hit the keybinds, and nothing.

[DrakeFish]

Hmm.. It did work for me, I updated the offset and then noticed it was the same.

[jjfortherear]

same as fatal, I'll have wow selected and the position doesn't update, keybinds don't do anything

[DrakeFish]

Maybe it's cause of my client... oh well I'll check at this.

[SacredSpenny]

Same problem with me, attaach but no coords and wont work :P

[frozenthorn]

Yeah not working on 4.0.3a client, thanks for trying to address it so quickly tho.

[m60gunner]

I tried using it this afternoon and it will attach to warcraft but I get no coordinates and when I hit the keypad 5 to try clip through the door it says 'you cant do that now' in red text in the warcraft client and nothing else happens.