Ai4rei

Updated to 2.4.18, fixes a potential crash due to wrong memory usage.

Updated to 2.4.17, adds iRO:Restart, kRO Zero and phRO, and updates jRO patch information (for details see docs). Fixes a super-random crash on super-modern systems.

Updated to 2.4.28, fixes file corruption caused by back-ports from trunk, that were added to 2.4.26. Please read follow up instructions, if you update from 2.4.26 or 2.4.27.

Seems .26 broke RGZ unpacking and since kRO has been resetting rdata.grf, it got corrupted. But no worries, the GRF will recover after I fix the patcher.

Hello Ai4rei, after update to last version 2.4.27 this happen: 

 
Happens exactly after this download finish:

 
 
why this happen? The rdata is in kro folder. 

As per private request, patches for 2015-09-16aRagexe (unpacked):
// long jmp (1) F:85C00F85????FFFF6A11 R:85C00F85000000006A11 // short jmp (3) F:85C075??6A11 R:85C075006A11 Which is basically the same, as above, except that the long jmp is negative. For wild-card impaired hex-editors the patches are:
F:85C0752F6A11 R:85C075006A11 F:85C075396A11 R:85C075006A11 F:85C00F8528FEFFFF6A11 R:85C00F85000000006A11 F:85C0752F6A11 R:85C075006A11 The key sequence for this patch is:
CALL <150916A.CSession::IsSiegeMode> TEST EAX,EAX JNZ <150916A.+??> PUSH 11 ; /Key = VK_CONTROL CALL NEAR EBX ; \GetAsyncKeyState Where the call to GetAsyncKeyState may take various forms.

As per private request, patches for 2015-09-16aRagexe (unpacked):
// long jmp (1) F:85C00F85????FFFF6A11 R:85C00F85000000006A11 // short jmp (3) F:85C075??6A11 R:85C075006A11 Which is basically the same, as above, except that the long jmp is negative. For wild-card impaired hex-editors the patches are:
F:85C0752F6A11 R:85C075006A11 F:85C075396A11 R:85C075006A11 F:85C00F8528FEFFFF6A11 R:85C00F85000000006A11 F:85C0752F6A11 R:85C075006A11 The key sequence for this patch is:
CALL <150916A.CSession::IsSiegeMode> TEST EAX,EAX JNZ <150916A.+??> PUSH 11 ; /Key = VK_CONTROL CALL NEAR EBX ; \GetAsyncKeyState Where the call to GetAsyncKeyState may take various forms.

The file is present on the mirror, so no problem there. There should be a  rsu-kro-rag-lite.exe-debug.log file in the same folder as the patcher, that says why it failed to retrieve the file.
 
Updated to 2.4.26, updates phRO patch information, fixes few issues and removes idRO and some iRO variants.

Updated to 2.4.19, updates twRO patch information and makes the UI less confusing.
Updated to 2.4.20, the real thing.
Updated to 2.4.21, updates kRO patch information.
Updated to 2.4.22, fixes potential patch process issues introduced in previous release.
Updated to 2.4.23, removes notices and behavior related to archives over 2GiB.
Updated to 2.4.24, updates bRO patch information and removed fRO (closed).
Issued hotfix for kRO Zero (2.4.24.807), updates kRO Zero patch information.

Updated to 2.4.25, updates kRO patch information, allows mirrors for kRO Zero and allows HTTP mirrors.

Merging is still in progress, the rsu codebase is messy, so it will take some time.
Update 2017-08-04:
Someone give me a full week hikikomori mode without disturbance and I can release it...
Update 2017-08-05:
People who will want to extend the functionality of the patncher, can start learning COM. The plug-in will have to establish communication with a call like this:
hr = CoGetClassObject(CLSID_PluginServiceProvider, CLSCTX_INPROC_SERVER, NULL, IID_IClassFactory, &lpServiceProvider); Update 2020-08-18:
Obviously no one will read this, and no one will dare to make a necro-post in response to this. Since I have nothing to do for a week, I'm finishing that thing. Things are coming along quite well so far. The updater part is written from scratch, since the RSU code-base is too outdated. Not sure about the ROCred part, there is currently no UI. Oh yeah, there is no name either...

I was bored, so here you go @PunkBuster:
// long jmp F:85C00F85????00006A11 R:85C00F85000000006A11 // short jmp F:85C075??6A11 R:85C075006A11 Any combination of these two patches should yield total of 4 hits. You did not state a client version, so these are only tested up to 2012.

RO Open Setup


About
Enhanced alternative for the default game setup application shipped with every RagnarokOnline installation. Comes in several languages, is free of cost and works on every 32-bit and 64-bit Microsoft* Windows* platform.

Known Issues
None.

Download & Website
http://ai4rei.net/p/opensetup

License

This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.

RO Credentials


