xFranko

You probably have an error in your database that isn't being caught and is silently making the process of new account creation/character init getting stuck, try to run in debug mode and trace with breakpoints.

Check this and see if the button is maybe disabled, it looks like you have a modified client not the original one. https://cooldown.dev/topic/673-tutorial-how-to-removeresizedelete-any-gui-button

Um, this doesn't make any sense, if the source came with 167.94.158.235...just change it to your local ip? You could maybe try https://www.radmin-vpn.com/ if you want your friends to join with you, it basically create a LAN over the internet. most IPs would start with 26.x.x.x for it.

This is most likely means the client isn't even reaching your auth server Try to debug by printing what your auth server is receiving Check the injector or loader you're using that it's actually hooking correctly Check the ports in your loader config and check the host (and maybe try to avoid loop back address 127.0.0.1 - some sources don't support it) Also check this thread that Spirited created previously for most common issues https://cooldown.dev/topic/6-guide-client-downloads/

Thank you, this looks good! I think it would be nicer if you format the thread properly because it's a bit harder to read, what you pasted was meant for .md formats but the forum doesn't support rendering it.

Oh wow that's amazing! I thought I would only see such thing in Tow Conquer, now we got this too!

Yep I understand your motive was for good intention, I was just replying to "Shang"

If something is open source and the license explicitly allows redistribution, I don’t see an issue with someone packaging it so less-experienced users can use it without having to compile or set everything up themselves. Also, it’s not fair to paint @darkfox as a bad actor. He has personally helped me multiple times without ever asking for anything in return. He also continues to maintain ConquerLoader, and in many cases he didn’t even take credit for large parts of it, instead properly crediting the original authors.

Hey @carniato Sadly it still crashes past login after getting the Entity UID, I will message you privately for a version to test with That's how it looks before the client crashes and shutsdown Crash Logger Initialized DLL Path: O:\Games\Conquer\MTA Conquer\Client v6609 - MTA\Env_DX9\ Game Path: O:\Games\Conquer\MTA Conquer\Client v6609 - MTA\Env_DX9\ Log File: O:\Games\Conquer\MTA Conquer\Client v6609 - MTA\Env_DX9\crash_log.txt ======================================== [2026-01-09 15:07:54] Crash logger initialized successfully [2026-01-09 15:08:13] ======================================== CRASH DETECTED ======================================== Exception Code: 0xC0000005 (EXCEPTION_ACCESS_VIOLATION) Exception Flags: 0x00000000 Exception Address: 0x016A43B4 Exception Parameters: 2 Parameter[0]: 0x00000000 Parameter[1]: 0x00000000 Access Type: READ Fault Address: 0x00000000 Register Context: EAX: 0x00000000 EBX: 0x1C951378 ECX: 0xAB1ABDB5 EDX: 0x0019F9E4 ESI: 0x1C837EB0 EDI: 0x1CB0CB90 EBP: 0x00000007 ESP: 0x0019FA20 EIP: 0x016A43B4 EFLAGS: 0x00210283 Module Information: Crash Module: graphic.dll Module Base: 0x01670000 Module Size: 0x001A2000 Offset in Module: 0x000343B4 Stack Trace: [00] 0x016A43B4 [graphic.dll] Font_CloseSys+0x8B4 [01] 0x01689CCB [graphic.dll] TargetBmpCreateEx+0xAB Memory Information: Fault Address: 0x00000000 Base Address: 0x00000000 Region Size: 0x00010000 State: FREE Type: PRIVATE Protect: 0x00000001 ======================================== [2026-01-09 15:08:15] DLL_PROCESS_DETACH: Shutting down... [2026-01-09 15:08:15] Crash logger shutting down

Hey @carniato! Thank you so much for this really, and sorry for the late reply I got busy with work so didn't have further time to debug the issue further on my end, I will give this one a try and will update here with the results, I hope it works! And if it does I maybe could also create a PR with my logger so that for the future it's more robust to catch such issues Will update you soon! : )

Did it ever crash your client past this login point before? I tried to add a logger to detect the crashes, seems like it's trying to access wrong memory address or smth during dll unload for a font cleanup method it seems Font_CloseSys (I'm not the best at C++ xD) , I will update if I find a solution, this is probably related to my client even though I'm on 6609 [2026-01-07 07:40:26] ======================================== Crash Logger Initialized Log File: O:\Games\Conquer\MTA Conquer\Client v6609 - MTA\Env_DX9\crash_log.txt ======================================== [2026-01-07 07:40:27] Crash logger initialized successfully [2026-01-07 07:40:27] DLL loaded (DLL_PROCESS_ATTACH) [2026-01-07 07:40:51] ======================================== CRASH DETECTED ======================================== Exception Code: 0xC0000005 (EXCEPTION_ACCESS_VIOLATION) Exception Flags: 0x00000000 Exception Address: 0x015C43B4 Exception Parameters: 2 Parameter[0]: 0x00000000 Parameter[1]: 0x00000000 Access Type: READ Fault Address: 0x00000000 Register Context: EAX: 0x00000000 EBX: 0x1A43DEF0 ECX: 0x93C87EF3 EDX: 0x0019F9E4 ESI: 0x1D8921C0 EDI: 0x1D9D0008 EBP: 0x00000007 ESP: 0x0019FA20 EIP: 0x015C43B4 EFLAGS: 0x00210283 Stack Trace: [00] 0x015C43B4 Font_CloseSys+0x8B4 [01] 0x015A9CCB TargetBmpCreateEx+0xAB ======================================== [2026-01-07 07:40:52] DLL unloading (DLL_PROCESS_DETACH) [2026-01-07 07:40:52] Crash logger shutting down

