# Problem with class filter

**URL:** https://community.gemsofwar.com/t/problem-with-class-filter/76918
**Category:** Bug Reports
**Created:** [September 8, 2022, 7:25pm UTC](https://community.gemsofwar.com/t/problem-with-class-filter/76918 "2022-09-08T19:25:31Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Jerry\_the\_skunk](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/jerry_the_skunk/32/53897_2.png) [@Jerry\_the\_skunk](https://community.gemsofwar.com/u/Jerry_the_skunk)
#### Post date: [September 8, 2022, 7:25pm UTC](https://community.gemsofwar.com/t/problem-with-class-filter/76918/1 "2022-09-08T19:25:31Z")

</div>

PC/Steam version here.

This bug is a little difficult to explain, and I don’t have the means to capture it on video. Should be easy to reproduce though.

If you have a team with a hero, whose active class is not among the first few in the selection, but further down the line (in my case Sunspear), the result of a kingdom or type search in the class menu will seemingly come back empty. If you move the empty screen to the left a bit, your search result will show up.  
The problem is, that the screen position you were at is carried over into the filtered search, I think.

---

<div class="post-metadata">

### Author: ![Lucien](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/lucien/32/75325_2.png) [@Lucien](https://community.gemsofwar.com/u/Lucien)
#### Post date: [September 8, 2022, 7:49pm UTC](https://community.gemsofwar.com/t/problem-with-class-filter/76918/2 "2022-09-08T19:49:23Z")

</div>

hit apply filter twice

---

<div class="post-metadata">

### Author: ![Jerry\_the\_skunk](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/jerry_the_skunk/32/53897_2.png) [@Jerry\_the\_skunk](https://community.gemsofwar.com/u/Jerry_the_skunk)
#### Post date: [September 8, 2022, 7:50pm UTC](https://community.gemsofwar.com/t/problem-with-class-filter/76918/3 "2022-09-08T19:50:27Z")

</div>

I know, that I can still find my result. Does not change the fact, that this is a bug and deserves to be fixed.
