This page contains all the information you need to get started with developing as well as useful tips.

The main language the whole project is written in is Clojure. Below are a few links to useful learning resources and documentation of Clojure and libraries used:

• Clojure for the Brave and True - a nice online crash course of Clojure, written in accessible language
• ClojureDocs - online Clojure documentation
• Reagent - ClojureScript interface to Facebook's React. Used in many places on the web presentation side.
• Hiccup - describes the HTML templating libraries used in the .cljs files.

There are several options available, including:

• IntelliJ IDEA with Cursive
• Emacs (Unix | Windows | MacOS) with CIDER

You need the following dependencies installed:

• Java8 (for MacOS, download the full JDK)
• Node.js, Node Package Manager (make sure npm is in your PATH)
• Leiningen (version 2+)
• MongoDB

Here's a guide for Windows specifically

You can install nearly everything through Homebrew except the NPM modules /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Then:

• brew tap caskroom/versions
• brew cask info java8
• brew cask install java8
• brew install clojure
• brew install node
• brew install mongo
• brew install leiningen

If you want to contribute, you should fork the mtgred/netrunner repository on github. For a review of basic git commands, visit http:https://rogerdudler.github.io/git-guide/

After cloning your own fork on your machine, configure mtgred/netrunner as a remote.

$ git remote add upstream https://github.com/mtgred/netrunner.git

When you run git remote -v, you now should see something like this:

origin  https://github.com/yourgithubname/netrunner (fetch)
origin  https://github.com/yourgithubname/netrunner (push)
upstream        https://github.com/mtgred/netrunner.git (fetch)
upstream        https://github.com/mtgred/netrunner.git (push)

To keep your own repository up-to-date, refer to Syncing a fork.

If you want to start coding a feature or fix a bug, simply use

git switch -c your_new_branch_name

to create a local copy of the current master branch named your_new_branch_name that can easily be merged with a pull request.

Push it to your own repo with git push origin your_new_branch_name and create a pull request via the github website.

Adding IDE-specific files to .gitignore should happen in a global gitignore file, e.g. in ~/.gitignore:

# IDEA IntelliJ files
.idea
*.iml

And then inform git of this file via:

git config --global core.excludesfile '~/.gitignore'

1. git checkout master
2. git pull upstream master
3. git checkout -b features
4. echo "cool feature" > feature.txt
5. git commit -am "Added cool feature"
6. git checkout master
7. git pull upstream master
8. git checkout feature
9. git rebase master
10. git push origin feature

Install JavaScript dependencies:

$ npm ci

Possibly with --dbpath option specifying card data directory:

$ mongod

On Windows, run mongod.exe. See Install MongoDB on Windows.

$ lein fetch

This data fetch only needs to be performed if it's your first time building the project OR new card data has been made available on NetrunnerDB and you want to update your local data (e.g., a new data pack).

If you don't want card images to be downloaded (such as on a testing environment), you can run lein fetch --no-card-images. If you have the card data saved locally, use lein fetch --local ../path/to/data.

Only necessary if this is your first time building the project OR any .cljs files have been edited/modified and you need to update the UI:

$ npm run cljs:build

This step can be skipped if you have no plans to modify CSS/layout items.

$ npm run css:build

Start server in dev mode, and open a REPL prompt:

lein repl

Open one or more browser sessions and visit: http:https://localhost:1042

Using lein repl compiles the project if it's out of date, then launches an interactive shell from which you can type and evaluate Clojure commands. Once you have a game initiated, you can modify card code and execute the defcard form to load the changed code. To see changes reflected in an ongoing game, simply trash/discard a copy of the card in question and reinstalling it or playing it again to see the new behavior.

How can I use a REPL while running the server?

Create a new Run Configuration and choose Clojure REPL -> Local:

When the REPL started, use (future-call -main) to start the game server.

I start a REPL from IntelliJ IDEA, but I get the following error: 'No nREPL ack received'.

Cursive uses a default time out of 60 seconds when trying to connect to the REPL. Change Settings -> Clojure -> REPL startup timeout to a higher value:

How can I access the code in the REPL?

Right click the file in the editor, REPL -> Switch REPL NS to current file or run (in-ns 'game.core) to switch the namespace

How do I run the tests?

Run lein test from the command line.

I have the REPL up and running, now what?

Go to your browser and start a game. Now, from the REPL prompt, run

(def state (:state (second (last (:lobbies @web.app-state/app-state)))))

You can now access the state of your game as you are playing it by using the variable @state. For example, try running (get-in @state [:corp :hand]) to see the corp's current hand, or (->> (get-in @state [:corp :hand]) (map :printed-title)) to filter for the card titles.

So, I have changed a card, now what?

Evaluate defcard with your new card definition in the REPL. For example, to make Akamatsu give 10 MU, evaluate

(defcard "Akamatsu Mem Chip"
  {:constant-effects [(mu+ 10)]})

Note that if the card you changed is already installed, you have to play it again before the changes take effect.

If you want to use Emacs you have to install clojure-mode and cider. Cider allows you to connect Emacs to a REPL with C-c M-j. To reload a function, it's C-c C-c with the cursor inside the function definition. To reload a file (eg. card.clj) it's C-c C-k.

Install the extension for https://calva.io/.

The main communication channel between developers, besides GitHub, is the team's Slack Channel. To request access, send an email to NoahTheDuke stating who you are on GitHub and linking an open PR.

If you want to look for some of the easier issues to get started, look through our GitHub issues for issues labeled easy. These usually don't require in-depth codebase knowledge, and changes required to fix them shouldn't involve more than 1-3 source files.

The project is configured to integrate with CircleCI. Create a CircleCI account and create a new project linked to your Github fork of this project. CircleCI will automatically build and run tests when you push changes to your repo.