matthewtodd-settlers 0.1.1

data/Rakefile

@@ -0,0 +1,18 @@
+require 'rubygems'
+
+spec = Gem::Specification.new do |s|
+  s.name             = 'settlers'
+  s.version          = '0.1.1'
+  s.summary          = "Provides a simple command-line executable for playing Robb Thomas' JSettlers game."
+  s.files            = FileList['[A-Z]*', 'bin/*', 'lib/**/*.rb', 'resources/**/*']
+  s.executables      = ['settlers']
+  s.author           = 'Matthew Todd'
+  s.email            = 'matthew.todd@gmail.com'
+end
+
+desc 'Generate a gemspec file'
+task :gemspec do
+  File.open("#{spec.name}.gemspec", 'w') do |f|
+    f.write spec.to_ruby
+  end
+end

data/bin/settlers

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+
+$:.unshift File.expand_path(File.join(File.dirname(__FILE__), '..', 'lib'))
+require 'settlers'
+
+Settlers::Game.new(*ARGV).play

data/lib/settlers.rb

@@ -0,0 +1,3 @@
+require 'settlers/jar'
+require 'settlers/runner'
+require 'settlers/game'

data/lib/settlers/game.rb

@@ -0,0 +1,26 @@
+module Settlers
+  class Game
+    def initialize(port=8880, server_delay=2)
+      @host, @port, @server_delay, @runner = 'localhost', port, server_delay, Runner.new
+    end
+
+    def play
+      @runner.background server.command('soc.server.SOCServer', @port, 4, 'root', ''); sleep @server_delay.to_i
+      @runner.background server.command('soc.robot.SOCRobotClient', @host, @port, 'Leonardo', '')
+      @runner.background server.command('soc.robot.SOCRobotClient', @host, @port, 'Humperdink', '')
+      @runner.background server.command('soc.robot.SOCRobotClient', @host, @port, 'Elwood', '')
+      @runner.foreground client.command('soc.client.SOCPlayerClient', @host, @port)
+      @runner.clean_up
+    end
+
+    private
+
+    def server
+      Jar.new('JSettlersServer.jar')
+    end
+
+    def client
+      Jar.new('JSettlers.jar')
+    end
+  end
+end

data/lib/settlers/jar.rb

@@ -0,0 +1,17 @@
+module Settlers
+  class Jar
+    def initialize(path)
+      @path = path
+    end
+
+    def command(*args)
+      ['java', '-cp', full_path] + args
+    end
+
+    private
+
+    def full_path
+      File.expand_path(File.join(File.dirname(__FILE__), '..', '..', 'resources', 'jsettlers-1.0.6', @path))
+    end
+  end
+end

data/lib/settlers/runner.rb

@@ -0,0 +1,25 @@
+module Settlers
+  class Runner
+    def initialize
+      @pids = []
+    end
+
+    def background(command)
+      @pids.unshift fork { exec *ensure_strings(command) }
+    end
+
+    def foreground(command)
+      system *ensure_strings(command)
+    end
+
+    def clean_up
+      Process.kill 'INT', *@pids
+    end
+
+    private
+
+    def ensure_strings(command)
+      command.map { |arg| arg.to_s }
+    end
+  end
+end

data/resources/jsettlers-1.0.6/COPYING.txt

@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) 19yy  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) 19yy name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.

data/resources/jsettlers-1.0.6/README.txt

