Leaderboard

Hello everyone, Hello Rathena Community. Recently, maps nif_dun01 and nif_dun02 have been added to the KRO. and I was particularly in love with them, because I really like the Nifheim theme... When trying to add the these maps, I always encounter a Models error and right after this i receive one Gravity Error. so I went to find the solution to this problem and try to solve it in all ways ... I encountered the following problem: all Model files that are used on these maps have the RSM2 extension... While doing some research... I found that these files are only read by Clients 2020 +.. My server is 2019/09 and I definitely can't transfer my server to a client 2020+, due to the extreme amount of errors in the process... Anyone, could tell me if there is a way to make these RSW2 files become RSW1 and work on conventional clients? Note: Browedit cannot read these maps due to the same reason ... The only way to open these maps was: remove all the Models in Grf Tool - Flat Map... -> The real Map on KRO -> The Map Preview om GRF Editor-> After >days< triyng: ------------------------------------------------------------------------------------------------------------------------------------------------------------- with the most recents files with KRO - November 2020 - like i say above.. i'm try to implemented the maps NIF_DUN01 and NIF_DUN02. Link: Map in KRO https://www.youtube.com/watch?v=ipiYKyPtKf8 I will tell step by step what I did to try to make it work.. FIRST STEP: to try to make it work I did the standard procedure.. (I use Hercules) the MCHACHE files was generated ... and then placed in their respective folder \hercules\maps\pre-re or re\ after... the maps was add on \conf\map\maps.conf after.. the maps was add on \Hercules\db\map_index when tried open in game the >CLIENT CRASH<. SECOND STEP: was identified above ... the maps use RSM2 files and this maybe cause the client crash.. after this i tried to convert all RSM2 files to RSM files.. and i did it.. FILES IN RDATA WITH RSM2 EXTENSION-> THE SAME FILES IN PERSONAL GRF CONVERTED TO RSM FILES -> After this convert process i use the HEXADECIMAL EDITOR.. With him is possible to change the nif_dun01 or 02.RSW file without damaging it. The hard job is: found all rsm2 files inside the codes and trade to rsm extension. Changing the CODES [ 72 73 6D 32] to [ 72 73 6D 00] to AFTER finish this... i put the RSW files inside GRF and checked if everything was normal. The Grf Read perfectly all files: Files with RSM2 extension -> Files with converted RSM files. work's perfectly-> AFTER doing all this steps i made one personal GRF. contains: - The maps NIF_DUN01 and NIF_DUN02 edited on Hexadecimal Editor (rsm2 -> rsm) - All models that are used by the New Nif maps... converted (rsm2 -> rsm) - All textures used in the process. - Link to Download GRF: https://www.4shared.com/file/mIGedibHea/nifgrf.html This GRF was cited first inside the DATA.INI After ALL this steps when tried to open MAPS in game the >CLIENT CRASH< ALL THESE SAME STEPS WAS MADE BEFORE WITH MAP "ba_lost" which uses RSM2 files to.... and >WORKED< FINAL CONCLUSION: I came to the conclusion that these MAPS are not yet released to us (Western) as of the current November 2020 date. My client as mentioned in the post above is 2019-06-26. And I tried it with clients after July 2020, (When these maps arrived at KRO), and it didn't work to. If anyone else wants to try or can help me with them I would be very grateful. Basically everything I tried was cited in this post.

MemoryRO FluxCP template with extra module Custom Homepage Editor Custom Server Info Editor Custom Download Editor Blog Module Manual Event Module Module Redeem Code MVP Rank by Saders1992 if u have the script PVPRank by Annieruru Free Installation

I personally would start with pre-renewal, just check out latest rAthena and enable PRERE, compile. For client you can always use the latest client for which there is a diffable executable (and usually can just get the latest data.grf from kRO). I would recommend just starting with the most recent available because diffing the executable is the hardest and most annoying part of setting up a server, so you only want to do it once and not later again if you want even newer content. Tools like WARP already offer quite some modes and tricks (e.g. to remove the doram selection screen). The advantage of starting with PRERE is that you already have all the mechanics work like PRERE and you could already just launch your server in alpha mode. Then slowly start adding renewal content. Since this is a long process that can take years, it's better to do it slowly one after another. If you started with Renewal, you'd have a long phase were you wouldn't even have a working version, so you'll probably lose motivation before you're even down reverting all renewal mechanics back to pre-re. So yeah, my recommendation is to start with pre-renewal. I think on rAthena we already did it so that even in PRERE all the renewal maps are available and you can warp to them with the warp atcommand. Now the work starts. The best thing is probably to start small. Just pick a single renewal map you want to make accessible. You will need to find add the warps from and to the location. You can take them from existing renewal NPC files, but don't blindly copy the complete file because you'll add warps to locations you don't support then. I guess copying or loading the file but commenting out the warps you don't want yet is the best way to go about it. Same strategy should work with NPCs on that map, but might want to remove the scripts for all NPCs you don't want yet (if you keep the file location as it is and then link to it from the pre-re scripts_main file you can easily restore the deleted NPCs just using TortoiseGit Diff or a similar tool). Now you want to add all the database stuff needed for that map: Items, monsters, etc. These you can't simply copy over from renewal as the stats there have a different meaning, you will need to rebalance the items. I don't think automatically converting items in any form will result in a balanced item. You'd need to look at similar items in renewal and decide for a suitable value. For monsters, you can actually convert some values mathematically. I never wrote a converter for it, but it could certainly be done. For example if you look at HORN_SCARABA (2083): Attack: 886 Attack2: 91 Defense: 135 MagicDefense: 20 Defense 135 in renewal means 23% damage reduction. Which is the same as 23 DEF in pre-renewal. MagicDefense 20 in renewal means 15% damage reduction. Which is the same as 15 DEF in pre-renewal. So you would want to put this instead: Attack: 886 Attack2: 91 Defense: 23 MagicDefense: 15 Next problem is the attack. As you know, in pre-renewal Attack is minimum ATK and Attack2 is maximum ATK. But in renewal Attack is physical ATK and Attack2 is magical ATK. This could also automatically be calculated, you just need Level, STR and INT on top of Attack and Attack2. From renewal "Attack", "Level" and "STR", you can actually calculate both minimum ATK and maximum ATK. From renewal "Attack2", "Level" and "INT" you want to calculate the pre-renewal INT as that determines MATK in pre-renewal. But you only really need to do that if the monsters actually has any magical spells. Otherwise you might just want to leave the original INT value as it is. Also consider the "Level" as well. If you keep max level 99 on your server, then monsters have level 130+ will have too high HIT/FLEE, which might make them unbalanced on your server. I just improved my old helper tool to convert those numbers. It's attached. prerenewal_v2.zip

do you have it? if you have it can share with me? ^^