Tell me more ×
Game Development Stack Exchange is a question and answer site for professional and independent game developers. It's 100% free, no registration required.

I'm new at this and I was wondering if someone could suggest the most appropriate API to use to make a card game that is:

  • cross-platform
  • two-player
  • peer-to-peer
  • capable of laying out cards (png files)
  • open-source
  • beginner-friendly (well documented)

If it helps to give a better answer, the game is based on Set: http://www.setgame.com/set/puzzle_frame.htm

This will be a standalone client application using C#, or any other suitable language for cross-platform GUI-based applications (e.g., Ruby, Java & Swing, Python).

There are a number of toolkits listed at:

http://content.gpwiki.org/index.php/Game_Engines This helps, but which toolkit would be most suitable?

share|improve this question
2  
Just letting you know, the FAQ specifically states these kinds of questions don't belong here. Also, if you're planning to use C# for a cross-platform game then you are going to be sorely disappointed. – Mike C Apr 26 '12 at 1:02

closed as not constructive by Byte56, Jonathan Hobbs, Tetrad Apr 26 '12 at 15:10

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.

1 Answer

Have you looked at Developing a Card Game Framework, or wagic - A Multi-platform Card game Engine, or Card Game Framework, or Java Playing Cards Game Framework?

If this is for the web (an easy way to get x-platform support) Open Source Card Game may work for you.

The only real way to know if any framework will work for you is to simply pick the best looking one and start cutting code against it. Sadly experienced developers run into situations where the framework they've chosen, even after painstaking evaluation, end up causing them pain, or having to be scraped. The Law of Leaky Abstractions holds here.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.