Question about aging rate and mix editor tool

I try to use aging rate and mix editor

but after i update the server.exe file. The server.exe file is damaged, and i notice the file size increase also.

Does anyone have the same problem?

Please help me out!!!! Thanks

friend, about the aging rate, i change manually, but the mix editor, i try use the "update mix editor" and is 100% right... but, if you have problems to add a new mix try this:

The mix editor show to us 300 diferent mixes, go to 114 ~ 115 + or - , you go see a blank mix... start here to create or mixes, because you try add the numer 301 the mix not save your progress...

Try this, and back here to answer...

thanks for reply.

I tried with different slot above 103... it still does works.. Maybe i do it incorrectly...

Please check to see which step i did it incorrectly

1) load the server.exe
2) enter 200 at the box (between - and +)
3) Press "Read Mix"
4) Select: sword, axe, javaline, pole, bow...
5) Select: "Don't use new sheltom"
6) 6 celesto and 6 Devine
7) enter the value and effect at label from 1-4
EX: 80 Max.atk 80 Min.atk 8% crt 8% block

5) Select: "use new sheltom"
6) 3 3 3 3 for each new sheltom
7) enter the value and effect at label from 5-8

8) Press "Write Mix"
9) "Save File"

Same problem here. Some people dosent have any problem,some have. What's the difference? I'm using the updated mix editor with the attached -KPT-Endless-Tower-Update-V2.2.exe
Anyone resolved it?

Editing the Mixing table is a Hex edit to the executable... when MixEditor was released it was mentioned that "everybody here knows how to do it manually" and MixEditor just makes it quick and easy... guess what... I don't know how to do it manually. :D:

But I do know that if you change the exe around with LordPE or such, the easy method will stop working. :wink:

LOL.But it's important for me if I can change it or not, because new sheltoms become almost worthless unless it can be used with mixing.:(:

Agreed. My statement is a matter of fact, and equally a plea for the old school (presumably 1st or 2nd generation) devs to remind us upstarts how it was done back in the day. :wink: