Please see the original thread on BoardGameGeek 🤓
This repository hosts three documents. Efforts are ongoing to translate them to languages other than English. Please reach out if you'd like to help with translating. Click in the table to download the most recent builds in the chosen language:
| Progress | 📜 Rewritten Rule Book | 🖨️ Rule Book - printable version | 📋 Comprehensive Components List | |
|---|---|---|---|---|
| 🇬🇧 English | 100% | 🇬🇧📜 | 🇬🇧🖨️ | 🇬🇧📋 |
| 🇵🇱 Poski | ~50% | 🇵🇱📜 | 🇵🇱🖨️ | n/a |
| 🇪🇸 Español | ~25% | 🇪🇸📜 | 🇪🇸🖨️ | n/a |
| 🇫🇷 Français | ~10% | 🇫🇷📜 | 🇫🇷🖨️ | n/a |
Componets List lists all the cards 🃏, minis 🚹, tokens, etc. for every box. See another BoardGameGeek thread for details.
This project aims to rewrite the original rule book, in which the amount of vague language was just too vast to ignore.
This repository hosts a document that aims to explain the rules clearly and concisely, and should eventually have an answer for any basic rules query you might have.
The content in the official English rule book is, simply put, insufficient as a teaching tool for the game or as a general rules reference. If you read the thread linked above you should understand how frustrating this has been for me.
I am completely rewriting the rule book in LaTeX. It's possible that a finalized version will be later put together using other tools such as Adobe Visual Studio.
This is a communal effort. This repository serves both as a means for me to preserve my work, but also for others to contribute to it as writers, proofreaders, or layout designers. If you wish to contribute directly, please contact me on BoardGameGeek or discord, my username is Heegu on both platforms.
All new version of the rule book and their change logs will be published here and in the BGG thread. I will probably submit an indefinite number of changes before changing the version number again. The aim is to have a vastly superior "1.0" version ready before most people receive their pledges.
The current aim is to produce a document that's meant more for digital reading, as most references to other rules and sections within the document are accomplished by using hyperlinks in the text. I know most people would also love a version that's designed more for printing, I'll see if I later have the energy to create that as well. A printable document would probably be more of a shorter reference, this document will always have 30+ pages.
Please discuss any and all factual errors, bad language or other errors you've found by either contacting me directly or in the thread. You can do this by reaching out to me directly or by opening pull requests with suggestions.
To work on the document on your machine, you need the following:
- MiKTeX (required) to build the PDF file from LaTeX files
- Inkscape (required) to render glyphs in the document (while installing on Windows, make sure to tick
Add Inkscape to the System Pathoption) - TeXstudio (optional) to edit LaTeX files and rebuild the PDF file quickly
- po4a (optional) to work on translating the document to other languages
- GIMP (optional) to edit some images in
assetsdirectory - see below for details - aspell (optional) for spellchecking - see below for details
To build the document in English, either run this in the command line:
latexmk -pdf -silent -shell-escape "main_en"or press the Build & View main_en.tex file.
To build the document in any other language (currently pl, es and fr are supported), make sure you have po4a (version 0.70 or higher) and use the script:
./build.sh <LANGUAGE>or press the Build & View main_<LANGUAGE>.tex file open, after running po4a (see Translations below for details).
To build components list instead of the rule book, use this:
latexmk -pdf -shell-escape components_listor press Build & View on file components_list.tex open in TeXstudio.
To build the printable version in a given language, make sure you've built a regular one first at least once. Then, use the script:
⚠️ Be careful, as it edits all the files! Also, you'll need Python for this 🐍
./make_printable.sh <LANGUAGE>Make sure you have po4a installed (MacOS instructions).
To translate a particular section:
- Go to
translations/<section_name>and open<lang>.pofile, e.g.,translations/introduction.tex/pl.po - Choose a fragment to translate. Those start with
msgid. Write your new text in the line below starting withmsgstr. Example:This text (msgid "\\addsection{Introduction}{\\spells/magic_arrow.png}" msgstr "\\addsection{Wprowadzenie}{\\spells/magic_arrow.png}"
msgstr) will replace the original (msgid) in your translation. - Regenerate your localized section:
Disregard the errors about mismatched
po4a --no-update po4a.cfg
multicols, as this is an upstream parser issue. - Rebuild your PDF file (or press Build
▶️ in TeXStudio).latexmk -pdf -silent -shell-escape "main_<lang>" - Commit and repeat!
TeXstudio has built-in spellchecking, but the first steps have been made towards automated spellchecking with aspell. For local development, after installing the tool, you can run it from the command line for example with
aspell -d en_US -p=./.aspell.homm3.pws --mode=tex --dont-backup check main.texor when wanting to check all .tex files then with
find . -type f -name "*.tex" -exec aspell -d en_US -p=./.aspell.homm3.pws --mode=tex --dont-backup check {} \;Please note that currently the tool will flag many parameters in LaTeX commands. We are currently looking into it, how best to remediate this.
The personal dictionary .aspell.homm3.pwd currently contains only game-related words.
It does not contain names (e.g., "BoardGameGeek") or parameter values (e.g., "px", "svg") in order to minimize the chances of false-negatives in the main body of text.
All assets come from publicly available sources.
Some of the images in the rule book (all in the assets/examples directory as of writing) were generated by GIMP.
Their respective XCF files reside in assets/gimp-files directory.