# Mab freeze trait stopped working

**URL:** <https://community.gemsofwar.com/t/mab-freeze-trait-stopped-working/9595>\
**Category:** Support\
**Created:** [July 15, 2016, 3:03am UTC](https://community.gemsofwar.com/t/mab-freeze-trait-stopped-working/9595 "2016-07-15T03:03:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pasa](https://avatars.discourse-cdn.com/v4/letter/p/e19adc/32.png) [@Pasa](https://community.gemsofwar.com/u/Pasa)\
**Post date:** [July 15, 2016, 3:03am UTC](https://community.gemsofwar.com/t/mab-freeze-trait-stopped-working/9595/1 "2016-07-15T03:03:13Z")

</div>

After the update no troop gets frozen on 4/5 match from mab trait. While Jarl’s similar trait works.

---

<div class="post-metadata">

**Author:** ![Ozball](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/ozball/32/36110_2.png) [@Ozball](https://community.gemsofwar.com/u/Ozball)\
**Post date:** [July 15, 2016, 3:03am UTC](https://community.gemsofwar.com/t/mab-freeze-trait-stopped-working/9595/2 "2016-07-15T03:03:36Z")

</div>

Known bug.

> [@2.0.1 Known Issues](http://community.gemsofwar.com/t/2-0-1-known-issues/9574/12):
>
> Update on Mab’s Winter Veil Trait: there seems to be a bug there. We will try to get a fix out asap, but Mab fix will need a client update.

---

<div class="post-metadata">

**Author:** ![Pasa](https://avatars.discourse-cdn.com/v4/letter/p/e19adc/32.png) [@Pasa](https://community.gemsofwar.com/u/Pasa)\
**Post date:** [July 15, 2016, 3:05am UTC](https://community.gemsofwar.com/t/mab-freeze-trait-stopped-working/9595/3 "2016-07-15T03:05:57Z")

</div>

Eh, was looking for a known thread but auto-skipped the stickies… O,O

---

<div class="post-metadata">

**Author:** ![Ozball](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/ozball/32/36110_2.png) [@Ozball](https://community.gemsofwar.com/u/Ozball)\
**Post date:** [July 15, 2016, 3:07am UTC](https://community.gemsofwar.com/t/mab-freeze-trait-stopped-working/9595/4 "2016-07-15T03:07:15Z")

</div>

The title does look very similar to the 2.0 Known Issues thread, so I almost skipped it initially for that reason as well. Hadn’t noticed that the 2.0 had been unpinned and 2.0.1 pinned in its place.
