ArkhamHorror

# Arkham Horror LCG

![Screenshot](./docs/img/screenshot.png)

The goal of this project is to implement a web version of Arkham Horror with as
many of the rules implemented as possible.

## Features

* Multiplayer up to 4 players
* Multiplayer solitaire
* Tarot Readings
* Deck import from ArkhamDB and arkham.build

## Finished Content

### Chapter 1

All content is implemented. You can use every player card (including promos and
parallels) and play every campaign and scenario (including challenge
scenarios). The only things currently missing are some of the refractions,
designer dares, and other variants.

### Chapter 2

All content before 2027 is implemented.

* Brethren of Ash
* Children of Blood (Beta)
* Traces to Nowhere (Beta, side story)

Content marked beta will require enrollment in the beta program which is
available from the settings page. Beta content is likely to have more bugs than
usual and the expectation is that games may break in non-recoverable ways.

### Homebrew

There is fan-made content in here too: four campaigns and nine side stories
written by people in the community. Right now all Homebrew content is in
beta so you will need to enroll in the beta program before they show up.

Want to make your own? See [Writing homebrew content](./docs/homebrew.md).

## I just want to try this out on my computer

Easiest is the [prebuilt package](./docs/install/prebuilt.md): one download
with the game, the database and the web server already inside it. Nothing to
install, not even Docker.

If you would rather run it in Docker there is a one-liner for
[Linux](./docs/install/docker-linux.md), a longer path on
[Windows](./docs/install/docker-windows.md), and a
[by-hand version](./docs/install/docker-manual.md) if you want to write the
compose file yourself.

Later on, [upgrade.sh](./docs/install/updating.md) updates a Docker install or
a checkout. The prebuilt package updates itself.

## Local dev

This is the non-Docker path: the servers run on your machine, from the source
tree, with rebuilds and hot reload. The Docker instructions above are a
different thing and need none of this.

### Setup

```
./scripts/setup
```

On Windows this all happens inside WSL, which takes a few steps first — see
[Developing on Windows](./docs/windows.md).

It checks for everything the build needs, prints whatever is missing with the
command that fixes it, and installs them if you say yes. Then it installs the node
modules, creates the database, applies the migrations, and builds the backend
once.

`--check` reports and changes nothing. `--yes` skips the prompt, `--no-build`
leaves out the backend build, `--no-db` leaves the database alone, and
`--with-images` also fetches the image assets.

What it looks for, if you would rather do it yourself:

* ghcup, and GHC 9.14.1 through it. `backend/stack.yaml` sets `install-ghc:
  false`, so stack will not fetch a compiler of its own — it wants
  `ghc-9.14.1` on PATH, whatever plain `ghc` happens to be.
* Stack 3.7.1