Mag Glitches

[Scissors61]

so far from what i've seen so far, EV3(like Varaha) and possible EV2(like mitra) will glitch when diets or feeder(id/class) changes. This is possibly because the game thought it was the mag it was supposed to be but wasnt at the time(s) it was fed. Confusing? yes but heres a great example:

For Kaitabha, sol atomizors usually would increase POW and some DEF. Mags will evolve when its on a ranger w/ Sect ID GBPOW and DEX is greater than POW. However, EV3(which is what Kaitabha is) usually will check it's stat balance again and correct its form. So at multiples of 5, Kaitabha has a legitimate chance of changing into a different mag if the either the feeder changes into something other than a ranger w/ Sect ID GBPOW or if DEX is no longer greater than POW which is also greater than MND. In this case, normally mag feeders have a risk of having a Sato plan messing up because DEX usually leads the diet until the very end where POW is 5 lvs greater. When POW is greater than DEX which is greater than MND on a ranger w/ GBPOW, kaitabha COULD have changed into a Madhu but usually it doesnt as the balance chanck skips ever other 5. So in reality, the game knows its a kaitabha ur feeding and will raise POW and DEF respectively but when the player disconnects/leaves room/ect. the game will forget it was a kaitabha the player was feeding and look back the history and believe the mag was a Madhu and that the Madhu was fed Sol Atomizors. Unlike the kaitabha, Sol Atomizors raise MND(primarily) and DEX. This means the game thought the player was raising MND levels on the mag instead of POW and the mag is basically ruined because 4lvs from 95(which is where POW will most likely pass DEX) the player will need to change to an appropriate fomarl/fonewearl to make a sato. I have run several tests, ive fed and raised over 40 mags so far, these facts are solid.

[Scissors61]

so far from what i've seen so far, EV3(like Varaha) and possible EV2(like mitra) will glitch when diets or feeder(id/class) changes. This is possibly because the game thought it was the mag it was supposed to be but wasnt at the time(s) it was fed. Confusing? yes but heres a great example:

For Kaitabha, sol atomizors usually would increase POW and some DEF. Mags will evolve when its on a ranger w/ Sect ID GBPOW and DEX is greater than POW. However, EV3(which is what Kaitabha is) usually will check it's stat balance again and correct its form. So at multiples of 5, Kaitabha has a legitimate chance of changing into a different mag if the either the feeder changes into something other than a ranger w/ Sect ID GBPOW or if DEX is no longer greater than POW which is also greater than MND. In this case, normally mag feeders have a risk of having a Sato plan messing up because DEX usually leads the diet until the very end where POW is 5 lvs greater. When POW is greater than DEX which is greater than MND on a ranger w/ GBPOW, kaitabha COULD have changed into a Madhu but usually it doesnt as the balance chanck skips ever other 5. So in reality, the game knows its a kaitabha ur feeding and will raise POW and DEF respectively but when the player disconnects/leaves room/ect. the game will forget it was a kaitabha the player was feeding and look back the history and believe the mag was a Madhu and that the Madhu was fed Sol Atomizors. Unlike the kaitabha, Sol Atomizors raise MND(primarily) and DEX. This means the game thought the player was raising MND levels on the mag instead of POW and the mag is basically ruined because 4lvs from 95(which is where POW will most likely pass DEX) the player will need to change to an appropriate fomarl/fonewearl to make a sato. I have run several tests, ive fed and raised over 40 mags so far, these facts are solid.

[Scissors61]

Okay well heres what my current glitched mags are supposed to be right now

2 White:sato:5DEF/50POW/45DEX/0MND

2 Black:sato:5DEF/50POW/45DEX/0MND

However, the kaitabha lv99s glitched when logging out into what is seen in the pictures

http://s1105.photobucket.com/albums/h356/Julius_Lontok/?action=view&current=Fixmymagsplease.jpg

[serverus]

solved