Mobs are shown as "warrior" or "mage" when they are clearly something else, i.e. shamans

Bug #723456 reported by speedwaystar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MobInfo2
Won't Fix
Low
Unassigned

Bug Description

Submitted via: Curse Client 4.0.1.104, Microsoft Windows NT 6.1.7600.0
By: Zenshu
On: Sun, 2 Jan 2011 23:06:14
Version: MobInfo2 v3.83

Description: seems to only acknowledge the Warrior and Paladin or mage class since every mob I have fought has either been classified as a Warrior, mage or Paladin even if they are neither.

Tags: stats
Revision history for this message
speedwaystar (speedwaystar) wrote :

This is unfortunately Blizzard's fault: MobInfo2 simply displays the class names which WoW publishes for each particular mob.

I'm not sure, but I'd hazard a guess that Blizzard have a small number of standard "AI" packages which basically fall into either "Warrior (melee warrior)", "Rogue (melee warrior that backstabs)", "Mage" (ranged caster), "Paladin" (melee warrior caster) and maybe "Hunter" (ranged caster that uses a pet). For this reason you'll see priest mobs classed as "Mage" (because they use ranged caster AI), and Shaman mobs classed as "Paladins" because that AI package makes them close to melee range and use weapons, but also cast spells.

So, I think the names we're seeing are probably really internal flags describing the set of basic AI behaviours shown by the mob.

Changed in mobinfo2:
importance: Undecided → Low
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.