@@ -0,0 +1,264 @@
+Java Settlers - A web-based client-server version of Settlers of Catan
+
+Introduction
+------------
+
+JSettlers is a web-based version of the board game Settlers of Catan
+written in Java. This client-server system supports multiple
+simultaneous games between people and computer-controlled
+opponents. Initially created as an AI research project.
+
+The client may be run as a Java application, or as an applet when
+accessed from a web site which also hosts a JSettlers server.
+
+The server may be configured to use a MySQL database to store account
+information.  A client applet to create user accounts is also
+provided.
+
+JSettlers is an open-source project licensed under the GPL. The
+software is maintained as a SourceForge project at
+http://sourceforge.net/projects/jsettlers.
+
+Forums for discussions and community based support are provided at
+SourceForge.
+
+                          -- The JSettlers Development Team
+
+
+Contents
+--------
+
+  Documentation
+  Requirements
+  Setting up and testing
+  Shutting down the server
+  Hosting a JSettlers Server
+  Database Setup
+  Development and Compiling
+
+
+Documentation
+-------------
+
+User documentation for game play is available as .html pages located
+in "docs/users" directory. These can be put on a JSettlers server for
+its users using the applet.
+
+Currently, this README is the only technical documentation for running
+the client or server, setup and other issues. Over time other more
+will be written. If you are interested in helping write documentation
+please contact the development team from the SourceForge site.
+
+
+Requirements
+------------
+
+To play JSettlers by connecting to a remote server you will need the
+Java Runtime Version 1.1 or above (1.4 recommended). To connect as an
+applet, use any browser which is Java enabled (again, we recommend
+Java 1.4 using the browser plug-in).
+
+To Play JSettlers locally you need the Java Runtime 1.4 (or
+later). Remote clients started on the command line can connect
+directly to this server. To host a JSettlers server and provide a web
+applet for clients, you will need an http server such as Apache's
+httpd, available from http://httpd.apache.org.
+
+To build JSettlers from source, you will need Apache Ant, available from
+http://ant.apache.org.
+
+
+Setting up and testing
+----------------------
+
+From the command line, make sure you are in the JSettlers distribution
+directory which contains both JSettlers.jar, settlers-server.jar and the
+"lib" directory.  Start the server with the following command
+(server requires Java 1.4):
+
+  java -jar JSettlersServer.jar 8880 10 dbUser dbPass
+
+If MySQL is not installed and running (See "Database Setup"), you will
+see a warning with the appropriate explanation:
+
+  Warning: failed to initialize database: ....
+
+The server will function normally except that user accounts cannot be
+maintained.
+
+Now, from another command line window, start the player client with
+the following command:
+
+  java -jar JSettlers.jar localhost 8880
+
+If you are using Java 1.1 you will need to unpack the Java archive
+(Java could not run directly from jar files until version 1.2). The
+commands to unpack, then start the client are:
+
+  jar -xf JSettlers.jar
+  java soc.client.SOCPlayerClient localhost 8880
+
+In the player client window, enter "debug" in the Nickname field and
+create a new game.
+
+Type *STATS* into the chat part of the game window.  You should see
+something like the following in the chat display:
+
+  * > Uptime: 0:0:26
+  * > Total connections: 1
+  * > Current connections: 1
+  * > Total Users: 1
+  * > Games started: 0
+  * > Games finished: 0
+  * > Total Memory: 2031616
+  * > Free Memory: 1524112
+
+If you do not, you might not have entered your nickname correctly.  It
+must be "debug" in order to use the administrative commands.
+
+Now you can add some robot players.  Enter the following commands in
+separate command line windows:
+
+  java -cp JSettlersServer.jar soc.robot.SOCRobotClient localhost 8880 robot1 passwd
+
+  java -cp JSettlersServer.jar soc.robot.SOCRobotClient localhost 8880 robot2 passwd
+
+  java -cp JSettlersServer.jar soc.robot.SOCRobotClient localhost 8880 robot3 passwd
+
+Now click on the "Sit Here" button and press "Start Game".  The robot
+players should automatically join the game and start playing.
+
+If you want other people to access your server, tell them your server
+IP address and port number (in this case 8880).  They will enter the
+following command (or use the instructions above for Java 1.1):
+
+  java -jar JSettlers.jar <host> <port_number>
+
+Where host is the IP address and port_number is the port number.
+
+If you would like to maintain accounts for your JSettlers server,
+start the database prior to starting the JSettlers Server. See the
+directions in "Database Setup".
+
+
+Shutting down the server
+------------------------
+
+To shut down the server enter *STOP* in the chat area of a game
+window.  This will stop the server and all connected clients will be
+disconnected.
+
+
+Hosting a JSettlers server
+--------------------------
+  - Start MySQL server (optional)
+  - Start JSettlers Server
+  - Start http server (optional)
+  - Copy JSettlers.jar jar and "web/*.html" server directory (optional)
+    - Extract JSettlers.jar to allow Java 1.1 clients (optional)
+  - Copy "docs/users" to the server directory (optional)
+
+To host a JSettlers server, start the server as described in "Setup
+and Testing". To maintain user accounts, be sure to start the database
+first. Remote users can simply start their clients as described there,
+and specify your server as host.
+
+To provide a web page from which users can run the applet, you will
+need to set up an html server, such as Apache.  We assume you have
+installed it correctly, and will refer to "${docroot}" as a directory
+your web server is configured to provide.
+
+Copy the sample .html pages from "web" to ${docroot}. Edit them, to
+make sure the PORT parameter in "index.html" and "account.html" applet
+tags match the port of your JSettlers server.
+
+Next copy the client files to the server. Copy JSettlers.jar to
+${docroot}. This will allow users with Java version 1.2 or later
+installed to use the browser plug-in. Using the .jar like allows for
+faster downloads, and startup times, but does not allow browsers with
+Java version 1.1 to start the client.
+
+To allow browsers with old versions of Java (1.1) to use the applet,
+unpack JSettlers.jar and copy (recursively) the extracted "soc"
+and "resources" directories to ${docroot}. To unpack, use:
+
+    $ jar -xf JSettlers.jar
+
+You may also copy the "doc/users" directory (recursively) to the same
+directory as the sample .html pages to provide user documentation.
+
+Your web server directory structure should now contain:
+  ${docroot}/index.html
+  ${docroot}/*.html
+  ${docroot}/JSettlers.jar
+  ${docroot}/resources/...
+  ${docroot}/soc/...
+  ${docroot}/users/...
+
+Users should now be able to visit your web site to run the client
+version of JSettlers.
+
+
+Database Setup
+--------------
+
+If you want to maintain user accounts, you will need to set up a MySQL
+database. This will eliminate the "Problem connecting to database"
+errors from the server. We assume you have installed it correctly. 
+
+Run the following commands to create the database and configure its
+tables.
+
+CREATE DATABASE socdata;
+
+USE socdata;
+
+CREATE TABLE users (nickname VARCHAR(20), host VARCHAR(50), password VARCHAR(20), email VARCHAR(50), lastlogin DATE);
+
+CREATE TABLE logins (nickname VARCHAR(20), host VARCHAR(50), lastlogin DATE);
+
+CREATE TABLE games (gamename VARCHAR(20), player1 VARCHAR(20), player2 VARCHAR(20), player3 VARCHAR(20), player4 VARCHAR(20), score1 TINYINT, score2 TINYINT, score3 TINYINT, score4 TINYINT, starttime TIMESTAMP);
+
+CREATE TABLE robotparams (robotname VARCHAR(20), maxgamelength INT, maxeta INT, etabonusfactor FLOAT, adversarialfactor FLOAT, leaderadversarialfactor FLOAT, devcardmultiplier FLOAT, threatmultiplier FLOAT, strategytype INT, starttime TIMESTAMP, endtime TIMESTAMP, gameswon INT, gameslost INT, tradeFlag BOOL);
+
+
+To create accounts, run the simple account creation client with the
+following command:
+
+  java -jar JSettlers.jar soc.client.SOCAccountClient localhost 8880
+
+
+Development and Compiling
+-------------------------
+
+Source code for JSettlers is available via anonymous CVS. Source code
+tarballs are also made available.  See the project website at
+http://sourceforge.net/projects/jsettlers/ for details. Patches
+against CVS may be submitted there.
+
+Before building, make sure you have at least version 1.4 of the Java
+development kit installed.  If you simply want to run the client and
+server, you only need the Java. If you wish to maintain a user
+database for your server, you need MySQL installed, and configured.
+
+This package was designed to use the ANT tool available from
+http://ant.apache.org tools.  We assume you have installed it
+correctly.
+
+Check the "build.properties" file. There may be build variables you
+may want to change locally. These can also be changed from the command
+line when calling ant, by passing a "-Dname=value" parameter to ant.
+
+Now you are ready to invoke ant. There are several targets, here are
+the most useful ones:
+
+ build      Create project jar files. (default)
+ clean      Cleans the project of all generated files
+ compile    Compile class files into "target/classes"
+ dist       Build distribution tarballs and zips.
+ javadoc    Creates JavaDoc files in "target/docs/api"
+ src        Create a tarball of the source tree
+
+All files created by building are in the "target" directory, including
+Java .class files, and JavaDoc files. Distribution tarballs, zip
+files, and installation files are placed in "dist".

data/resources/jsettlers-1.0.6/VERSIONS.txt

@@ -0,0 +1,50 @@
+[ The list of the different public versions of JSettlers ]
+
+    > 1.0.6 (build 2004-11-17)
+
+- Fixed the same PORT property error in the Account client
+- Fixed bug which could allow modified clients to invoke admin
+  commands (*STOP*, *KILLCHANNEL*, etc) (Lasse Vartiainen)
+- Fixed 920375, 1022157: mysql-connector-3.x fails: version 2.x works
+  (Mezryn)
+- Fixed 1060651: Bots crash if database backend is used (Jack Twilley)
+- Moved more SQL error handling and reconnecting from SOCServer to
+  SOCDBHelper correcting potential errors like 1060651
+
+    > 1.0.5 (build 2004-06-12)
+
+- Fixed an error introduced into the applet initialization which kept
+  the PORT property from being read properly
+
+    > 1.0.4 (build 2004-06-10)
+
+- build.xml file added for Ant builds
+- soc.util.Version class added so both build files and source code get
+  version and copyright info from build.xml. Clients and server updated
+- Build process creates two jar files: one for client, one for server
+- README updated for jar file invocation, with additional sections for
+  intro, requirements, hosting a server, and development
+- Fix for inconsistent game state when players leave a game.
+- Divider in chat window cannot be moved off-screen
+- Text of game chat now correctly scrolls to bottom of text.
+- Rewrite of much of the display code to address continuing display
+  issues. Methods which directly manipulate GUI components can cause
+  race conditions, and are now never called from main networking
+  thread.
+- Removed calls to deprecated methods
+- Images can now be loaded from files (on server or not) or from
+  within jar.
+
+    > 1.0.3 (build 2004-03-29)
+
+- Continuing to fix the display bug in the SOCPlayerClient
+
+    > 1.0.2 (build 2004-03-26)
+
+- Fixed display bug (again) in the SOCPlayerClient when run as a stand
+  alone.
+
+    > 1.0 (build 2004-03-14)
+
+- First release. See the README file for how to setup a server and
+  robot clients.

metadata

@@ -0,0 +1,64 @@
+--- !ruby/object:Gem::Specification 
+name: matthewtodd-settlers
+version: !ruby/object:Gem::Version 
+  version: 0.1.1
+platform: ruby
+authors: 
+- Matthew Todd
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2008-10-10 00:00:00 -07:00
+default_executable: settlers
+dependencies: []
+
+description: 
+email: matthew.todd@gmail.com
+executables: 
+- settlers
+extensions: []
+
+extra_rdoc_files: []
+
+files: 
+- Rakefile
+- bin/settlers
+- lib/settlers/game.rb
+- lib/settlers/jar.rb
+- lib/settlers/runner.rb
+- lib/settlers.rb
+- resources/jsettlers-1.0.6
+- resources/jsettlers-1.0.6/COPYING.txt
+- resources/jsettlers-1.0.6/JSettlers.jar
+- resources/jsettlers-1.0.6/JSettlersServer.jar
+- resources/jsettlers-1.0.6/README.txt
+- resources/jsettlers-1.0.6/VERSIONS.txt
+has_rdoc: false
+homepage: 
+post_install_message: 
+rdoc_options: []
+
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+requirements: []
+
+rubyforge_project: 
+rubygems_version: 1.2.0
+signing_key: 
+specification_version: 2
+summary: Provides a simple command-line executable for playing Robb Thomas' JSettlers game.
+test_files: []
+