About
Simple and tiny client launcher+login. Has no prerequisites and runs on all Windows versions. Known Issues
[aavc] This tool is not safe for computers running Avast Anti-Virus. Download
binary, reference source Q & A Is it customizable?
Yes. How?
With resource editing tools, such as ResourceHacker. All text and icons can be customized. Settings can be edited in an INI file, instructions on how to do that are provided in the example files together with the launcher. What is "reference source"?
You cannot compile it (unless you provide the missing components), but see what functionality the latest binary contains. I want it to be xyz.exe, but it does not read the INI file. Why?
You have to match the INI name to the EXE name. rocred.exe -> rocred.ini mytest.exe -> mytest.ini  
How can I embed an INI file into the EXE?
Add the INI file as RCDATA resource named CONFIG with ResourceHacker. How do I use background skinning?
Create a file named bgskin.bmp (magenta #ff00ff is considered transparent). You can also embed the file as BITMAP resource with the name BGSKIN. Window size is adjusted to the bitmap size, position of controls must be set in the INI. Buttons can be skinned as well, see the INI for names.
Can I add custom buttons, if so, how many?
Yes, see the INI template for details. There is no defined limit on how many, the only constraints are available memory, GDI resources and INI size limit on some platforms. By the way, custom buttons can be skinned as well. Why does the client not auto-login when I press "Start" / Why do I have to login twice?
The client must be 2010-08-04aRagexeRE or newer and must not have the "Restore Login Window" patch and should have the "Use SSO Login Packet" patch.
This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.
 

Depending on how much you want DIY on the client, the learning curve can be steep.
Imho the primary skills are knowing how the client works from the player perspective (i.e. the whole functionality available, without modifying it) and knowing the subject you want to include/exclude. Thus, if you want to deal with bots, you should also know how bots work and be able to setup and use one.
Further down, you have to deal with C++, machine code generated from C++ (assembler), disassembling, debugging and Win32 API. If you stumble upon graphics stuff, GDI and DirectX 7 are also topics of interest. If you deal with network code and packets, some background knowledge of TCP is also helpful.
Note, that some things are better to be done server-side rather than client-side for two reasons:
Players can undo your client-side changes, but not server-side. Server-side is easier to edit, since you have all the source, whereas in the client you have only the gory machine code.

RO Open Setup


About
Enhanced alternative for the default game setup application shipped with every RagnarokOnline installation. Comes in several languages, is free of cost and works on every 32-bit and 64-bit Microsoft* Windows* platform.

Known Issues
None.

Download & Website
http://ai4rei.net/p/opensetup

License

This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.

RO Open Setup


About
Enhanced alternative for the default game setup application shipped with every RagnarokOnline installation. Comes in several languages, is free of cost and works on every 32-bit and 64-bit Microsoft* Windows* platform.

Known Issues
None.

Download & Website
http://ai4rei.net/p/opensetup

License

This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.

A test build for 2.15.0 is available. If someone wants to help or is just plain bored, following tests (in addition to general function) are wanted:
Behavior on AMD and nVidia graphics cards, please include opensetup.log Behavior on CJK systems, especially readability and clipping (Mis-)Behavior on Windows 10, especially clipping, please include opensetup.log (Mis-)Behavior on Windows 8(.1) Behavior on Windows 7 Functionality (whether or not selected settings work) with more recent clients (July 2018 and newer) Functionality with not so recent clients (2016 and older) opensetup.log can be created by pressing SHIFT+ESC (= write log and discard changes).
Of course you can also suggest new functionality.
Thanks in advance.

Get rsu.merge and create a file called UpdateGRF.bat in the same folder with the following content and it will do what you describe:
@rsumerge.exe data.grf update.gpf  

Depending on how much you want DIY on the client, the learning curve can be steep.
Imho the primary skills are knowing how the client works from the player perspective (i.e. the whole functionality available, without modifying it) and knowing the subject you want to include/exclude. Thus, if you want to deal with bots, you should also know how bots work and be able to setup and use one.
Further down, you have to deal with C++, machine code generated from C++ (assembler), disassembling, debugging and Win32 API. If you stumble upon graphics stuff, GDI and DirectX 7 are also topics of interest. If you deal with network code and packets, some background knowledge of TCP is also helpful.
Note, that some things are better to be done server-side rather than client-side for two reasons:
Players can undo your client-side changes, but not server-side. Server-side is easier to edit, since you have all the source, whereas in the client you have only the gory machine code.

Depending on how much you want DIY on the client, the learning curve can be steep.
Imho the primary skills are knowing how the client works from the player perspective (i.e. the whole functionality available, without modifying it) and knowing the subject you want to include/exclude. Thus, if you want to deal with bots, you should also know how bots work and be able to setup and use one.
Further down, you have to deal with C++, machine code generated from C++ (assembler), disassembling, debugging and Win32 API. If you stumble upon graphics stuff, GDI and DirectX 7 are also topics of interest. If you deal with network code and packets, some background knowledge of TCP is also helpful.
Note, that some things are better to be done server-side rather than client-side for two reasons:
Players can undo your client-side changes, but not server-side. Server-side is easier to edit, since you have all the source, whereas in the client you have only the gory machine code.

6) About removing doram in character creation

RO Open Setup


About
Enhanced alternative for the default game setup application shipped with every RagnarokOnline installation. Comes in several languages, is free of cost and works on every 32-bit and 64-bit Microsoft* Windows* platform.

Known Issues
None.

Download & Website
http://ai4rei.net/p/opensetup

License

This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.

Updated to 2.12.0, adds support for new in-game commands.
New translation bits:
IDCHECKBOX_BTG, "Turns the battle grounds icon on and off.\n\nIngame: /btg" IDCHECKBOX_CASHSHOP, "Turns the cash shop icon on and off.\n\nIngame: /cashshop" IDCHECKBOX_GOLDPC, "Turns the PC Bang gold mining UI on and off.\n\nIngame: /goldpc" IDCHECKBOX_ROULETTE, "Turns the roulette icon on and off.\n\nIngame: /roulette" IDCHECKBOX_QUAKE, "Turns screen shaking effect on and off.\n\nIngame: /quake" Updated translation bits:
IDCHECKBOX_AURA, "Turns aura effect simplification on and off.\nThis effect is displayed when you attain maximum base level for your job.\n\nIngame: /aura"  

@Beret Nemo change client exe. it may change anything what was coded in patches.
But opensetup change registry and local files configurations.