If you installed the author’s GitHub release of Magic Set Editor and opened it to find no card frames at all, nothing is broken. The 2.1.2 zip is the program only — 4,347,166 bytes for the win64 build — and it deliberately ships without game templates or fonts. Templates live in separate community packs, and installing one is a file-copy job, not a setup wizard. This guide walks through it exactly as the pack maintainers describe it.
What a template pack actually contains
Template packs are maintained by the MagicSetEditorPacks organisation on GitHub, separate from the program itself. The largest Magic pack, Full-Magic-Pack, contains a data/ folder (the templates), a Magic - Fonts/ folder (the required fonts), the program files themselves (magicseteditor.exe and mse.exe, which are the same program, plus the magicseteditor.com command-line version), and a Template Creation Tutorial document. The data/ folder is the part that matters here: it is what you copy into your own program folder.
Step by step: copy data/ into your MSE folder
- Step 1 — Put the program somewhere writable. Extract Magic Set Editor into a folder you can write to, such as Desktop or Documents — not Program Files, which causes save errors (see our full installation guide).
- Step 2 — Download a template pack from the MagicSetEditorPacks project on GitHub. For Magic, the Full Magic Pack is the complete option; the M15 packs are smaller, focused alternatives. Our templates hub lists the packs and what each one is for.
- Step 3 — Extract the pack to its own folder first. Do not copy files out of an unextracted zip window.
- Step 4 — Copy the
data/folder from the extracted pack into your Magic Set Editor folder, alongside the program file. If Windows asks about merging folders, allow the merge. - Step 5 — Install the pack’s fonts. Open the pack’s fonts folder, select every font file, right-click and choose Install. This is a separate, required step — our font installation guide covers it in detail.
- Step 6 — Restart Magic Set Editor and create a new set. The pack’s frames should now be offered as template choices.
The trap: the bare 2.1.2 program has no templates
This deserves repeating because it generates most of the confusion around MSE installs. The SourceForge 2.0.0 full installer (2011) and the community 2.5.8 integrated packages bundle their frames, so they work immediately. The GitHub 2.1.2 release does not: it is a portable zip of the program alone, published that way by the author. An empty template list after a 2.1.2 install means the template step is still missing — it does not mean the download was corrupt. If you would rather skip the two-part install entirely, the community integrated packages on our download page bundle program and frames together.
Integrated packs vs. adding templates yourself
Some downloads blur this line. The Full-Magic-Pack is itself an integrated package: it includes the program files next to its data/ folder, so extracting it gives you a ready-to-run portable setup. That is different from adding templates to an existing program folder, where only the data/ (and fonts) move across. Both routes end at the same place; what you must not do is mix them carelessly — copying individual template files out of context, instead of the whole data/ folder, leaves templates half-installed and missing their supporting files.
Verify the install worked
- Create a new set: the template picker should list the pack’s frames, not an empty or near-empty list.
- Type a card title and body text: the text should render in the pack’s card typeface, not a plain fallback font. Wrong-looking fonts mean step 5 was skipped.
- Open a card and look at its frame art: borders and text boxes should be complete, with no missing-image placeholders.
- Restart the program once more: templates that survive a restart are installed in the program folder, not being read from a temporary location.
If the frames appear but the text looks wrong, the templates are fine and the fonts are not — fix the fonts before reinstalling anything.