To Devs: Fix Blu

[Mavrick]

Corrosive Ooze is 5% attack down / 5% defense down not 33% def down, has regular MA/ME.
.

Just a little correction here but...
There are 2 versions of Corrosive Ooze. Blue Mage version and BST's version which they get access to via Gooey Gerard.
Blue Mage gets the gimp 5% version. BST gets the superior version which is ATK/DEF-33% with a max duration of 90 seconds (3 mins recast). I've yet to see Corrosive Ooze fail on anything that is not naturally resistant to enfeebles and considering that Gooey Gerard's Purulent Ooze (Max HP-10%) sticks with high accuracy even on NMs in Hall of Ki I'm willing to bet Ooze is just as potent.

[saevel]

Just a little correction here but...
There are 2 versions of Corrosive Ooze. Blue Mage version and BST's version which they get access to via Gooey Gerard.
Blue Mage gets the gimp 5% version. BST gets the superior version which is ATK/DEF-33% with a max duration of 90 seconds (3 mins recast). I've yet to see Corrosive Ooze fail on anything that is not naturally resistant to enfeebles and considering that Gooey Gerard's Purulent Ooze (Max HP-10%) sticks with high accuracy even on NMs in Hall of Ki I'm willing to bet Ooze is just as potent.

Blue Mage gets modified versions of the monsters spells, SE kinda of stated this years ago. For this reason I'm only speaking about the BLU versions as most monsters versions would be stupidly broken for a BLU to use.

To the above people saying the "test server and real server are different", you don't think SE knows this? You think that if they wanted Torbillion to have regular magic acc they would of copied that over when they implemented it? The production server is ~always~ the "correct" version, development servers are just that, for development.

It's now boiled down to a few people crying of very minor things they see as problems and saying that Blue "needs fixing" because of that.

You can keep on arguing but it won't change SE's position. Your own position has already been self defeated the moment you referenced the development server as being "right".