Thank you for the report, however I don't believe there is an easy fix due to how the client loads monster info =/ Just applies to this one monster as far as I know.