You're the best man!

Thank you so much!

Thank you so much! this is much helpful! Tho I still cannot understand what are exploits.. Also some others questions: was there a specific BP shared across the guild depending on the rank, or everyone shared the same battle power from Arsenal? For PK Donation, must the killer/killed be from enemy guild or anyone? For Guide donation, how was that calculated? so for example if they're Level 10 and I am in a team with them and level them up to 20 (that would be 10 Guide points? )

Most of you probably already know this, but it’s still a good idea to document it here. Sometimes you may want to remove annoying buttons you never use, or simply rearrange or resize parts of the UI. This tutorial will be split into two sections: Deleting a button Moving & Resizing In this part, we’ll focus on deleting a button. We’ll be using Resource Hacker to modify Conquer.exe, editing the GUI.INI, GUI800X600.ini, Control.ani files, and removing some .dds image files. Note 1: Make a backup of anything you will modify in case you break your GUI! Note 2: This has been tested on 6609 I'm not sure about the behavior on older clients. ____________________________________________________________________________________________________________ [1.1] Example: Removing the “Poker” Button First, type the following command in the game Talk chat: /enablefocus (Credits goes to @Spirited for this command) This allows you to identify a button’s ID by simply hovering over it. When you hover over the button, look at the top-left corner of the screen. You’ll see information displayed in this format: [parent -child] You’ll also see the ANI reference name, which points to the DDS image controlling that button. The first number is the parent window ID The second number is the child window/button ID under that parent For example: [579 - 3055] 579 → parent container (this holds most of the icons at the top-right area btw) 3055 → the specific ID of the Poker button This exact same format is used inside the GUI.INI files (along with x, y, width, height, etc.). ____________________________________________________________________________________________________________ [1.2] Editing Conquer.exe with Resource Hacker Now that we have the button ID, open Resource Hacker and load Conquer.exe Click Open Make sure you edit the correct executable (in my case, I’m using the DX9 version, so I edit the exe inside ENV_DX9) Next: Expand the Dialog section You’ll only see parent windows, so search for 579 Inside this dialog, you’ll see an approximate layout of all the buttons in that container. Each line represents a child control under parent 579, written in something similar to a CSV format. The second value in each line is the button ID we found in-game: CONTROL "ShowHand", 3055, BUTTON, BS_OWNERDRAW | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 82, 62, 14, 13 To disable the button: Replace WS_VISIBLE with WS_DISABLED Updated line: CONTROL "ShowHand", 3055, BUTTON, BS_OWNERDRAW | WS_CHILD | WS_DISABLED | WS_TABSTOP, 82, 62, 14, 13 Now Compile [1] and Save [2] (Make sure to close the client first), a backup will be created automatically under the name Conquer.old.exe in the same file you can keep or delete it. At this point, the button will no longer be clickable, but the image will still be visible. ____________________________________________________________________________________________________________ [1.3] Removing the Button Image Next, open GUI.INI or GUI800X600 and search for the button entry: This section defines: Button position and size The ANI section that controls its image Now open: ani/Control.ani Search for: [Dentrance_DentranceBtn] You’ll find four frames, each pointing to a DDS image used for different button states: Simply delete this entire section. Once removed, the button will be completely gone when you open the client. ____________________________________________________________________________________________________________ [1.4] Optional Cleanup For extra cleanup, you can also delete the DDS image files from their directory since they’re no longer needed alongside the entries from GUI.ini However, removing the ANI section alone is enough to fully hide the button. ____________________________________________________________________________________________________________ [1.5] Alternative Method (Without /enablefocus) If you can’t use the /enablefocus command, you can use WinSpy instead. Drag the WinSpy finder tool (shown in the screenshot below) Drop it on the button you want to remove WinSpy will give you the Caption, which matches the first string in the Resource Hacker control entry. Note: WinSpy does not provide the window ID So you’ll need to: Search for that caption string in Resource Hacker using CTRL + F Locate the matching control manually And that’s it. ____________________________________________________________________________________________________________ [2.1] Resizing/Moving a button By now, resizing should be straightforward. Simply adjust the size values in the GUI.INI file. Make sure to apply the same changes in GUI800X600.ini as well, so the button displays correctly at both resolutions. If you prefer a visual approach, you can use the /enablefocus command. This allows you to resize a button by dragging its corners. For example, if the nobility icon appears too large, you can reduce its size by dragging the edges of the red selection box. You can also move the button by dragging it, and the new position will be automatically saved to your GUI.INI file. Note 1: I recommend avoiding direct visual editing when possible. It’s easy to accidentally click another button (such as a nearby button), and sometimes the UI may behave unpredictably. In some cases, the button can end up outside the window boundaries and become invisible. Note 2: Resizing won't work for most types of buttons because their sizes will depend only on the actual DDS image, what you will control is the area that's clickable (the red square) when resizing. Note 3: You will often make the button unclickable when moving it with the command, to fix that just restart the client and it will be clickable in its new position. Note 4: If you wanna move an element, you won't be able to move it outside its parent container (you can know the element boundaries by [RED] edges and parent by [YELLOW] edges when hovering with the command enabled) for example the settings button, you won't be able to move it (if someone figures out a solution maybe they can drop in comments! ) After Resize : Note 5: You can also use WinSpy if you want to experiment with a button’s position without restarting the client or using in-game commands. This helps reduce the risk of breaking something, since WinSpy changes are applied only in memory and will be discarded once the client is restarted.