All ONR cards will have their titles prefaced by "ONR ", like ONR Accounts Receivable.

All ONR cards have unique subtypes, like onr-asset or onr-black-ice.

As I work, I'm trying to put cards in baskets: easy to implement, things that will take work, and things that require an actual game system rewrite.

Implementation status of ONR cards can be found in 'implement' and 'unimplemented' text files, as I slowly work through them (in order).

There are several game systems that need to be changed/modified/added for onr to work. These are:

• counters get hosted all over the place, and lots of cards have their own unique counters (every single virus, lots of ice, etc)
• lots of cards create permanent floating effects
• you can pay agenda points (different to forfieting agendas)
• some cards disable actions (as a floating effect) until a cost is paid - interaction needs to persist even if that card dissapears
• purging requires you to forgo future actions. You can purge in any ability window.
• Other abilities on both sides will also require players to forgo actions
  • the solution for this is to do the following
  • There's a "actions owed/to forgo" counter for each player
  • If the counter is positive, no basic or click actions can be taken by that player except forgoing an action
• The ONR trace system is different - the corp can pay credits up to the trace strength, and the runner needs link cards to interact with traces
• Bad publicity does not give credits per run - it instead makes the corp lose at 7
• Regions (and certain other cards) require the corp to have the rez credits handy already, and are rezzed when installed

• Base Set
  • 374 cards total
  • 109 full implementations
  • 7 partial implementations
  • tests complete for 16/116 implemented cards
• Proteus Set
  • 154 cards total
• Classic Set
  • 52 cards total

Total: 116/580 cards implemented.

I thought it would be fun.

Hosted at http:https://www.jinteki.net. Example of gameplay.

Card rules implementation status

Install Leiningen, NodeJS and MongoDB.

This project runs on Java 8. If you're on OSX or Linux, we recommend using jenv to manage your java environment.

You can check your setup by running:

$ lein version
Leiningen 2.9.6 on Java 16.0.1 OpenJDK 64-Bit Server VM

Your exact version numbers below may vary, but we require Java 1.8+.

Populate the database and create indexes using:

$ lein fetch [--no-card-images]
1648 cards imported

$ lein create-indexes
Indexes successfully created.

You can optionally pass --no-card-images if you don't want to download images from NetrunnerDB, as this takes a while. See lein fetch help for further options.

To install frontend dependencies, run:

$ npm ci
added 124 packages, and audited 125 packages in 2s

To compile CSS:

$ npm run css:build
compiled resources/public/css/netrunner.css

Optionally you can say npm run watch:css to watch for changes and automatically recompile.

Compile ClojureScript frontend:

$ npm run cljs:build
[:app] Compiling ...
[:app] Build completed. (238 files, 0 compiled, 0 warnings, 22.18s)

Finally, launch the webserver and the Clojure REPL:

$ lein repl
dev.user=>

and open http:https://localhost:1042/.

To run all tests:

$ lein test
Ran 2640 tests containing 44704 assertions.
0 failures, 0 errors.

To run a single test file:

$ lein test game.cards.agendas-test
Ran 216 tests containing 3536 assertions.
0 failures, 0 errors.

Or a single test:

$ lein test :only game.cards.agendas-test/fifteen-minutes
Ran 1 tests containing 29 assertions.
0 failures, 0 errors.

For more information refer to the development guide.

• Development Tips and Tricks
• Writing Tests
• "Profiling Database Queries" in DEVELOPMENT.md

Jinteki.net is released under the MIT License.