2011-07-11, 12:21 AM
According to Nexon, this should be fixed after the update.
They've already addressed this, though.
They've already addressed this, though.

