Skip to main content

Contact

I read everything that comes through here. Bug reports from people actually running games are the most useful thing I get, and they tend to get fixed quickly.

Before you write

Email: Click to reveal

I usually reply within a few days. It's one person, not a support desk.

Reporting a bug? Include the page and what you were doing — it saves a round trip.

Built something good? Submit it to the Community Gallery.

What to send

A bug

The most useful reports name the tool and the step, say what you expected, and say what happened instead. If a monster or spell is involved, its name is usually enough for me to find it. If you saw an error message, paste it verbatim — the wording tells me which code path failed. Your browser helps too, since a surprising number of issues are specific to one.

Challenge rating that looks wrong

This is worth its own mention because it is the most common disagreement, and it is often me rather than you. The calculator follows the official challenge-rating maths, which does not always agree with how a creature actually plays at the table. If you think a number is off, tell me the creature and what you expected — if it's a bug in the maths I want to fix it, and if it's the official formula being the official formula I would rather explain that than leave you second-guessing the tool.

A feature you keep wishing existed

Especially if you have worked around its absence more than once. The thing you have quietly given up on asking for is usually the thing worth building. Requests that come with the situation that prompted them get taken more seriously than requests on their own, because the situation often suggests a better answer than the feature.

Something about your own content

If you want a gallery submission edited or taken down, say which one and I will handle it — you do not need to explain why. If you believe something published here infringes your copyright, or that a submission contains material it should not, flag it and I will look at it promptly. See the attribution page for how licensing works on the site.

What to expect back

A reply within a few days, from me. There is no ticket system and no autoresponder. Bugs that stop you using a tool get looked at first; feature requests get an honest answer about whether and roughly when, rather than a polite maybe.

If you would rather not use the form, the email address above works just as well — it is obscured only to slow down scrapers.

Faster than writing to me

A few things you can settle without waiting for a reply:

  • Your work is saved in your browser before you make an account. If it has vanished, check whether you are in a private window or have cleared site data — that accounts for most reports of lost work. Signing in adds cloud saving so it follows you between devices.
  • Both rule sets are supported. If a stat block looks like the wrong edition, check the 2014/2024 toggle — it changes the format and the underlying maths, not just a label.
  • The tools page has a quick reference for challenge rating, conditions and starting gear, which answers a fair number of the rules questions that reach me.