Report a bug

Something misbehaved at the table? Reports are welcome — every one is investigated, and you will hear back on the issue whether the answer is a fix, a documentation improvement, a design-feedback note, or an explanation of what the module was doing and why.

One module, one issue queue — the importer is part of ACKS II — Extras, so a problem connecting or importing a book goes to the same form as a problem on a sheet. The form has an optional field for which book, if that is where it happened.

Where to file

• ACKS II — Extras

  Everything on the sheet and at the table: class documents and the class builder, proficiencies and class powers, equipment and encumbrance, formations and marching order, henchmen and hirelings, influence and reactions, places and markets, monster stat blocks — and connecting your books, importing content and tables from them, and the Getting Started band in the Books window.

  File a bug report

Filing needs a free GitHub account. The form walks you through everything below.

What makes a report actionable

• Versions — the module’s and Foundry’s. Both are on the form, and both matter: the bug you hit may already be fixed in a newer release.
• Which book, if it happened while connecting or importing one — by name, and the printing or PDF release if you know it.
• What you did and what you saw, step by step. Which sheet, which button, which actor or item. “Encumbrance is wrong” takes a conversation; “I dragged a shield onto Marcus and his stone count didn’t change” takes a fix.
• What you expected — the rule as you understand it, with a book and page citation if you have one.
• Console errors. Press F12, open the Console tab, and paste anything red. This is very often the whole diagnosis.
• Whether it survives disabling other modules. If you can, try with only the module and its requirements enabled — it is the first question we will ask.

Cite pages, never paste them

Never paste book text or attach page scans or PDFs to a report. Name the book and page instead — “ACKS II Revised Rulebook p. 47” tells us everything the excerpt would.

Not sure it’s a bug? Check the guides first — the behaviour you hit may be documented, and if it turns out the docs are what’s missing, that’s a report worth filing too.

Something in your world looks broken rather than behaving wrongly? Examples are a sheet listing someone who was deleted, a purchase you cannot find, or a party member who is no longer there. As the GM, run Repair This World (GM) from the ACKS Extras Macros compendium, or open it from the module’s settings. It lists the damage this module knows how to find and changes nothing until you choose. If it finds nothing, or its fix does not take, that is worth a report. Say what it listed.