Camera Zoom Unlocker

[Osiris183]

Noticed this is achievable with an addon using some less than intended negative value calls of MoveViewInStart (I am not the addon author)

[Likely hotfixed as of this week, see below post] https://www.wowace.com/addons/maxcam/

Still +REP for your work as I'm sure they will fix the addon work around and your method will be ok.

[illusion_1]

The addon is already doomed, blizzard is implementing a hotfix today to break it.

From the devs page: "(Edit) This bug was already scheduled to be fixed in an upcoming patch, but the addon now forced Blizzard to move it into a hotfix"

[illusion_1]

A patch just came out and this tool doesn't seem to be working anymore.

[Torpedoes]

This bug was already scheduled to be fixed in an upcoming patch, but the addon now forced Blizzard to move it into a hotfix

Fun Detected...

[Curvystone]

Hey since Blizzard broke the Addon today and were now limited to 39 (which is still shit), any chance you'll update the tool? The desperation is back Q_Q

[Pu3Ho]

Yes, can we get an update on this godly tool?

[Filint]

Updated to 22423, apologies it is so late, I have been away the past couple of weeks. Whatever hotfixes they have implemented don't matter since this tool uses a completely different method

If you're having issues getting it to work:
Make sure your antivirus isn't blocking/deleting the Unlocker.exe file, Bitdefender in particular likes to delete anything and everything...
Make sure you're running the correct version for the current WoW build; if I haven't updated the tool post here or let me know via PM.

[sk68]

Hello Filint,

Want to thank you for your work. Was wondering if you have tested it with non-US versions of the 22423 client. Thanks in advance for your reply.

[Filint]

Hello Filint,

Want to thank you for your work. Was wondering if you have tested it with non-US versions of the 22423 client. Thanks in advance for your reply.

Not specifically, but I don't think there is any reason that it shouldn't work. Let me know if it does/doesn't

[sk68]

doesn't seem to work in the latest legion version 225xx Tried zooming out in Dalaran but no go.

[Jaladhjin]

"confirmed safe"

Good luck finding this..

No matter who tells you anything.. the most anyone including those same people will say if you're banned is sucks bro.. sorry to hear.. or yup.. that's why you don't run cheats on accounts you highly value ;-)

[Filint]

Updated to 22522. Shortly I'll make it use patterns so it doesn't break with each patch.

Good luck finding this..

No matter who tells you anything.. the most anyone including those same people will say if you're banned is sucks bro.. sorry to hear.. or yup.. that's why you don't run cheats on accounts you highly value ;-)

Yeah. There is never a "confirmed safe" when you are messing with the way a game is supposed to work. But, we can reduce the likelihood of there being an issue as much as possible, for example by avoiding or subverting any methods that the anti cheat currently employs. Of course if you could not bear to lose your account, you might like to think twice before running anything like this. Everyone has their own free choice whether to use it or not :-)

[Dekaii]

Thank you very much for the update

[OldSchoolFarmin]

Not working for me

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

************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at UnlockUI.Form1.button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.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: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
UnlockUI
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Alex/Desktop/UnlockUI.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

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

[Filint]

Not working for me

*snip*

Hi, please ensure you have both exes in the same directory, so: Unlocker.exe and UnlockUI.exe

If that doesn't work, let me know.