[Source] [v83] MoopleDEV | Multi Worlds | Rev 120 | Rev121 Snapshot

[Eric]

Anybody know how to make max level to 250, instead of 200.

In client/MapleCharacter, search for getMaxLevel() and change the return from 200 to 250 (can also change Cygnus cap here too). Also change isCygnus() ? 120 : 200 ? in saveToDB to isCygnus() ? 120 : 250.

 

[OMGitsOMG]

In client/MapleCharacter, search for getMaxLevel() and change the return from 200 to 250 (can also change Cygnus cap here too). Also change isCygnus() ? 120 : 200 ? in saveToDB to isCygnus() ? 120 : 250.

So, I change...

    public int getMaxLevel() {
        return isCygnus() ? 120 : 200;
    }

to

    public int getMaxLevel() {
        return isCygnus() ? 120 : 250;
    }

and

ps.setInt(1, isCygnus() ? 120 : 200);

to

ps.setInt(1, isCygnus() ? 120 : 250);

To make max level to 250?
(I'm trying to get Explorer class to get to 250)
--------------------------------------------------------------------
Do I have to edit ExpTable.java, so that level 200~250 will have an exp to get to?



Actually, I'm looking at it and it's auto lvl 200 ~ 250 experience to 2 bil.
Is 2 bil the highest number it can go up to? or can I change that?



How can you change the Max experience that's shown?
At lvl 200 the max exp is set to 0. And at lvl 201~250 max exp is set to 2147483647. (These are just shown but it's not the actual number you need to get to next level)
The actual number from 200 to 201 is 1697021059. From +201 it's always set to 2 bil by how it's set up from the ExpTable.java

I want change the max exp shown to match what it actually is.

 

[Eric]

@OMGitsOMG Yes, that will raise the cap to 250 for just Explorers.

In ExpTable, anything > 200 will return Integer.MAX_VALUE. It is a check because the array size only fits levels 1->200. You can add more, but can't go anything higher than Integer.MAX_VALUE (2147483647) as the highest exp gain possible is of integer in v83, unless you modify it entirely in the client or update to v150+ when they changed it to long. Also, i'm pretty sure client-sided NEXTLEVEL::NEXTLEVEL exp calculations checks > 250 return INT_MAX, (2147483647), so again you can't do anything about it. However, you may be able to make it able to reach up to 255, but even if you modified the client to do so, exp would either be < 2147483647 or JUST 2147483647.

Now a workaround would be to add 2147483647 + exp and get a percent out of the total required. Server-sided you could make a @exp or something to check the EXACT exp required for the level.

tl;dr you can't go higher than 2147483647 exp without major client editing, but you can with server-sided checks and incorrect visual display by use of commands to show the real percentage.

Also, this is a release thread and I suggest creating help threads for such questions to avoid off-topic posts related to the release.

 

[Syre]

@OMGitsOMG Yes, that will raise the cap to 250 for just Explorers.

In ExpTable, anything > 200 will return Integer.MAX_VALUE. It is a check because the array size only fits levels 1->200. You can add more, but can't go anything higher than Integer.MAX_VALUE (2147483647) as the highest exp gain possible is of integer in v83, unless you modify it entirely in the client or update to v150+ when they changed it to long. Also, i'm pretty sure client-sided NEXTLEVEL::NEXTLEVEL exp calculations checks > 250 return INT_MAX, (2147483647), so again you can't do anything about it. However, you may be able to make it able to reach up to 255, but even if you modified the client to do so, exp would either be < 2147483647 or JUST 2147483647.

Now a workaround would be to add 2147483647 + exp and get a percent out of the total required. Server-sided you could make a @exp or something to check the EXACT exp required for the level.

tl;dr you can't go higher than 2147483647 exp without major client editing, but you can with server-sided checks and incorrect visual display by use of commands to show the real percentage.

Also, this is a release thread and I suggest creating help threads for such questions to avoid off-topic posts related to the release.

You gave me a delicious idea for a ridiculously high level (900? nah lets go 9000) on a high rate server. Hmmmmmmm. Too bad v83 has short for stats. :'[


Edit: with that said, theres the client that journey is working on