Map selection menu filters bugged?

:arrow_forward: GAME INFORMATION

:point_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.

  • GAME BUILD #: 50830
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED

:point_down: DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.

This may not be a bug. But when I select multiple filters in the map selection menu, I get some unexpected results.

Say for example, I want maps that are both competitive map and African. I check both radio buttons but Sonora pops up. This means that the selector is doing an OR condition.

I feel like it should be an AND condition. So if I check competitive maps and African maps, it should show me the African maps that are competitive.

If I select both land maps and water maps it should return a null set.

I don’t know if it’s intended or not, so just thought I’ll put it here.

:arrow_forward: FREQUENCY OF ISSUE

:point_down: How often does the issue occur? CHOSE ONE; DELETE THE REST!

  • 100% of the time / matches I play (ALWAYS)

:arrow_forward: REPRODUCTION STEPS

:point_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!

Here’s the steps to reproduce the issue:

  1. Open the map selector
  2. Choose more than one radio button as filter
  3. See that OR condition is used.

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?

I was expecting AND, which I feel is more intuitive. I understand some people like OR.

:arrow_forward: IMAGE

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.

I have pictures if you need … but I hope the info above was enough.

:arrow_forward: GAME FILES (SAVE / RECORDING)

:point_down: Attach a SAVE GAME (.aoe3Ysav) or GAME RECORDING (.aoe3Yrec) of the match where you encountered the issue. Link it below if using an external file service.

  • N/A

Hi @DiplexBoss6 !

Thank you for your suggestion!

We are now tracking this issue