Projects / webDiplomacy

webDiplomacy

webDiplomacy (previously phpDiplomacy) is a Web implementation of a popular turn based strategy game in which you battle to control Europe. It is not a game of luck: to win you must be diplomatic and strategic, forming and breaking allegiances and bargains with your friends and enemies. It features an interface intuitive and simple enough that seasoned Diplomacy pros and complete newcomers can play alongside each other.

Tags
Licenses
Operating Systems
Implementation
Translations

Recent releases

  •  24 Apr 2010 04:52

    Release Notes: This release fixes bugs and has allowed for a cool-off period, so the first 1.0x release will be a stable platform to start developing from.

    •  06 Feb 2010 10:28

      Release Notes: This release fixes some bugs, marks responded forum threads with an icon, adds customizable FAQ entries, adds moderator reporting, and adds title-bars with descriptions to most pages.

      •  10 Jan 2010 09:24

        Release Notes: This version adds variant support, a long requested feature allowing non-standard maps to be played. It also makes some significant improvements to server-side order validation efficiency.

        •  20 Dec 2009 06:13

          Release Notes: This version fixes bugs and makes optimizations regarding the new live-game feature, allowing instantaneous processing when ready. Bugs and inefficiencies in the new JavaScript order-generation code have been removed, and caching capability has been improved. Several JavaScript tweaks have been made, allowing small improvements. For example, the forum now remembers which individual threads have been read, some CSS tweaks have been made, JavaScript error logging has been made silent, and more preperations for future variant support have been made.

          •  15 Nov 2009 08:27

            Release Notes: This version adds client-side order generation and updates some map code to fix bugs, reduce server load, prepare for future variants and translations, and make things quicker for users.

            Recent comments

            23 Aug 2005 14:35 stumegan

            well I like it ;)
            Hi all,

            Notwithstanding the issues in the other comments I just wanted to post and say I am currently running an installation using the prior verison 0.6 and am very happy with it. Not only that , but the author kestas offered great support and was very helpful. I have been looking for a good implementation of Diplomacy to host,and have found it in this project.

            I am eagerly awating the 0.72 upgrade as it has some specific changes to help support my site that he is including.

            If you want to see the prior early beta version running, check out:

            http://stumegan.net/Diplomacy

            07 Feb 2005 16:40 kestasjk

            Re: Major Security Issues

            >
            > %
            > % Until a stable version is released
            > (the
            > % next release will be stable) all
            > % information is passed using GET
            > % requests, for easier debugging; in
            > the
            > % next version POST will be used.
            > % Ultimately it doesn't make that much
            > % difference, passwords have to be sent
            > in
            > % plaintext one way or another (unless
            > % you're using SSL).
            > %
            >
            > I've been using the following package at
            > work:
            >
            > http://freshmeat.net/projects/maxmediamanager/
            >
            > And they utilized a JS function to
            > convert the password on the login page
            > to a MD5 hash in order to get around the
            > issue of not using SSL enabled pages.
            > Perhaps something like that would
            > satisfy the comments made regarding lack
            > of security on the login page.
            >


            Thanks for the info gOOpy, I'll look into it. However I'd like to avoid requiring JavaScript because it's so hard to get a Script to work across multiple browsers.


            Also there's ultimately a plaintext string which authenticates you; whether it's an md5 hash or a password doesn't really matter, they would both perform exactly the same function and have exactly the same risk.


            I've changed the form submission from GET to POST for this release; so phpDiplomacy uses the same sort of authentication mechanism as phpbb and almost any other non-ssl login form on a website, so I don't think there's any real security problem here. :)


            As I said thanks for the info, I'll look into it,

            Kestas J. K

            07 Feb 2005 09:45 goopie

            Re: Major Security Issues

            >
            > Until a stable version is released (the
            > next release will be stable) all
            > information is passed using GET
            > requests, for easier debugging; in the
            > next version POST will be used.
            > Ultimately it doesn't make that much
            > difference, passwords have to be sent in
            > plaintext one way or another (unless
            > you're using SSL).
            >


            I've been using the following package at work:

            http://freshmeat.net/projects/maxmediamanager/

            And they utilized a JS function to convert the password on the login page to a MD5 hash in order to get around the issue of not using SSL enabled pages. Perhaps something like that would satisfy the comments made regarding lack of security on the login page.

            22 Jan 2005 00:29 kestasjk

            Re: Major Security Issues
            FYI I've resolved the register_globals issue. Regards,
            Kestas.

            13 Jan 2005 19:49 kestasjk

            Re: Major Security Issues

            > I highly don't recommend installing this
            > package untill several issues are
            > addressed and corrected.
            %
            > Login details including plaintext
            > password are shown in the URI !!!

            Until a stable version is released (the next release will be stable) all information is passed using GET requests, for easier debugging; in the next version POST will be used. Ultimately it doesn't make that much difference, passwords have to be sent in plaintext one way or another (unless you're using SSL).


            > The script includes a function to
            > disable operation if register globals is
            > on.
            > No matter what the authors feelings are
            > on this matter, PHP.ini settings are a
            > personal choice and are not for him to
            > dictate.
            >
            > All this has acomplished is that the
            > check function will be disabled and the
            > script used without it.

            Bear in mind that register globals is off by default; I don't think as many people will have a problem with this as you suggest.

            Otherwise I agree; the register globals check is only there because, until a stable release, I would prefer to keep register globals off so I can spend less time checking for security holes and more time developing the program. I'd like to deal with the register globals problem all at once.


            > The paths to configuration files are
            > incorrect.
            > They point to the top level directory
            > while those files reside in a folder
            > named "misc".

            There is only one configuration file, and it is included in a function which is in the "misc" directory, so I think you might have misunderstood something. Beta does work fine afterall, although it is beta.


            > Recommendation to the author, spend a
            > little less time on making the code 1337
            > or pretty and more time on program
            > substance!

            I try to make the code readable, well annotated, and structured; it doesn't take as long to read and it doesn't take much longer to write it that way anyway.


            > I assume there are many more such errors
            > but I will not test this application any
            > further untill the above noted problems
            > are corrected.

            Thanks for your feedback I appreciate it, I hope you'll give it another chance when there's a stable release. Thanks again,

            Kestas.

            Screenshot

            Project Spotlight

            OpenStack4j

            A Fluent OpenStack client API for Java.

            Screenshot

            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.