# Warpriest has wrong Gem Mastery bonus

**URL:** <https://community.gemsofwar.com/t/warpriest-has-wrong-gem-mastery-bonus/50965>\
**Category:** Bug Reports\
**Created:** [January 12, 2019, 5:33am UTC](https://community.gemsofwar.com/t/warpriest-has-wrong-gem-mastery-bonus/50965 "2019-01-12T05:33:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Starlite](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/starlite/32/43018_2.png) [@Starlite](https://community.gemsofwar.com/u/Starlite)\
**Post date:** [January 12, 2019, 5:33am UTC](https://community.gemsofwar.com/t/warpriest-has-wrong-gem-mastery-bonus/50965/1 "2019-01-12T05:33:54Z")

</div>

**Platform, device version and operating system:**  
Steam, Windows 7 x64

**What you were expecting to happen, and what actually happened:**  
The new Warpriest class has broken from the usual colour pattern that has applied to all previous classes. I am reporting this because it may be unintentional.

Every Hero Class potentially has 5 colours associated with it:

1. Mana colour of the Hero Class weapon.
2. +5 Bonus to Magic when using weapons with a particular mana colour.
3. +20 Bonus to a Gem Mastery colour.  
4-5. Arcane traitstone colours for unlocking Class Traits (can be the same colour).

For **every** previous Hero Class, only one or two different colours have been used, so the colours 1=2=4 and 3=5. In constrast, for Warpriest, 1=2=3=4=Blue, but 3\<\>5=Yellow.

Personally, I would prefer the earlier pattern to continue, by adjusting the Warpriest.

If this change was deliberate, I would be interested to hear the thinking behind it. Thank you.

Hope this helps.

---

<div class="post-metadata">

**Author:** ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)\
**Post date:** [January 13, 2019, 11:18pm UTC](https://community.gemsofwar.com/t/warpriest-has-wrong-gem-mastery-bonus/50965/2 "2019-01-13T23:18:34Z")

</div>

The team are aware of this issue and should be fixing it soon 🙂
