Auto Patch System

[thisismyaccountokay]

Hey pintinho12 thanks for this submission it really helped. I was curious if you can confirm that the patcher works for you on 5187? I was experiencing immediate crashes after logging in that only occur when using your patcher (and injecting a loader which by itself works fine). The only thing I can think of is some kind of memory address problem? If it's just me I am likely doing something incorrectly though.

Thanks in advance for any input!

[pintinho12]

Originally Posted by thisismyaccountokay

Hey pintinho12 thanks for this submission it really helped. I was curious if you can confirm that the patcher works for you on 5187? I was experiencing immediate crashes after logging in that only occur when using your patcher (and injecting a loader which by itself works fine). The only thing I can think of is some kind of memory address problem? If it's just me I am likely doing something incorrectly though.

Thanks in advance for any input!

It works for me on clean 5187

[Dark^Magic]

Originally Posted by pintinho12

It works for me on clean 5187

no he is right
the problem here
BASE_MAIN_UI0_ADDR
BASE_MAIN_UI1_ADDR

[pintinho12]

Originally Posted by Dark^Magic

no he is right
the problem here
BASE_MAIN_UI0_ADDR
BASE_MAIN_UI1_ADDR

There are a few hex editions that must be done to the exe before injecting. I forgot the addresses but I'll try to find out.

[thisismyaccountokay]

Originally Posted by pintinho12

There are a few hex editions that must be done to the exe before injecting. I forgot the addresses but I'll try to find out.

I appreciate it, thank you for looking into it. If you'd be willing to explain what you do so I can learn to help myself in the future I would appreciate it. Thanks!

Originally Posted by pintinho12

There are a few hex editions that must be done to the exe before injecting. I forgot the addresses but I'll try to find out.

Originally Posted by Dark^Magic

no he is right
the problem here
BASE_MAIN_UI0_ADDR
BASE_MAIN_UI1_ADDR

Hey Dark Magic, how did you determine that the issue was occurring at those memory addresses?

[Dark^Magic]

Originally Posted by thisismyaccountokay

I appreciate it, thank you for looking into it. If you'd be willing to explain what you do so I can learn to help myself in the future I would appreciate it. Thanks!





Hey Dark Magic, how did you determine that the issue was occurring at those memory addresses?

sorry for late i was trolling around and found it )

[pintinho12]

Originally Posted by thisismyaccountokay

Hey Dark Magic, how did you determine that the issue was occurring at those memory addresses?

When you try to read at wrong offsets it might show you arbitrary data that you can notice that is not what youre looking for xD

[thisismyaccountokay]

Originally Posted by pintinho12

When you try to read at wrong offsets it might show you arbitrary data that you can notice that is not what youre looking for xD

I understand now what those memory addresses were attempting to read - but I don't quite understand how your launcher was injecting a new X value for the MoveWindow for the main UI because I didn't see anything hooking MoveWindow - maybe I'm blind here. :S

As far as I see there isn't enough space to inject anything above a byte value at the MoveWindow call for the base ui X value either. Let me know if you have any knowledge bombs for me .

[denominator]

I'm getting an error index outside the bounds of an array in the newer version of the autopatch

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at AutoUpdater.FrmMain.ConnectToAutoUpdateServer()
   at AutoUpdater.FrmMain.FrmMain_Load(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.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)

[pintinho12]

Originally Posted by brockley1

so i opened a server 5517 real classic hard server 132.148.77.255 go there and download/register disable antivirus when u extract

There's a section for advertising which you have targeted on your linkback.
I am reporting you in all those posts.

[Baloony]

Does anyone happen to have a conquer.exe that would work with the current GUI re-arangement implementation?

[moorrr]

pintinho12 first of all thanks for that AutoPatcher, really good release. Even though it's old it's still relevant for me trying to host a 5065 private server.

I was just curious about the Injector, does most of the AntiVirus nowadays find it as a threat? Is it viable to host a private server with it or it will scare people from joining if many of their AVs will popup?

From a check I did with VirusTotal it looks like only 2/71 AVs find the AutoUpdater.exe as a threat when compiled with the injector, and 4/71 find UpdaterCore.dll as a threat, so it's look good but I was confused how so little of them considering all the Conquer Loaders I downloaded from this forum was always found as a threat.
Does removing the Injector and manually changing the Conquer.exe assembly is a waste of time?