Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

LCI Mocked Draft fails to start on unmapped booster cards

Closed
  • Is something wrong?
#682 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend, desktop

Research direction

Start by reproducing the failure with an LCI booster fixture and inspect the Draftmancer booster parsing and Scryfall identity-mapping paths mentioned in the issue. Identify the unmapped card, then run the fixture test and verify an unmappable card names itself in the error. After the dependency is resolved, confirm an LCI Auto Mocked Draft completes through the desktop GUI to deck build.

Written by the indexing model from the issue text.

Description

bug draftomen size: M

Problem

Starting an LCI Mocked Draft fails with "the simulated draft did not start: Draftmancer booster card must have a mapped Scryfall id or an integer arena_id". HOB works with the same Draftmancer checkout and Scryfall bulk file. The failing card and the cause are unknown.

Proposed change

Find which LCI booster cards fail the mapping and fix the mapping. If a card truly cannot be mapped, report the specific card in the error.

Acceptance Criteria

  • AC1: A test with an LCI booster fixture reproduces the failure and passes after the fix.
  • AC2: An LCI Auto Mocked Draft in the desktop GUI completes to a deck build.
  • AC3: An unmappable booster card produces an error that names the card.

Dependencies

Blocked by "Mocked Draft set selector resets to HOB after choosing another set", so LCI can be selected.

Implementation classification

  • Estimated size: M
  • Orchestration risk: Normal
  • Reason: The cause is not yet known and may sit in Draftmancer booster parsing or Scryfall identity mapping.
Dominant language
Python
Stars
2
Forks
0
Avg merge
4h 48m
Merged PRs (30d)
225

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from andreagrandi/draftomen

All issues in andreagrandi/draftomen

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.