Fixed [Indev 0.53] Max Level Parameter Bug

[Shou Liengod]

when you sec a higher level at max. lets say 200, once a pokemon levels up from 100, it would register it as level 101 right? however because of the battle doing automatic calculation, it will set to lvl 100 back, plus everytime your pokemon gets hit, it heals automatically to full HP regardless how much the HP was taken down.

this was tested when i set my pokemon to 149, i tryied lvling up, but in the process i noticed issues regarding what was stated above.
the EXP bar exceeds and it shows that its not registered.

this should be fixed for future Gamemodes regarding max Levels.

 

[The Omega Gengar]

My job here is thread reviving
I don't get much, but it makes for a living
I'm a Necromancer, so I take a big breath
As l revive this thread from death

Well yeah, this bug still happens.

 

[Shou Liengod]

so no one tested this bug yet? its quite the issue regarding the custom max level for gamemodes.

 

[jianmingyong]

I guess it is still exist.
Even the bar when pvp gets out of range.

 

[Fanta]

I guess it is still exist.
Even the bar when pvp gets out of range.

The exp bar has been fixed in 0.53, can you check if the other one has been fixed as well or not?

 

[Shou Liengod]

The exp bar has been fixed in 0.53, can you check if the other one has been fixed as well or not?

I will have to check when i can.

 

[jianmingyong]

The exp bar has been fixed in 0.53, can you check if the other one has been fixed as well or not?

By using the old version of 1 Year Later 3D gamemode, the game simply not responding when I battle a level 700 Dream Monster while I set the eevee to level 600.

Not working....

 

[jianmingyong]

Okay, I reduced the level.... To Lv 120 Eevee and Lv 20 for the dream monster and this time it didn't freeze ( Probably integer value is overflowed... )
and it becomes this:

 

[Shou Liengod]

Okay, I reduced the level.... To Lv 120 Eevee and Lv 20 for the dream monster and this time it didn't freeze ( Probably integer value is overflowed... )
and it becomes this:

View attachment 8178

suppose its still not fixed yet. had the exact issue when the pokemon is still at lvl:100 but still considered 120...
welp, still need to wait.
and yeah its an older version anyway.

 

[jianmingyong]

Fixed in next version.