@dodgepong Nice idea, ICE and ICE breakers are important, maybe I will implement it in the near future.
@iReidBooks Thx for spotting the tablet problem, I will check it out.
As for advanced filtering and complicated queries: What you can see on the site are pre-calculated, cached, static content. Statistics are not calculated on the fly as you visit the site. The reasons are to make it faster for the visitor and less stressful for the backend and easier, cheaper to host. Currently 1500+ query results are stored. Introducing more filters would increase this number exponentially. When a new idea comes up I have estimate how useful would that be for the average user and how many users would actually use it. Also replacing the data layer means a lot of work for me
I believe that filtering for cardpool and identity is generally a good way to go. New cardpool usually shakes up the meta and results changes in deck composition. Different IDs usually mean different archetypes as well, it’s rare that you can build the same deck concept with different IDs. There are always niche situations of course.