[Card Bug] Florian's where-X life-loss binding is unsupported

[PBernaerts]

Card(s): Florian, Voldaren Scion

Build/version: Current preview coverage, card_data_hash=f0a6b4b86732b9a2

Game mode: Commander / Unknown runtime

Actual behavior: Florian has one unsupported Effect:where_x_binding clause: where X is the total amount of life your opponents lost this turn.

No runtime behavior was tested.

Expected behavior: At the beginning of each postcombat main phase, X should bind to the combined life lost by all opponents during that turn and control how many cards are examined.

Steps to reproduce: Inspect Florian in the current preview coverage export; it is supported: false with gap_count: 1 and the diagnostic above.

[mike-theDude]

Triage analysis

Clarified summary: Florian's effect cannot bind X to the total life all opponents lost during the current turn.

Expected behavior: At each postcombat main-phase trigger, X is the combined life lost by all opponents that turn and determines how many cards are examined.

Observed behavior: Current preview data contains an unsupported where_x_binding node for the reported clause.

Oracle text (verified from client/public/card-data.json): “At the beginning of each of your postcombat main phases, look at the top X cards of your library, where X is the total amount of life your opponents lost this turn. Exile one of those cards and put the rest on the bottom of your library in a random order. You may play the exiled card this turn.”

Likely scope: Oracle effect parsing and engine binding of aggregate opponent life-loss history to X.

Acceptance criteria: The clause parses as a supported typed binding, and multiplayer runtime tests aggregate all opponents' life loss for the current turn before resolving the look/exile operation.

[mike-theDude]

Classifier analysis

Verdict: unsupported_aspect

Matched clause: “where X is the total amount of life your opponents lost this turn” (supported: false)

Reasoning: The preview export explicitly marks the reported where_x_binding node unsupported.

---

Posted by bug-coverage-classifier skill.