How '<attribute>_n' matchers work with HTTP payloads?

[matejsmycka]

Hello, I have created the following template:

flow: http(1) && http(2)

requests:
  - raw:
      - |
        GET {{login_path}} HTTP/1.1
        Host: {{Hostname}}
        Authorization: Basic RandomStringThatDoesNotExist==

      - |
        GET {{login_path}} HTTP/1.1
        Host: {{Hostname}}
        Authorization: Basic {{base64(username + ":" + password)}}

    attack: clusterbomb
    payloads:
      username:
        - admin
        - test
      password:
        - admin
        - test
        - password
      login_path:
        - /login
        - /admin
        - /logs
        - /

    stop-at-first-match: true
    matchers:
      - type: dsl
        condition: and
        dsl:
          - 'status_code_1 == 401 || status_code_1 == 403 || status_code_1 == 301'
          - 'status_code_2 == 200'

However, the matching of the status codes does work; I suspect it's because of the combination with clusterbomb.
The matcher works for status_code but not any status_code_N except status_code_0.

Is it a bug or a feature?
Is there any workaround?

Thank you