Several creatures that should not be skinnable can be skinned

[Einkatzi]

CURRENT BEHAVIOUR: I skinned mountain cougars (level 3, ID 2961) in Tauren starting area in Mulgore. They drop surprising amounts of Medium Leather and even Red Whelp Scale. Their skinloot entry is 100008, which is supposed to be used for Red Whelp (1042), Lost Whelp (1043) and Crimson Whelp (1069). The same skinloot entry is used for several other creatures that aren't supposed to skinnable (see below).

EXPECTED BLIZZLIKE BEHAVIOUR:

1. They should not be skinnable at all.

SOURCE: Wowhead TBC Mountain Cougar has no skinning loot entries. TrinityCore had the same issue and fixed it There were more creatures in TrinityCore that had this skinloot template. In the case of AzerothCore, it's the following creatures:

• 1419 Fizzles
• 2230 Umpi
• 2955 Plainstrider
• 2961 Mountain Cougar
• 2966 Battleboar
• 3124 Scorpid Worker
• 3680 Serpentbloom Snake
• 4781 Snufflenose Gopher
• 6728 Narnie
• 6867 Tracking Hound
• 7507 Brown Snake
• 7508 Black Kingsnake
• 7509 Crimson Snake
• 7557 Prarie Dog
• 8612 Screecher Spirit
• 10042 Corrupted Saber
• 10577 Crypt Scarab
• 10657 Corrupted Cat
• 11884 Obi
• 12202 Human Skull
• 12257 Mechanical Yeti
• 12372 Brown Ram
• 12373 Gray Ram
• 12374 White Riding Ram Mount
• 12581 Mercutio
• 14453 Orb of Domination
• 14495 Invisible Trigger One
• 14602 Swift Stormsaber
• 14646 Stratholme Trigger
• 14869 Pygmy Cockatrice

STEPS TO REPRODUCE THE PROBLEM:

1. Learn skinning and carry a skinning knife
2. Kill one of the above mentioned creatures (won't work with every ID - Stratholme Trigger or the Orb of Domination probably won't be killable).
3. Skin it.

EXTRA NOTES: As mentioned, TrinityCore had the same problem (with even more creatures) and fixed it, specifically in this commit

AC HASH/COMMIT: ChromieCraft on AzerothCore rev. cedbd604d3f5 2021-06-29 00:45:12 +0200 (master branch)

OPERATING SYSTEM: Windows 10

MODULES: ?

CUSTOMIZATIONS: several addons, but no relevant ones

[Einkatzi]

I'm sorry, I just saw that this issue has been reported before.

6250 is the original issue.

However, the fact that TrinityCore has solved the same problem already might be useful to know.