Jump to content

Santheus

Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by Santheus

  1. Data folder is prioritized first before any grf files. But I think all clients do that. So that means you can create the same folder hierarchies that exist in GRF files. They will overwrite the same files that exist in your GRF files, since the client prioritizes data folder over grf files, meaning the client ignores reading duplicates of files if they are already loaded onto memory from the data folder. You can do your modding safer here, instead of recompiling GRF files again and again. Once you confirm there are no errors, that's the time you insert them into your modded GRF.
  2. EDIT: My post above my was duplicated due to connection timeout
  3. en.grf only contains translation files, your data.grf file should be working by default, unless you modified it or used a different data.grf file one other than the one provided official kRO client. The errors you're displaying point to files that should be contained inside data.grf, but are missing. Please do not modify files unless you know what you are doing.
  4. If you are referring to client version 2025-05-08, then yes I can confirm Cash Shop Preview is working by default here, no need to to patch @Skylove I just noticed that for client version 2025-05-08, the viewID limit extension patch for Headgears does not appear in WARP. Is there a way to manually extend the values from 3K (Default) to a maximum of 64K For client version 2025-03-19, the option does appear
  5. Several factors 1. Resellers package everything (Client and Server). So you don't have to waste effort and mental energy if something goes wrong, but sometimes it does (there are scammers after all) 2. Instant Gratiffication (some people just want the out of the box experience without the hassle) 3. A lot of people in the internet just don't dig through stuff unlike us forum peeps I could think of other stuff, but these three are the gist of it mostly
  6. I had effects disabled to remove visual clutter I did read that MVPs in renewal have extremely high VIT/DEF, but I didn't think it would be around 99% damn.
  7. Is anyone here experiencing low physical ( melee or ranged damage) on MVPs? Damage on regular mobs seem to be fine tho. EDIT: I've tested ranged and melee PHYSICAL DMG as well on Mini-MVPs as welll, and dmg formula seems to be fine here as well. There seems to be a problem with PHYSICAL combat damage not correctly working on MVPs.
  8. Yes, I noticed the the small differences in the pc.cpp file as well So I recompiled the src after manually DIFFing from that blob by Jhonvaliense, and everything works fine now Everything is working as intended now after I DIFFed everything from Jhonvaliense's blob @Everyone For anyone recompiling in the future Please do not use the commit here: https://github.com/AoShinRO/brHades/commit/1396b012600db9b0688f3cd3fdb9ac273d525bd0#diff-16a6f317c581ce365a41a9846cf48dc45c8d6ac0256a7c45849e6e1b37100ecdR13025-R13037 Please use this one instead: https://github.com/Jhonvaliense/ROClient_en/blob/main/20231220%2B CLIENT bodystylefix.diff They are functionally almost the same commit. but there are small differences in the pc.cpp file as mentioned by dark elf Thank you dark elf and amm0nition
  9. 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)
  10. 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.
  11. 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
  12. 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?
×
×
  • Create New...