2025-06-04kro (en)

[Rhyperion]

his git just moved

https://github.com/Jhonvaliense/ROClient_en

[112112113]

On 2025/5/4 at PM11点26分, Brynner said:

单击服务器选择后，是否有人遇到客户端因重播而崩溃的情况？

I'm having the same issue same issue

[berato]

Hello! how to increase zoom out / zoom in it??

[Rhyperion]

WARP Patches that work i've tested:

Enable effect for all maps
Increase map quality

[hendra814]

On 5/1/2025 at 8:27 PM, Skylove said:

20231220+ CLIENT bodystylefix Source :https://github.com/AoShinRO/brHades/commit/1396b012600db9b0688f3cd3fdb9ac273d525bd0
 20231220+ CLIENT bodystylefix.diff

failed when apply the patch

[WhiteEagle]

5 minutes ago, hendra814 said:

failed when apply the patch

do it manually. It works for me

[b1rbert]

Took a look at the client and I'm very suprised at how good everything works. after what feels like ages of client drought you brought us a nice gift, thanks skylove!

Those anyone know a hex edit to increase max hairstyles? currently capped at 42

[amm0nition]

So I applied the patch, and they're still showing me novices. I manually patched battle.hpp because int is now int32. Is there something I'm missing? 

Edit: Solved it. I need to change clif_changelook(&sd->bl,LOOK_BODY2,0); to  clif_changelook(&sd->bl,LOOK_BODY2,sd->status.body);

Edited May 8 by amm0nition
Found Solution

[Santheus]

9 hours ago, amm0nition said:

So I applied the patch, and they're still showing me novices. I manually patched battle.hpp because int is now int32. Is there something I'm missing? 

Edit: Solved it. I need to change clif_changelook(&sd->bl,LOOK_BODY2,0); to  clif_changelook(&sd->bl,LOOK_BODY2,sd->status.body);
 

So I found the line of code : clif_changelook(&sd->bl,LOOK_BODY2,0); inside PC.CPP instead of battle.hpp. So basically, edit the line of code to : clif_changelook(&sd->bl,LOOK_BODY2,sd->status.body); and then recompile rAthena again, is that correct?

[Andre]

is there a way to fix the lightmaps? normally u have to use: http://nemo.herc.ws/patches/IncreaseMapQuality/ this patch.

 

EDIT: okay got it!

look for this

6A 00 6A 00 6A 01 8D 85 FC FF FB FF B9 54 41 22

and change it to:
 

6A 00 6A 00 6A 04 8D 85 FC FF FB FF B9 54 41 22

means 01 to 04

Edited May 8 by Andre

[amm0nition]

1 hour ago, Santheus said:

So I found the line of code : clif_changelook(&sd->bl,LOOK_BODY2,0); inside PC.CPP instead of battle.hpp. So basically, edit the line of code to : clif_changelook(&sd->bl,LOOK_BODY2,sd->status.body); and then recompile rAthena again, is that correct?

Yes, you replace that line inside pc.cpp and then recompile the server.

[amm0nition]

Can someone tell me how to disable Enable 44khz Audio because this patch worsens the audio quality of newer BGMs instead of improving anything.

[hendra814]

On 5/4/2025 at 7:06 AM, Skylove said:

 

Download x64dbg from:
https://x64dbg.com/

1. Run x32dbg as Administrator.

2. Load the 2025-03-19 client in x32dbg.

3. In x32dbg, go to the Patch menu (Shortcut: Ctrl + P).

4. Click Import, then load the downloaded patch file ExtendCashShopPreview.1337.

5. Choose Patch File to create a new patched client!

video :  https://drive.google.com/file/d/1gjFYTEHKpUnUA-gbThLNOKlIVxZSj0zY/view?usp=drive_link

 

please help

need permission to see the video, i'm have issue like this

[hendra814]

On 5/7/2025 at 10:02 PM, Newbiey said:

Yes just diff by manual.

so sad, so many error after do manually.

 

[Santheus]

32 minutes ago, hendra814 said:

so sad, so many error after do manually.

 

A a lot of lines of code in the Github commit  (BODY Style Fix DIFF) do no match the same starting point of where to edit those changes. You have to compare and reference where those lines of code 

are placed inside of the latest rAthena commits in order to know where to DIFF those changes manually. Thus your seeing those errors while rebuilding your rAthena.sln in Visual Studio

