Jump to content

Craven

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Craven's Achievements

Poring

Poring (1/15)

2

Reputation

  1. Figured out the issue, kind of a stupid mistake on my part if you ask me. NEMO Forgot to add .exe behind the Output Patched file's name, i.e.: I wrote /Ragnarok instead of /Ragnarok.exe Apparently I've been copying a two days old client, all the while I was thinking it was the latest patched one.. ? Thanks for the help @LuLu!
  2. You could shoot me if I'm doing something wrong here, but you're showing me exactly what I have, although I'm not currently using lub. (And yes, I've tried changing it from lua to lub, but it simply won't translate) Do you mind telling me what your NEMO version is and which patches you've used?
  3. Alright, I got one step further now with the simple fix of re-ordering the DATA.INI file. The user interface is now completely English, with the exception for the 'Help' menu, that one is still experiencing overlapping gibberish. The items, however, are still using the trash language, here's what I already tried out: Client Turned Load Custom lua file instead of iteminfo*.lub off -> nope. Changed Load Custom lua file instead of iteminfo*.lub value to itemInfo_true_V3.lua (appropriate for client 20180620) -> nope. Turned Use Plain Text Descriptions on -> nope. Tried step 2 + 3 in conjunction -> nope. Re-did step 1 and then renamed itemInfo_true_V3.lua to itemInfo.lub -> nope. Lua Checked every single (translated) lua file for faulty characters and/or gibberish, none to be found unless encoding the .lua file to ANSI. Tried changing itemInfo_true_V3.lua's encoding from UTF-8 to ANSI, which for example turns "나이프" (dagger) into "나ì´í”„" instead of the way it looks in-game: ÀÌÇÁ. (see OP) data.grf Found the itemInfo.lub inside data.grf/data/LuaFiles514/Lua Files/datainfo and replaced it with the translated itemInfo.lub from ROenglishRE -> nope. Note: oddly enough, there are 3 folders inside data/LuaFiles514/Lua Files called datainfo, DataInfo and Datainfo. For some reason, the System folder is being read, just not correctly whatsoever. It also contains the English information for the tipbox (help menu) and is equally gibberish in-game. Formatting breaks the moment the client tries to pull the item names, descriptions as well as the tipbox from the .lub and .lua files. ? I've also checked my System Locale just in case my system is trying to look up information the wrong way, but that part seems to be in order.
  4. I'm not entirely sure what you meant by "try packing it all into GRF.", but this is what I've tried: Checked itemInfo_true_V5.lua (the one I'm using in the NEMO patch) It doesn't show gibberish. (see below) Checked itemInfo.lub and.. yeah: This could simply be how the lub files look like in terms of their format, but what do I know? lol Packed the data folder from the translation project into english.grf. It shows À¯ÀúÀÎÅÍÆäÀ̽º as the folder with all the translated textures in it. Added an extra entry in the DATA.INI file to load in the english.grf: [Data] 1=rdata.grf 2=data.grf 3=english.grf I'm not sure if the order here matters, but I'd assume the last one will overwrite anything from the previous GRF. Though if that's the case, it still didn't work, sadly. Furthermore, I've never tried extracting the official data.grf this kRO client came with, since the wiki never told me to do so. But isn't it logically correct to simply extract data.grf, overwrite the old files with zackdreaver's translated files and then re-pack the whole thing into a new GRF file? Is that a thing or..? ?
  5. Thought I could handle it myself, albeit with a ton of headaches, but alas.. I'm at a dead end here and decide to create an account after all. I've been trying to get the client translated for about 2 days now with the use of zackdreaver's ROenglishRO translation files, in combination with the basic translation patch as found in NEMO. I understand a couple of people have had similar issues as I, though applying the solutions they were given, they sadly didn't work out for me. Performed 'Download, Update & Extraction' Steps Downloaded the 2017-07-05 kRO client from https://rathena.org/board/topic/102572-kro-full-client-last-update-2017-07-05/ Extracted the kRO client into a generic Ragnarok Online folder. Downloaded the Ai4rei's RO Patcher Lite from https://rathena.org/board/topic/62758-ro-patcher-lite-v2424806-last-updated-20191229/ Used RO Patcher Lite to update the client, which ended somewhere around 2018-06. Downloaded the ROenglishRO translation files from https://github.com/zackdreaver/ROenglishRE Extracted the data & System files into the main folder of the client. Performed Client Patching Steps Downloaded the 2018-06-20eRagexeRO client from https://rathena.org/board/topic/117168-packetver-20180620-client-release-2018-06-20eragexere/ Note: my server was compiled using that clients' packetver, for ease of use. Downloaded the latest version of NEMO. Applied a bunch of patches (see spoiler below) with the use of http://nemo.herc.ws/clients/2018-06-20eRagexeRE/ to figure out what works and what doesn't. Patch 65 Load Custom lua file instead of iteminfo*.lub (Recommended) was pointed to itemInfo_true_V5.lua in the System folder. Patch 35 Read Data Folder First is used temporarily until I get the translation right and can pack it all into GRF. (s)clientinfo.xml Result A mix of English, Korean and utter gibberish. (The help menu is even getting overlapped, holy..) However.. NPCs and NPCs have their name written in perfect English; NPC dialogues are in English; Some menus are in English as well, i.e.: achievements (+ their descriptions), status, equip (excluding equipped item names), skill tree (+ skill descriptions), world map (+ navigation and mob info) and the options menu itself (ESC -> 게임 설정). I've tried swapping up itemInfo_true_V5.lua with one the other itemInfo lua files using the custom lua patch, but to no avail. The gibberish as seen on the screenshot reminds me of an encoding format issue in the event you accidentally change that in a TXT file. If anyone can shed some light on what could be the issue here, I'd gladly hear it since it's the last step for me to get it all working flawlessly-ish.
×
×
  • Create New...