Jump to content

Tokei

Members
  • Posts

    660
  • Joined

  • Last visited

  • Days Won

    89

Everything posted by Tokei

  1. I've finally been able to reproduce your issue (thank you for Ai4rei's comment, it made this quicker). You added a file to the very first node of the project and this is not supposed to be allowed. I'll make this clearer in the next release, but meanwhile, you should be adding files to the "root" node for RGZ and Thor files. The root node represents your RO directory where files will be copied. On a side note, saving your RGZ file again will fix your previous issues.
  2. The compressed GRF is fine, it's the decompression in 1.6.6 that has issues. Please update to 1.6.7 and you'll be fine .
  3. Fixed in 1.6.6 (at least from my tests, if the error still eccurs for you, send me your client with the DLL generated). The new DLL will also no longer disable itself if it meets "unexpected conditions". Fixed the conversion and saving issues with the RGZ file format in 1.6.6. GRF Editor didn't allow GRFs to be added to a RGZ file (or any other format actually); its defaut behavior is to open the file instead. This was made on purpose because you shouldn't be packing a GRF inside a RGZ file; it's a double compression and it should be avoided. That being said, I've removed the restriction and you can do it now. If you're planning to make a Thor patch, I would recommend the following method instead (you will need the version 1.6.6) : Open your GRF with GRF Editor Go in File > Save as... > Rename it with the .thor extension. Click on the root node (or any other node), and select the "Container options" tab (on the right panel). Use "Merge into GRF" for the patching mode and type in the output GRF name. Save your Thor patch. Once you patch the file with Thor Patcher, it will either create or merge the GRF for you. Hope this helps!
  4. Tokei

    Ghost Helm?

    This helm can be found in 2014-8-5Costama_Egg25.gpf (attached the file). It's named ³²_À§½ºÆÛÅçÇÞ 2014-8-5Costama_Egg25.gpf
  5. Couldn't you just download jRO's GRF with a patcher (RSU)? Anyway, here they are (the patches are attached to this post) : For other jRO patches, you could just get the files from the links below. Patch list : http://httppatch.ragnarokonline.jp/patch30/patchbbs/patch2.txt Patches : ftp://ftppatch.ragnarokonline.jp/pub/dl-gunghoftp/roftp/ ³²_¹ý»ç°ü ³²_¹Ù´ÏÇìµåµå·¹½º ³²_ÇǸ°Æ®½ºÄ«ÇÁ Can be found in 2014-3-4Costama_Egg20.gpf ³²_Áúdz½Å·Ú ³²_´õºíº»Ç︧ ³²_»çÀ̱׷é2 Can be found in 2014-2-4Costama_Egg19.gpf ³²_±â¿øÀǺ¢²É ³²_ÃÊ¿øÀǹٶ÷ ³²_ÆĶõÀå¹ÌÀå½Ä Can be found in 2014-4-1Costama_Egg21.gpf 2014-3-4Costama_Egg20.gpf 2014-2-4Costama_Egg19.gpf 2014-4-1Costama_Egg21.gpf
  6. The latest build wasn't packed properly, simply redownload GRF Editor (1.6.5.9+) and it should be extracting as expected.
  7. Tokei

    WorldMap

    Simply edit mappostable.txt in the data folder. Change the array size from "12@" to "13@" and add the locations at the end of the file with this format : 12#map_name.rsw#x1#y1#x2#y2 Example : 12#abyss_02.rsw#301#0#500#100# The coordinates represent the top left point (x1, y1) and the bottom right point (x2, y2).
  8. Both of these are empty files, with 0 byte size. Try to extract them again (it's possible they're also simply encrypted, which makes their content impossible to extract).
  9. 47 bytes for a Thor file is too small as you probably know already. Are you... sure you selected the folder containg the files in it? Please check again, it doesn't make much sense to be that small! As for the encoding, it has no effect on the content on a file, these are treated as raw bytes no matter what you choose. When saving a GRF/Thor file, the paths need to be converted to ASCII (this is fixed and part of the structure, it cannot be changed). When you add files from Windows Explorer, the paths could be anything : Unicode, UTF-16, etc. Thor needs to know this information because it won't properly convert the paths otherwise. In your case, all the paths are ASCII characters, so you should use that.
  10. Heya, Create an empty project in GRF Editor, drop your data folder (with the files for the patch - C:\Users\user\Desktop\RAGNAROK\Patching\data) and then extract it. Doing so will fix any encoding issues with your path names. Try to make a Thor patch with this new folder instead and it should be working fine (use ASCII in thor). As for why you're having issues... empty folders are never shown in GRF Editor. This will happen if the file paths inside the GRF aren't encoded properly (they contain unknown characters). When you make a patch with Thor, you have to make sure ALL the files use the same encoding. If you see "À¯ÀúÀÎÅÍÆäÀ̽º" in windows explorer, you should choose ASCII and if you see "유저인터페이스", you should choose Unicode. Since you tried both encoding and none worked, you probably have paths with mixed encodings and this will not work =/. Hope this helps!
  11. I think you're looking for data\texture\À¯ÀúÀÎÅÍÆäÀ̽º\basic_interface\equipwin_costume.bmp The one in your screenshot is a special one : data\texture\À¯ÀúÀÎÅÍÆäÀ̽º\basic_interface\equipwin_special.bmp
  12. There you go : jRO-Ragray patch file : http://httppatch.ragnarokonline.jp/patch30/patchbbs/patch2.txt jRO-Ragray patches : ftp://ftppatch.ragnarokonline.jp/pub/dl-gunghoftp/roftp/ twRO-Ragray patch file : http://ronotice.gameflier.com/patch02/patch2.txt twRO-Ragray patches : ftp://ropatch.gameflier.com/Patch/
  13. Check the item 30189, "identifiedDisplayName" is missing (there's also a line that shouldn't be there).
  14. Hmmm, I think you switched the before and after files, but yeah, the error is most likely on the line 194677, for the item 30484. The "identifiedDescriptionName" variable identifier is missing, as shown below. [30484] = { unidentifiedDisplayName = "Accessory", unidentifiedResourceName = "Green_Large_Hibiscus", unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier].", }, identifiedDisplayName = "Green Large Hibiscus", identifiedResourceName = "Green_Large_Hibiscus", identifiedDescriptionName = { -- <- This line is missing "^8B0000BurningRO Custom Item^000000", "^008000Alle Statuswerte +5^000000", "Class :^777777 Headgear^000000", "Defense :^777777 1^000000", "Equipped on :^777777 Upper^000000", "Weight :^777777 10^000000", "Required Level :^777777 1^000000", "Applicable Job :^777777 Every Job Except Novice^000000", }, slotCount = 1, ClassNum = 2357 },
  15. See the attached file. You can use actOR with the magnifier.lua script (edit the 'mag' value) if you need to resize other sprites. ae_moltres.rar
  16. Sure, you could use the following script : for AID = 0, GetNumAct() - 1 do for FID = 0, GetNumFrame(AID) - 1 do for PID = 0, GetNumPat(AID, FID) - 1 do SetA(AID, FID, PID, 0x88); SetB(AID, FID, PID, 0x99); SetG(AID, FID, PID, 0x55); SetR(AID, FID, PID, 0xFF); end; end; end; Simply go in Script(S) > Edit... > copy and paste the above code and click on Run.
  17. Not sure where's the issue exactly, so... make sure everything down there is correct. 1. The data folder must be selected in the input. If any of your filenames/directories looks like "À¯ÀúÀÎÅÍÆäÀ̽º", then select Ascii. If you see "유저인터페이스" instead, then you must select Unicode. Also make sure that the target GRF is the one you actually want to patch. 2. The directory option is selected and you selected the folder containing your .txt files. These do not contain Korean characters, so select Ascii instead. When you click on Generate, select the "/data" option. If everything goes right, this should work!
  18. The client Kido made for you was using the "txt" files (idnum2itemdisplaynametable.txt, idnum2itemdesctable.txt, etc) to define your custom items. This 2013 client uses itemInfo.lua/itemInfo.lub instead. I'd suggest you to read http://rathena.org/wiki/Custom_Items
  19. Tokei

    GRF Editor

    About the encoding, the problem comes from when you save the text file and you have the display encoding (through the setting page) set to Korean. The lub decompiler always uses the ANSI encoding instead of using the current display encoding, which causes issues when saving afterwards. This is a bug on my end though and it is now fixed in 1.6.5.1 (can be obtained via the mediafire link in the description). As for the 'errors' with the values, I'm not really sure what to tell you. I've checked the lub file you've provided and I indeed got the same numbers as you did. The issue doesn't come from the decompiler though, the process is quite simple : ​00 00 00 00 06 82 4c 41 > Bytes concerned, in little endian. Converted to a floating point number > 3736588.0 That's it, the decompiler's job is done at this point. If you convert this value back to an integer and apply a mask of 0xffff, you will get the 'value intended' (which is apparently a 'short'/int16). As you can guess, I can't fix this problem as there is technically no issue =/. I'm gonna guess that the client cuts off the last bytes, treat the value as a short integer and that's why it's working properly.
  20. Tokei

    GRF Editor

    Heya, The entire document uses the Windows-1252 encoding (which is the most common ANSI codepage) and as far as I can tell, the characters shown by the decompiler are indeed from the ANSI codepage. So I don't see any bug with the 5th column, you'd have to elaborate on that (send me a message instead, I will respond to you faster)! Now the 4th column is definitely suspicious; I've decompiled a few versions of navi_mob_krask.lub and I'm getting the same lines as your second sample (except for the 5th column not being translated in english) : { "abbey01", 17104, 300, 1036, "±¸¿ï", "GHOUL", 61, 3211521 }, { "abbey01", 17105, 300, 1865, "´©´õ±â Á»ºñ", "RAGGED_ZOMBIE", 123, 4522241 }, { "abbey01", 17106, 300, 1867, "¹ê½Ã", "BANSHEE", 130, 3080454 }, { "abbey01", 17107, 300, 1864, "Á»ºñ ½½·¯ÅÍ", "ZOMBIE_SLAUGHTER", 124, 4522241 }, I can't reproduce your issue and I would actually need more info to fix this. If you could, please send me the lub file you've used . Also, just as a side note, if you need an urgent fix, you could go in the "Decompiler" tab and uncheck "Use GRF Editor Decompiler". Then click "File info" again and it will use another decompiler which is 'usually' more stable. And thanks for the bug report, I appreciate it!
  21. Version 1.0.2

    311 downloads

    Hey everyone, TkHashTool is a software primarily aimed to help users resolve issues with their client files. It does so by taking a 'snapshot' of the files in the Ragnarok folder and creates a scan report. This scan can then be compared with a working version of the client to identify the problems. This is the first released version, so if you find bugs don't hesitate to go forward and tell me. Your comments below (in the support forum) are greatly appreciated. This tool was a request someone [will put the name here if the person doesn't mind] suggested to me and I liked the idea. I thought I'd upload it before I forget about it . How to install There is no installation required. Simply run the executable within the zip file. End-user requirements The software was developed using .NET 3.5 SP1 Client Profile. This framework is the same one used by GRF Editor, and it's compatible with Windows XP, Windows Vista, Windows 7, WIndows 8 and later versions. However, it's NOT installed by default on Windows XP and Windows Vista. To solve this issue, I've made a wrapper in .NET 2.0 which is already installed on all common Windows versions. The wrapper checks if the framework is installed and prompts the user to download it (sends you to microsoft's webpage), otherwise it starts the application normally. It works with UAC, but applying patches may require the application to be run with admin privileges (the user will be prompted if that's the case). General information The TkPath syntax is used everywhere in the software : [file name on the hard drive]?[relative path within the container]. Containers are either .grf, .gpf or .rgz files. Examples : rdata.grf?data\texture\backside.bmp data\texture\backside.bmp Regular expressions are not available in the paths, but wildcards (*) are allowed. You can use paths such as *.gnd and *.grf?*.txt Files generated are saved in the application data folder. They are usually followed by a 'bunch of numbers', which simply represent the date : year-month-day-hour-minute-second. How to use it Start the application with TkHashTool.exe and you should have the 'Generate hash tool' tab already selected. The available options are rather straightforward and there are tool tips if you need more information on them. The exclusion list contains files that will be ignored (excluded files are set before anything else). For example, if you set "data\afile.txt" to scan and you put *.txt in the exclusion list, then the file won't be scanned. If you want to ignore all the map files, you could add : *.rsw, *.gnd, *.gat. Let's say you want to hash only the lua and lub files, you can select "Hash from specific files or folders" and use : *.lua, *.lub, *.grf?*.lua, *.grf?*.lub Using 'Files can be hashed more than once' scans files even if they've already been processed elsewhere (from another GRF or from the data folder). This is not always a good option because the patch generator cannot know what files to replace afterwards (since it doesn't know in what order the GRFs are being loaded). It will actually replace all files it finds instead. The third mode, 'Hash by using the configuration in data.ini' is similar to the second mode, except that files entered in the text box below will be treated as data.ini files. If you want to scan the same way the client reads the files, you could put : data, System, AI, DATA.INI. Click on the gear or on 'Generate client hash tool' to generate a client version. The config file alongside the executable is not necessary for the application to run. It simply tells the program to use .NET 4.0 if it's available. Reading HashObject A HashObject is simply a scan (.tko). All paths are saved in Unicode and casing is ignored. The scan contains information about all the paths hashed, the head directory from which the software has been launched and the settings used for the search. The partial option indicates wheter or not the scan has been completed entirely. These files are also heavily compressed. Comparing objects Simply open the 'Compare HashObjects' tab, drop your master .tko file in the first text box and the user one in the second. You can view the settings used for each one of them by using the 'View file headers...' option. As for the errors, just chek the tool tip for more information. Here's a list of the errors it can detect : HoMissingFile This file is missing from the user directory.HoHashMatch Both the user and the master files have the same hash.HoDuplicateFile This file has been found twice in the GRF (lower casing issue?).HoGenericError This file couldn't be decompressed or there was an unknown error while reading the file. Or the file size is over the size limit.HoHashDifferent The user and master files are different.HoExtraFile This file doesn't appear in the master object, only the user has it.HoPathOverride The user data path overrides the file in the master files. Scanning content Scanning the files is pretty straightforward, you can cancel the scan at any time by using the X button on the progress bar. Files larger than 25 MB will not be scanned (this doesn't include containers). They will appear in the scan with the HoGenericError code. You can change the current working directory if you're using the master version; this option lets you change the root directory of the scan. Patch Use this tab to apply a patch file (.tkp). These are applied to the current directory where the software has been launched from. This operation should be really quick as it doesn't repack the GRFs at all. It uses the quick merge option which will fragment the GRF, but if it gets too fragmented, then it'll get packed automatically.
    Free
  22. Hmm, if you did everything up there, then I really don't have any easy solutions for you. This doesn't seem to be a problem related to GRF Editor anymore; UAC is the only conflict the software has and since the last version it shouldn't even be a problem =/. I've googled a bit and here goes : And... As always with UAC, you will have to reboot for the privileges to fully apply. The last quote seems to have fixed the issues in most cases.
  23. The drag and drop features are always enabled. Update to the latest version and see if that resolved your issue (there has been fixes regarding drag and drop). If that didn't help, here are some steps that you can try : - Try to run the application without admin privileges (right-click on the desktop shortcut > Properties > Compabitlity tab > Privilege Level at the bottom, make sure "Run this program as an administrator" is not checked). - Try to run the application with admin privileges (right-click > Run as administrator). One of the two options above should have done the trick (normally the first one), if not... - Move the executable files to another folder, such as "C:\Grf"; the files are usually located in "C:\Program Files (x86)\GRF Editor\". Try to run it again. - Disable UAC entirely and restart your computer (this is a last resort solution, but it will fix all drag and drop issues). Control Panel > User Accounts and Family Safety > User Accounts > Change User Account Control settings > Set it to the minimum and restart. The reason for this problem comes from UAC which restricts drag and drop features between processes with different privileges. Windows Explorer is normally started without admin privileges even if you're an admin user and that's rather annoying. Hopefully though, your issue will be gone with the first two options!
  24. Yes, I always wondered why that wasn't included in the features of Grf Editor. I hope it is added in the future. It will save a lot of time! Thanks for the suggestion! Here's a quick update on the new features. Search feature Includes common options you'd expect from a search tool. Shortcuts Ctrl-F : Brings up the search panel (if a word is selected, it will be the default search) Ctrl-H : Brings up the replace panel Enter/F3 : Select the next word in the search (or replace the next word) Shift-Enter/Shift-F3 : Select the previous word in the search Ctrl-Shit-Down : Select the next word which is highlighted Ctrl-Shit-Up : Select the previous word which is highlighted Esc : Closes the search or replace panels and clear the searches. Shell integration You can associate shell files with GRF Editor via Tools > Settings > Shell integration > Context menus. If you were using the previous versions of this context menu, I'd strongly suggest you to use "Remove all extensions" to remove any previous registry entries. The shell integration offers the options shown on the image below; if you'd like something in particular don't hesitate to ask. ** For XP users, the tool should be installed properly but you might experience "graphic" issues. This feature was developped for Windows Vista onwards. Resource indexer This feature allows you to locate the usage of a resource within your GRF.
  25. Tokei

    GRF Editor

    Yep, the application's been written in C#!
×
×
  • Create New...