hi can anyone tell me a easy way to change the exp rate and also to change the cap?
hi can anyone tell me a easy way to change the exp rate and also to change the cap?
You change the Exp rate in MobInfoServer by using the Exp Editor. The level cap can be changed in ChrCommon.txt.
can you link me a web that has exp editor to download? please.
It's in the Shn editor. Tools > Exp Editor
ohh sorry didn't see the exp editor
but i want the server be x400 exp, it will take ages to change all mobs exps
That's why you use the Exp editor.
But in the new files I realized it's a bit buggy. The EXP Rate editor gets the current EXP rate from Slime's current EXP. I was able to set the EXP rate to the same as Outsparks(Slime exp value to 1) using the Column Massive Edit but then the EXP Editor won't work. Have you encountered it and/or have you found a fix to it?Originally Posted by Shawie
Last edited by Alsm97; 10-05-13 at 12:27 PM.
If you change the Slime's exp to 20 on the Odin files it should work. I don't know about Outsparks rate, try setting Slime's exp to 2 and then try using the Exp Editor.
I've tried every single value from 1 up to 20. They all got the EXP Editor to throw an exception until I reached 20 EXP, that was EXP Rate x1.
Just use the Column editor; does the same thing anyway.
Or code your own editor and embed other features that you need as you progress; always more fun to take that approach anyway.
That makes a lot of sense. I should try that but I don't know anything about SHN files except using the SHN Editor and editing them.
Can you guide me a little bit on how my application will read the SHN files?
Any help is much appreciated! Thank you.
Regards,
Alex
I agree..
1. Open MobInfoServer.shn
2. Column -> Column Index Editor
3. Set MonExp to 20 For items where MonExp = 0
4. Foreach (MonExp == 0) {Klick Go} (Order 0 EXP to top and you see when you fin.)
5. Tools -> Exp Rate Editor
6. Enjoy
I already tried that, It doesn't work lol.
How hard is it to understand how that works?
Alsm97 you said it gets the exp rate from Slime exp.
Because the exp rate editor accepts values from 1...n then to decrease you must make so that it figures that you have higher rate than 1.
So to decrease - set Slime exp to 20*m.
Ex.: You set it to 80 which is x4 rate and if you set it to 1 it divides all values with 4.
Ex.: You set it to 20 which is x1 rate and if you set it to 4 it multiplies all values with 4.
And after that you can set slime exp to 1 or whatever you like, so it would match with all other exps.
Value must > (over) 20 !
slime = 11 = error
I understand what you mean.. Believe me i tried all tweaks possible.. :p The tweaks are made using the Column Massive Edit and Massive Multiply all MonEXP values by 0.x
Thing is the Slime monster, like xWhiteCore says above, MUST ALWAYS be >= 20. Which means any Slime MonEXP value that is less than 20 will make the EXP Editor throw an exception. What we could do is use my method with the Massive Multiply and drop the mobs exp to Outsparks EXP rate(multiply with 0.x until Slime MonEXP equals to 1) and then just change the Slime MonEXP manually to 20. So the EXP Rate on all monsters is x1 which is Outsparks exp rate except for the Slime. But that ruins the whole idea of the EXP Rate to x1 as Slime is the first monster you encounter. We might eventually find a work-around to this but I'm not sure it's anywhere soon. Like Myth suggested me, I can try make my own SHN Editor and I'd gladly do. I don't care wasting countless hours on it, I enjoy programming. Problem is I don't have a base to begin from. I know nothing about reading SHN files and how they exactly operate so I could use a helping hard to start my project. Thanks for trying to help tho, I'll keep you up-to-date if I find a solution to this.
PS: The letter x where i say 0.x represents a number.
Have a great day!
Regards,
Alex
EDIT:
And another fix that I just thought of that I DO NOT SUGGEST but it simply seems it's the only legit way of doing this.
0. Make the exp rate to Outsparks using my Massive Multiply method (Read my post above on how).
1. Copy the row of the Slime.
2. Change the ID of the copied Slime row to an unused monster ID.
3. Change the original Slime row InxName to FakeSlime or expRate or whatever you like.
4. Change the MonEXP of the FakeSlime/expRate or whatever you called it to and make the MonEXP to 20.
5. Open EXP Editor with no thrown exception.
I do not recommend this method, but it seems it's the only proper way right now. I don't know about the consequences for doing this.
Good Luck.
Regards,
Alex
Why so complicated, you edit the all other exp to whatever you need and then lastly change the Slime exp to 1 or whatever.
Yes, that's what I did before. Check the screen on on the previous page and observer it carefully. And also read my previous post and take notes on all the facts I made for the EXP Editors functionality.
I don't see problem there. If you want to edit it again, you edit the Slime exp first........
Seems that I'm most of the cases misunderstood.
As for you the idea changing mob exp to 1x is waste of time, unless you really want exactly 400x exp.
But if current rate is 13x (Slime exp is 13, and if you divide it with 13 you get 1).
So the desired and current rate difference is 400/13 about 30, then change slime exp to 20.
Use Exp editor and change the rate to 30, now all other mobs exp rate is 400x, but slime is 600x, so change it to 400.
Just get used to how the Exp Rate Editor works. Its just coded that way.
@Alsm97
If you want to code your own Editor then search for "Fiesta Editor source".
It gives you a project what was stalled, but has basic file handling.
I don't see problem there. If you want to edit it again, you edit the Slime exp first........
Seems that I'm most of the cases misunderstood.
@Alsm97
If you want to code your own Editor then search for "Fiesta Editor source".
It gives you a project what was stalled, but has basic file handling.
I'm very sorry to have misunderstood you! Now I understand exactly what you mean! I guess my head ALWAYS goes to the advanced solutions and skips the simple work-arounds.. Haha xD Thank you for the tip, that should be an easy way for doing it. My fix is a permanent fix but I don't know if it has any consequences.
OH! Thanks for the source code as well, I didn't know they had shared it. I'll see what I can do, I'll work it all our eventually like always.
Have a good day.
Regards,
Alex
Reply With Quote
