Online Play

In this modern day and age, you can actually play instantly (and completely free) online against other opponents without ever having to purchase any cards.  There are several programs available for this, the most popular of which is GCCG. Lackey CCG is another option but there’s a really small user base so you are likely to struggle finding an opponent.

Generic Collectible Card Game (GCCG) is a multiplayer multiplatform implementation of a card game engine. The card game engine is designed to be of general purpose core for several modules each defining the game specific behaviour.

You can download GCCG here.

 


GCCG SETUP INSTRUCTIONS

Setting up GCCG and the MECCG module is not exactly the most straightforward process and may require a bit of effort. The following instructions comes from the relative Git Repository you need to reference at the very least to download the module in ZIP format.

 

  1. One of the things you need to know, is how to get gccg up and running.
  2. Below are the instructions for getting a merged gccg/core directory running.
    • If you have a repeal and replace setup using tortoisesvn and the old svn repo, you will have to store this until you get up and running again, in case you are worried.
  3. There is some discrepancy with file dates, when you replace files in your /gccg/core folder with files from this git repo.
  4. When checking out from this repository, make sure you checkout the MASTER branch, same for if you download a zip archive. Up above where it says branch it should say “Branch:master”, left of the “New pull request” button.
  5. You have three options, if you have your gccg/core folder raw and running, without the metw sources you can:
    • Manually download the zip format from here and not bother with GIT, and replace the files from the zip into the /gccg/core folder with files from /gccg/dc maintaining the structure.
      1. Using a file merge program, depending on settings might not cut it, if you are keeping the “newer files” in /gccg/core
      2. If you do just straight replace files with matching names&locations and not replace directories/folders then you are good.
    • Checking out the master branch from a trusty git gui app, like tortoisegit, sourcetree, etc
      1. From here you can copy+replace files the same way, as above. But now you have a git repo that can be updated.
      2. And if you replace the files with “newer dates” from the new dc git repo, when you goto replace in the future you can can just merge files and not worry about the dates issue.
      3. When checking out you can checkout to a folder called /gccg/dc or /gccg/metw, the top level name doesn’t matter.
      4. The easiest is when you have a folder structure such as /gccg/core and /gccg/metw
      5. The only reason the top level name was changed to dc was to distiguish the old svn metw folder and the new git dc folder.
      6. Which like I said when you check out you can, put the checkout in a folder/directory called gccg/metw
    • If you are GOOD with the command line you might be able to git checkout right into the gccg/core folder and replace files in their respective folders.
      1. In the future tho you would have to svn discard changes, and git checkout again, and you will not be able to update the git repository you checkout, nor the svn repository. UNLESS you are a FREAKING git+svn protocol wizard and get into: https://git.wiki.kernel.org/index.php/Git-svn
      2. Or you could get into some nasty .gitIgnore shenanigans…
  6. All in all the best setup is from SCRATCH:
    • Checkout the svn gccg core repo
    • Checkout the git gccg dc repo (into a folder called metw, if you want)
    • Leaving you with /gccg/core & /gccg/dc
    • Recursively COPY and REPLACE the files in /gccg/core with the files from /gccg/dc
    • Change the address line in: gccg/core/scripts/client.triggers {from} server.name=server.name_default; {to} server.name_default=”199.91.172.122″;
    • From here, you can, fetch/pull updates into the dc git repo, and
    • merge repeat, UNLESS the gccg/core SVN repo gets updated.
    • Then you’re going to have to discard changes in the svn gccg/core
    • Then repeat starting at 7) again.
    • NOTE the svn /gccg/core isn’t really updated (yearly) much so…
  7. If you need any help, see http://forum.councilofelrond.com