Web based implementation of Keyforge: the Unique Deck Game
This is the respository for the code internally known as keyteki which is running on thecrucible.online allowing people to play KeyForge online using only their browser
Glad you noticed! Yes, jinteki was a huge inspiration for this project, as the interface is clean and user friendly, so I've tried to make this similar in a lot of ways
Keyteki is a fork of the ringteki sourcecode
Sure! The code is written in node.js(server) and react.js(client). Feel free to make suggestions, implement new cards, refactor bits of the code that are a bit clunky(there's a few of those atm), raise pull requests or submit bug reports
If you are going to contribute code, try and follow the style of the existing code as much as possible and talk to me before engaging in any big refactors. Also bear in mind there is an .eslintrc file in the project so try to follow those rules.
Documentation for implementing cards
There is also a list of events raised by the code here. If you're writing abilities which listen for these events, it tells you what parameters the event has and whether it has a handler. If you're writing code which calls any of these events, please make sure you pass the same parameters.
The biggest help at the moment would be in terms of CSS, as that's a bit of a weakness of mine, feel free to pick up any of the issues tagged 'CSS' in the issue list.
If you're not coding inclined, then just playing games on the site, and reporting bugs and issues that you find is a big help
That's not a question, but that still sucks, sorry :( First, bear in mind the site is in its infancy so a lot of things aren't implemented yet, but you should be able to do most things with a bit of manual input. If there's anything you can't do that you need to be able to do, let me know by raising an issue.
See this document for features I have planned and a link to the currently implemented cards:
Check out the About page of Keyteki live deployment.
If you have docker installed, you can use the containerised version of the site.
Clone the repository
git submodule init
git submodule update
npm install
docker-compose up
(in another terminal)
docker-compose exec lobby node server/scripts/fetchdata
- Git
- Node.js 8
- MongoDB
- ZeroMQ Libraries
Clone the repository
git submodule init
git submodule update
npm install # See https://github.com/JustinTulloss/zeromq.node/issues/283 for zmq errors on OS X
mkdir server/logs
Create config/local.json and put the following in it:
{
dbPath: 'mongodb://localhost:27017/keyforge',
mqHost: 'localhost',
lobby: {
port: 4000
},
gameNode: {
hostname: 'localhost'
}
}
node server/scripts/fetchdata.js
node .
node server/gamenode
There are two exectuable components and you'll need to configure/run both to run a local server. First is the lobby server and then there are game nodes. The default configurations assume you are running mongo locally on the default port. If you need to change any configurations, edit config/default.json5 or create a config/local.json5 configuration that overrides any desired settings.
For production:
npm run build-vendor
npm run build
NODE_ENV=production PORT=4000 node .
Then for each game node (typically one per CPU/core):
PORT={port} SERVER={node-name} node server/gamenode
The game server should be accessible by browsing to localhost:4000.
You can register 2 or more users, to play against yourself. They can have fake email addresses. You can login as both users either from 2 different browsers, or by using an incognito window.
These users will be normal (non-admin) users. To escalate a user to the admin role requires manual edits to the Mongo database, but that is not required for testing in-game functionality.
If you implement or make changes to a card, you can use manual mode to add it to a deck from within a game. Use manual mode, and the command:
/add-card <card name>
Before you run the unit tests, be sure all the necessary dependencies are installed
npm install
Then, to run the tests:
npm test
All JavaScript code included in Ringteki should pass (no errors, no warnings)
linting by ESLint, according to the rules defined in
.eslintrc at the root of this repo. To manually check that that is indeed the
case install ESLint and run
eslint client/ server/ test/
from repository's root.
All tests should also pass. To run these manually do:
npm test
If you are making any game engine changes, these will not be accepted without unit tests to cover them.