How To Install Dragon Nest Mods
Since i've had quite a lot of people ask me how i have the English patch working in this vid in kdn After the supposed disabling of mods, figured i'd quickly write up an explanation and small guide on what people need to do allow their mods to work properly again after these recent changes. Credit's go to Sieg and Chocorollos for the info that helped make this work around. Firstly, as far as why the mods do not work any more, Eyedentity recently introduced a new software to dn where when you start up the client, it will firstly look at all the.pak files in your clients folder and it will compare their sizes. If it finds that any of the.pak files in there are smaller than 450mb, it will not execute them and instead cause the client to crash ( Normally seen with the 'Shadder' error). To work around this problem, we need to make our mods (.pak files) larger or equal to the 450mb benchmark. There are 2 relative options to do this.
Dragon Nest Mods. 1.- I get black screen and “Invalid Shader Data” after using a mod! This is an error that occurs when the game tries to read a.pak that is. If you are in the colder regions of skyrim, you will see frost dragon nests, if you are in warmer regions, you will see blood or tundra dragons. They will hunt anything near them, including you. You will also see lone dragons perched on mountains and such. Added death dragons Added lava and flame dragons. I added dragon hunters. Home / Gaming / Dragon Nest Costume Renamer + Modding Tools. For the costume mods from the Dragon Nest. Should have in your Dragon Nest install folder are.
1- Use a random file that is greater than 450mb when creating your mod. If for example you are creating a English patch, you'd take the random 450mb file ( that is not of the same type as your mod file that you want to make ( like.txt file and.txt file)) and put it in the same folder as the uistring file. When you compile that English patch, it will be greater than the required 450mb check that dn needs, will not crash your client and will work properly as intended. But this method can be less efficient if you don't know how to make mods and can be a massive pain to share since uploading and downloading at least 450mb worth of data might be annoying to some people (especially if you have bad internet). 2- Increase your mod file's size by filling it with a bunch of NULL's that serve as just extra bytes without altering the contents. This method is much more efficient and 'beginner friendly' compared to the above. Credits go to sieg for the main explanation and i'll be covering this method in detail to try to make sure people can fix their mods without any issues.
Small warning though, you will be using the command prompt and very minor programming to do this so make sure you follow exactly what is explained below to avoid any issues with your computer. Step- 1 - trunc.exe In order to start, we will firstly need to download the trunc.exe function from here: What trunc.exe does is it will extended your file size to be what ever size of bytes you desire by adding in NULL characters ( i.e ' 0' ). These NULL characters just serve to increase your files byte size and will have no effect on your mod file ( similar method is used in Linux with the truncate function or in C with the SetEndOfFile function). Once you have downloaded it, do not try to open it since it will briefly open the command prompt then close again.
In order for it to work, you need to run it from the command prompt ( also known as cmd). If you are using windows 7, go to the start button and in the search function type in cmd and pick the first option ( it will be 'cmd.exe') then open it. If you are using Windows 8 or 8.1, go to the search on the right side of your screen and search cmd. You will see it called 'Command Prompt'. Click it once and it will open. Do not open the cmd as an administrator.
That will not be necessary for this task. If you are using Mac or any other OS.
Ya i can't really help there since i only tested this on windows.sorry. If you've opened the cmd without any issues, your computer screen should look something like this Now we will need to put the trunc.exe file that we just downloaded into the same location that we see is displayed in our command prompt. To do this, simply open up any random file and move to the same location that is displayed in the cmd. I advise using the 'Downloads' file since that will be common to most people and will help you follow what i'm doing more easier. In the above, you will just remove the last part and make it the same as in your cmd.
In my case, i'll delete the Downloads section so that it looks exactly like what's in the cmd before the character. Then press enter. If you did everything correctly so far, you'll be in a file that looks something like this Simply move the trunc.exe file to this file then close the window.
Do not touch anything else. Step- 2 - Changing The File Size First test to make sure you put everything correctly.
In the Cmd right after the symbol, type in 'trunc'. Do not put any spaces between and trunc. If you did that correctly it should look like this in the cmd Where 'Michael' will be your user account name ( such as jenny, bob, ect). Before moving on, we will need to make a temporary file on the desktop to put our changed mods. This way if we make a mistake, we can still fix it in a secluded area. On your Desktop, create a file called 'temp' and paste a copy of the original mod file you plan on using there.
It should look like this: Right click on the mod file inside temp and view it's properties. From here we are going to use the trunc function to change the file in this exact location to the size we want to make it. Since we need at least 450mb, we'll need to set the byte count to to be slightly higher due to internal functions with the.pak file that uses more bytes than we instructed. For now we will simply set the.pak to roughly 500mb just to be safe. If you are worried about space on your computer, don't be. I'll touch on how to change the amount of space that used on your computer by the mod file without reducing the size of the file later.
For now we'll simply use the trunc function to set our mod file to be the desired size. On the cmd, you can either retype trunc or simply press the up key on your keyboard which will retrieve the last things you typed in.
You will need to put 2 things after the word trunc. First thing will be the exact location of your mod file that you want to change and the second thing will be how many bytes you want to make your file change to such that it looks something like this in your cmd: trunc yourfilelocation bytesize The spaces will mean the start of a new parameter. We're going to tell the trunc function to change the mod file to about 500mb. In bytes this is 500 million bytes. We need to put this 500 million bytes as a decimal value such that it is like this in your cmd 500000000 The picture below should hopefully show what i mean When you press enter after typing the above, you should get a message that says it was successful.
Close the properties box of your mod file and open it again. You'll see that your mod file's size has become nearly 500mb ( where some bytes were used for other functions). The image below shows what i mean. If you are not worried about extra memory consumption on your computer.
Then you don't have to worry about the rest of the steps. After this step, your mod will now work with dn when you put it in the same folder as your dnlauncher. This process will trick eyedentity's software to think you are using a 450mb+ file filled with data when you're not and will let your mod work.
If you wish to reduce the size of your mod file or want to share it, keep reading. Step- 3 - Changing the Size on Disk Small warning, these next little bits might be a bit harder to do compared to the above. But if you follow exactly what is instructed below then you should be fine.
Since we don't want to have a giant 450mb+ file clogging up our computer, we need to reduce the files size on our disk without changing the size we want identity software to view of min 450mb. To do this we are going to use the fsutil function and sparese. Fsutil is a default function already on your windows computer so you won't have to download anything. First close the cmd and reopen it so we have a clean start. After the type in fsutil sparse This will show us the 4 sparse commands we can use namely being: 1- queryflag 2- queryrange 3-setflag 4-setrange What sparse is basically gonna do is it will tell the cmd that out of the 500million bytes from our mod file, we only want the computer to use the first X number of those bytes on the disk and not worry about the rest of those bytes. Before you do anything else, make 2-3 more copies of your 450mb mod file in the temp folder!
This is to have a back up of the file incase you make a mistake and be forced to do all the steps all over again. Now we need to setflag of our mod file, meaning we want to tell the sparse command to ignore everything that is does not see as activated and focus on only our specific file ( easiest way i can say it without going indepth about flags lol.) Using the same location of our mod file, we will put this after setflag so that in your cmd. You can double check that the flag is set for our mod by using the queryflag command by pressing up and changing setflag to queryflag. If it says the file is set as sparse, then you can continue.
How To Install Dragon 13
If you did above correctly your cmd will look like this We now need to setflag of our original mod file ( the one which is the small amount of mb and not the 450mb one). Copy that original mod file and paste it into the temp folder and rename it to x ( for easier use). Then do the exact same as above but this time for x.pak so that in the end your cmd should look like this: If you've followed everything so far, good job.
Now what we are going to do is we want to see what the range of x.pak and our 450mb mod file is and set the 450mb mod file to only use the same amount of data as our x.pak on our disk. To do this first we need to see what the range is of each of those 2 files. Press up to scroll back to the mod files location and change setflag ( or queryflag if that's what it is) to queryrange then press enter. Do this again for the x.pak file and it should end up looking like this in the cmd. Important note: the Length is in hexadecimal format. Do not worry much about what that means but what i want you to make sure is that the very last number of both the x.pak is NOT a letter ( meaning not one of the following letters being A B C D E F).
When i say last number i mean for example in the x.pak the underlined number below Offset: 0x0 Length: 0x2edae 3 If your last number is a letter as stated above, i want you to retype that value ( 0x2edae3 for example) into this link: And convert it from hex to decimal before continuating. Keep that window open. If your last number of the x.pak is not a letter, feel free to continue reading. The next step is for us to set the range of data used on our our 450mb file to be the same as the x.pak. This format will be like follows: fsutil sparse setrange YourFileLocation OffsetValue LengthValue After your file location, you will retype the length of x.pak first but we will need to increase the last number by 1.
In my case since my last number is 3, i will increase that number to 4. If your last number is a 9, change that 9 to the letter A ( lower case version) ( since A is the hexadeciaml value of 10). After typing the x.pak range first put a space then retype the range of the 450mb mod file ( you do not need to change it). In the end you need to have something that looks like this: If you had a letter ( either A B C D E F) at the first red line, i want you take that decimal, increase it by 1 and then put it into this link Then convert the number that was +1'd to hex.
So if after converting to decimal you got the number 123456, you will increase than number by 1 to become 123457 and then put this new number in the converter above. When you have that new hex value, you will put a 0x at the start and type that into the spot where the second green line is in the picture. If for example i take my 123457 example and convert it to hex, it becomes 1E241. I will then type right where the green line is 0x1E241. After you finish that, press enter and then reopen the 450mb mod file's properties. If you did everything above correctly the size on disk of the 450mb mod will become very small such as in this picture. Now when you put this mod file into your clients folder, it will trick eyedentitys software and make it see it as a legit file and will run your mod without any issues.
If your size on disk is either 64kbs, 128kbs or 0 bytes ( or anything that is less than 1 million bytes), that means you made a mistake when setting the range or forgot to add a number/lettter and caused the file to become corrupt. Delete that file and use one of the other copies. Change one of the copies names and to the oringal name ( so for example instead of Resource01-English -copy make it Resource01-English) then repeat all of step 3 again. If you wish to share your mod, you will now instead of directly uploading it to a site have to compress it first then upload it.
The compresset will ignore all the extra NULL bytes and make the final file the same size as the original mod ( so it will pretty much upload a 500mb file as a 3mb file instead of a direct 500mb file). However when the person who downloads your 3mb mod extracts it, they will have 500mb version on their disk size instead of the lowered value since their sparse command is based on each individual machine and not on the file itself. But that much is not a big issue.
Simply link them to this thread and tell them to read step 3 if they want to reduce the file size. For now i'll leave a copy of the English patch that will work after the changes for kdn and cdn as well as a fixed chat filter for any one who plays in Chinese.
Note, when you extract the files, their size on disk will be 500ish mb. If you want to reduce this value and save some room on your disk follow step 3's instructions above. Remember to remove the mod before updating the client to avoid potential bugs.
Also as far as kdn's English patch, it's using the same uistring as the cdn's so some items ( like altheum) will have square boxes on them because i had the chinise versions of those items for an easier time to search in the market place. 1- CDN English Patch 2- Chat Filter mod 3- KDN English Patch i do not plan on updating this since certain English guilds in kdn have caused unnecessary drama with me in the past and i do not wish to help those guilds. If you would like me to send you a copy of the English patch for kdn that i used in the video above, send me a private message and i'll give you the link.
The post was edited by at Sep 26, 2014 12:50 am Signature. Reply Claudiuz Looks like you're running in windows xp.
Don't worry much about that format. Windows xp's version of sparse is a bit different as that it displays the values in decimal format ( normal numbers) instead of hexadecimal format( the one with the letters). The first number there which is 0 is the offset which is the same value as 0x0 in my example. The 2nd number there which is 500000000 Is the length which is the same value as 0x1dcd6500 in my example.
All you have to do is the same as above but when you set your range, both numbers will be in decimal format instead of hexadecimal format ( so after the location, you'd put the decimal length +1 of x.pak first then the decimal length of your 500mb mod file second ( which would be the 500 million value)) As far as the english patch goes, send me a private message on mmosite and i'll send you the link. Might want to remove your email cause not really the safest thing to put on these kind of public websites. quoteQuote: Originally Posted by url=at Oct 16, 2014 6:05 pm bReply url=iri4i/i/b br brWhen you do isparse setrange,/i make sure that you add +1 to size1.
How To Install Nest Camera
url=tryed that way also i didnt saw it when i make the pics but anyway still when i move the mods they are going to the 476mbs 175.203 Oct 28, 2014 2:10 am.
A place to discuss and share Dragon Nest Mods. Rules. No hacks/cheats. Anything that directly alters game mechanics is forbidden. No NSFW mods. NSFW mods are allowed as long as it's marked as such.
How To Install Mods On Dragon Nest
No Viruses or other malware. No personal information. (name, address, etc.). No gold/NX/CC trading. NEW Tag any mod submissions you make. This makes it easier to categorize and search.
We are not responsible if you somehow end up breaking your game or getting banned for mod usage. Use them responsibly. As always remember to remove your mods from the DragonNest folder when updating. Related Links.