[Santheus]

20 hours ago, amm0nition said:

Yes, you replace that line inside pc.cpp and then recompile the server.

So, I have DIFFed manually all the associated files from this github commit : https://github.com/AoShinRO/brHades/commit/1396b012600db9b0688f3cd3fdb9ac273d525bd0#diff-16a6f317c581ce365a41a9846cf48dc45c8d6ac0256a7c45849e6e1b37100ecdR13025-R13037

Applied the change you made on pc.cpp

Patched my kRO client

And yet all my characters are still displaying as Novices

There must be something I skipped 

My brain is seriously racked right now trying to fix this error 

I'll give it a rest for today. I'll wait for future assistance.

[dark elf]

8 hours ago, Santheus said:

So, I have DIFFed manually all the associated files from this github commit : https://github.com/AoShinRO/brHades/commit/1396b012600db9b0688f3cd3fdb9ac273d525bd0#diff-16a6f317c581ce365a41a9846cf48dc45c8d6ac0256a7c45849e6e1b37100ecdR13025-R13037

Applied the change you made on pc.cpp

Patched my kRO client

And yet all my characters are still displaying as Novices

There must be something I skipped 

My brain is seriously racked right now trying to fix this error 

I'll give it a rest for today. I'll wait for future assistance.

https://github.com/Jhonvaliense/ROClient_en/blob/main/20231220%2B CLIENT bodystylefix.diff
I applied the diff patch from here, and it seems to be working well!
I noticed that there are differences in the pc.cpp file.

Edited May 10 by dark elf

[amm0nition]

8 hours ago, Santheus said:

So, I have DIFFed manually all the associated files from this github commit : https://github.com/AoShinRO/brHades/commit/1396b012600db9b0688f3cd3fdb9ac273d525bd0#diff-16a6f317c581ce365a41a9846cf48dc45c8d6ac0256a7c45849e6e1b37100ecdR13025-R13037

Applied the change you made on pc.cpp

Patched my kRO client

And yet all my characters are still displaying as Novices

There must be something I skipped 

My brain is seriously racked right now trying to fix this error 

I'll give it a rest for today. I'll wait for future assistance.

That is because the client now uses bodystyle to display job sprites instead of job. Run a query script in your database table "char" to copy the job column into the body column. Before 2023 clients, bodystyle's only used up to value 1 for alternate costumes. Now they can be filled with whatever the job ID and the sprite will display that. Your previous chars were still using bodystyle 0 or 1 -- which are Sprite ID of Novice and Swordsman

UPDATE `char`
SET body = class;

Run this in query.

[WhiteEagle]

Another question, can someone recommend a hex editor?
 

[Santheus]

6 hours ago, amm0nition said:

That is because the client now uses bodystyle to display job sprites instead of job. Run a query script in your database table "char" to copy the job column into the body column. Before 2023 clients, bodystyle's only used up to value 1 for alternate costumes. Now they can be filled with whatever the job ID and the sprite will display that. Your previous chars were still using bodystyle 0 or 1 -- which are Sprite ID of Novice and Swordsman

UPDATE `char`
SET body = class;

Run this in query.

Running this query did fix the problem temporarily. However, when I executed @jobchange commands again the same problem persisted

EDIT: (defaulting to novice sprite, or sometimes swordsman)

Edited May 10 by Santheus

[amm0nition]

4 minutes ago, Santheus said:

Running this query did fix the problem temporarily. However, when I executed @jobchange commands again the same problem persisted (defaulting to novice sprite)

Now then, are you sure that you've properly patched your src files?

[amm0nition]

51 minutes ago, WhiteEagle said:

Another question, can someone recommend a hex editor?
 

HxD is enough for this kind of hex editing

[WhiteEagle]

23 minutes ago, amm0nition said:

HxD is enough for this kind of hex editing

Thanks ~ ^-^

[dark elf]

There are many features in this public repository that aren't implemented in rAthena. I'm really thankful!
https://github.com/AoShinRO/brHades

[WhiteEagle]

1 hour ago, dark elf said:

There are many features in this public repository that aren't implemented in rAthena. I'm really thankful!
https://github.com/AoShinRO/brHades

Yes, I hope that rAthena will also implement this relatively soon. The automated translation alone is interesting.