Jeweled Amulet — removes a charge without producing mana

[matthewevans]

Reported in Discord: https://discord.com/channels/1485498006781427802/1527802839114711070/1527802839114711070

Thread: Jeweled Amulet — removes a charge without producing mana
Discord thread id: 1527802839114711070

Summary

[[eweled amulet]]

Oracle text (verified from client/public/card-data.json)

jeweled amulet

{1}, {T}: Put a charge counter on this artifact. Note the type of mana spent to pay this activation cost. Activate only if there are no charge counters on this artifact.
{T}, Remove a charge counter from this artifact: Add one mana of this artifact's last noted type.

---

_{report_id: discord:1527802839114711070:1527802839114711070:0 · discord: 1527802839114711070/1527802839114711070}

[mike-theDude]

Triage analysis

Clarified summary
Activating Jeweled Amulet's second ability removes the charge counter but produces no mana.

Oracle text (verified from client/public/card-data.json)

{1}, {T}: Put a charge counter on this artifact. Note the type of mana spent to pay this activation cost. Activate only if there are no charge counters on this artifact.
{T}, Remove a charge counter from this artifact: Add one mana of this artifact's last noted type.

Investigation findings
This is a known parser gap and the gap is exactly the reported behaviour. Both halves of the card's noted-mana mechanic are unrepresented: the "note the type of mana spent to pay this activation cost" clause on the first ability, and the entire second ability that adds mana of the noted type. The first ability's counter placement is represented, which is why the cost is paid and the counter moves while no mana appears.

The missing primitive is a per-object record of a mana type noted during cost payment, plus a mana-production reference that reads it back. That is a small class (Jeweled Amulet and other "noted type" artifacts) rather than a one-off, so it should be built as a reusable noted-mana slot rather than card-specific state.

Acceptance criteria

• Paying the first ability's cost records which mana type was spent.
• Activating the second ability removes a charge counter and adds one mana of the recorded type.
• The recorded type survives across turns and is replaced, not appended, when the first ability is activated again.

[mike-theDude]

Classifier analysis

Verdict: unsupported_aspect

Matched clause: {T}, Remove a charge counter from this artifact: Add one mana of this artifact's last noted type. (supported: false)

Reasoning: The second ability is explicitly unsupported, as is the 'note the type of mana spent to pay this activation cost' child of the first ability. Only the first ability's charge-counter placement is represented, which matches the report exactly: the counter is removed and no mana is produced. The missing primitive is a per-object noted-mana-type slot written during cost payment and read back by a mana-production reference.

---

Posted by bug-coverage-classifier skill.