-
Posts
696 -
Joined
-
Last visited
-
Days Won
103
Content Type
Profiles
Forums
Downloads
Jobs Available
Server Database
Third-Party Services
Top Guides
Store
Crowdfunding
Everything posted by Tokei
-
The client's size is a registry setting, I believe normal setups have trouble setting the values because of privilege issues. Have you tried using OpenSetup by Ai4rei? It should set your settings properly, or at the very least tell you that there was an issue while it was trying to do so. If nothing else works, just set the values yourself, they can be found in : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Gravity Soft\Ragnarok\ with the keys HEIGHT and WIDTH. (unless you diffed your client to read the HKCU hive instead of the HKLM).
-
What you're looking for would require modifying the client and adding a protection with third party softwares (such as Harmony, Hackshield, etc). The encryption feature can only protect your data (from being stolen/read). You can prevent players from modifying a GRF, that is actually possible (but this method is not currently available in GRF Editor). If you encrypt the GRF's file table, the players won't be able to see anything within the GRF and it will crash almost any application trying to read/edit it. The big issue with this is that you won't be able to patch that GRF. Also, this doesn't prevent players from putting their GRFs before yours in the priority list (or in your data folder) unless this list is protected. The encrypted GRFs do not actually contain any information regarding the key used either. So knowing wheter or not a patch match an encryption key would not be possible. It is actually more trouble for you than what you'd gain in the long run. Plus someone would probably find a way to bypass it one way or another.
-
It should be showing all the content in the latest version 1.6.7.5 (mediafire link http://www.mediafire.com/download/aflylbhblrzpz0h ). The reason behind this bug is that there are many edge cases that need to be treated differently and carefully. If this happen for another file and you don't want to wait for a fix, you can always use the 'default' decompilers. Go in the "Decompiler" tab and uncheck "Use GRF Editor Decompiler". It will use LuaDec50.exe or LuaDec51.exe instead (using these also have their cons though!).
-
This is a known issue with ActOR2. As far as I know, the only way to change the sound ID is to use a lua script with the "SetSoundNo(ActionId, FrameId, SoundId)" method. Example, to change all the frames with the first sound in your sound list, you could use : for ActionId = 0, GetNumAct() - 1 do for FrameId = 0, GetNumFrame(ActionId) - 1 do for PID = 0, GetNumPat(ActionId, FrameId) - 1 do SetSoundNo(ActionId, FrameId, 0); end end end Hope this helps!
-
Assuming it's not compiled, you can edit it with any text editor. You'll probably want to use Notepad++ for it.
-
Redownload GRF Editor from the mediafire link : http://www.mediafire.com/download/aflylbhblrzpz0h (1.6.7.4). You'll be able to generate your cps.dll file and your GRF files. As for the error you get on the client, this will happen if you renamed the executable name (this is not allowed).
-
Your question is confusing me, I'm not sure what you're trying to do. Thor patcher doesn't offer a built-in encryption system, but it is possible to make encrypted patches for a protected GRF (or unprotected GRF, doesn't matter). There are multiple ways to achieve that : Rgz method Make a RGZ file with your encrypted GRF inside. This is quite easy to do, but it's not an optimal solution if you're planning to do multiple patches on your GRF. Grf in patch list method This is not very well known, but if you put a GRF file name in your patch list, Thor Patcher will merge the file with your default GRF. Example : ... 44 patch2014-09-07.thor 45 patch2014-09-08_encrypted.grf ... So you just need to make a new GRF, put your files to patch in it and encypt it using SecureGRF (I guess that's what you're using). GRF Editor method The method allows you to change the target GRF and save the patch as a Thor file. You will need the most recent version of GRF Editor for that. Encrypt your GRF with SecureGRF. Open the encrypted GRF with GRF Editor. Go in File > Save as... > Change the extension for .thor and save it. Click on the "Container options" tab from the right panel, and there you have all the same settings Thor Maker offers. As for data.ini, I'm... confused. What is your goal? This file is normally used to allow multiple GRFs to be read by your client, assuming you've diffed your client for that. Simply edit an existing one or create it from scratch yourself from a text file (rename it to .ini afterwards). Copy and paste the content in the file from the wiki page you've linked.
-
All resources related to Violet Fear are in the rar file attached below. Have fun! data.rar
-
There is already a script made for that, the file is named "magnifier.lua". Edit the file and change the "mag" value to your needs (mag = 2 means 200%).
-
Edit the line below in db/pre-re/skill_cast_db.txt : The 5th parameter (5000:10000:15000...) is the duration of the skill from level 1 to 10, in milliseconds.
-
I've put the last version I've used of GRFCrush as an attached file. If Curiosity wants me to remove the link or if he reuploads his tool, I'll remove it. GRFCrush.rar
-
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.
-
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 .
-
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!
-
This helm can be found in 2014-8-5Costama_Egg25.gpf (attached the file). It's named ³²_À§½ºÆÛÅçÇÞ 2014-8-5Costama_Egg25.gpf
-
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
-
The latest build wasn't packed properly, simply redownload GRF Editor (1.6.5.9+) and it should be extracting as expected.
-
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).
-
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).
-
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.
-
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!
-
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
-
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/
-
Check the item 30189, "identifiedDisplayName" is missing (there's also a line that shouldn't be there).
-
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 },